Hello,
I have added a security expression in record-level security to handle complex filter criteria that include the logged-in user as one of the filters.
I am exporting the record information using related actions and a scheduled job.
Export from the related action is fetching the expected output; however, export using the scheduled job is not returning the correct results because the record-level security condition is failing due to the logged-in user check.
To get the correct results, do I need to explicitly pass the filters defined in record-level security when querying the record from the scheduled job? Or is there a better way to achieve the same results?
Please advise.
Discussion posts and replies are publicly visible
I usually have a rule to allow the Application Administrators group and API users group to view all the Records.
You can then just run that process as admin and you won't have those types of issues.