Hi Team,
Today I will cover a real time example that why and when these issues occur.
Let's learn today about GlideRecordSecure. It helps to make sure that any update to the data should be done after checking its ACLs restrictions. We also call it "GlideRecord Query with Access Check"
It helps us to query data with the defined access in the system. If the user doesn't have access to the record to update and create then this will not work.
Also one very good point I learnt today that with GlideRecordSecure you will not be able to update the fields which are set as read only from the dictionary. That is also one of the access policies that GlideRecordSecure takes into consideration.
Make sure you follow the below practices if you want to run GlideRecordSecure perfectly:
- Make sure user has access from which you are running the script/API that is using GlideRecordSecure
- Make sure the fields shouldn't be read only from dictionary on which are are running the script/API that is using GlideRecordSecure
Hope this is helpful for you!
Thanks,
Shamma
