- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-29-2023 10:36 AM
Hello everyone,
I am running into an issue where I have a flow that contains a script step that will delete records from a table. The flow and table in question are both within the same scope, and the table has Can delete checked off, however, when I test the flow, I get a cross scope error that says access to GlideRecord.deleteRecord from the scope is not allowed. I am unsure why I would run into a cross scope error when both the flow and table are of the same scope, so I am unsure how to fix it.
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-29-2023 01:10 PM
It does seem unusual.
Is the error similar to this?
Security restricted: Delete operation against 'x_xxxx' from scope 'rhino.global' has been refused due to the table's cross-scope access policy
Or more like this?
Execute operation on API 'GlideRecord.deleteRecord' from scope 'xxxx' was denied
With the first one if you only recently checked the box for "delete" on the table, it might take a while for that setting to replicate and you may have to use a script to flush some cached properties.
With the second error, you probably need create a Application Cross-Scope Access for your record to access that API from Global. The record would look something like this (create in your application scope).
Michael D. Jones
Proud member of the GlideFast Consulting Team!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-29-2023 01:10 PM
It does seem unusual.
Is the error similar to this?
Security restricted: Delete operation against 'x_xxxx' from scope 'rhino.global' has been refused due to the table's cross-scope access policy
Or more like this?
Execute operation on API 'GlideRecord.deleteRecord' from scope 'xxxx' was denied
With the first one if you only recently checked the box for "delete" on the table, it might take a while for that setting to replicate and you may have to use a script to flush some cached properties.
With the second error, you probably need create a Application Cross-Scope Access for your record to access that API from Global. The record would look something like this (create in your application scope).
Michael D. Jones
Proud member of the GlideFast Consulting Team!