Another valid point that I forgot to mention. IF you have a custom field in a condition builder and the field gets deleted. This property will also throw back 0 records there, showing that there is something wrong.
I would be careful setting this property to TRUE, as unfortunately I've had Out of Box functionality break after doing this, something to do with User Role management. So yes, it is in theory a good property to set, however make sure you do thorough testing.
@@pervildstrandjobb7010 It was a few years ago, but I'm pretty sure it had to do with giving users Roles, and that any inherited roles weren't being applied to the user
Nice video, Göran. Thank you for sharing. I feel this sys property should be turned on (set to true) by default.
Another valid point that I forgot to mention. IF you have a custom field in a condition builder and the field gets deleted. This property will also throw back 0 records there, showing that there is something wrong.
what is the application you use to save script like this so you can just copy and paste it into the service now plateform?
Is it something running behind the scenes for glidequery
GlideQuery addresses this automatically. We have a Creator Toolbox episode on 4/6 to talk about this.
I would be careful setting this property to TRUE, as unfortunately I've had Out of Box functionality break after doing this, something to do with User Role management.
So yes, it is in theory a good property to set, however make sure you do thorough testing.
David, what OOB functionality stopped working? I seems pretty weird that it would.
@@pervildstrandjobb7010 It was a few years ago, but I'm pretty sure it had to do with giving users Roles, and that any inherited roles weren't being applied to the user