Flow Designer Scope Error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
18 hours ago
Hi,
Why am I getting this error?
Should I run the flow as a system user or as the user who initiates the sessions?
This is a custom table but i checked and there is a create acl but im getting the error even though im running the flow as admin
Is it the scope of the flow itself?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
16 hours ago
Thank you for marking my response as helpful.
Do you require any further help?
If my response helped please close the thread by marking appropriate response as correct so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 10x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
16 hours ago - last edited 16 hours ago
Hi @Alon Grod
Try this:
1.Update Table Application Access
- Navigate to System Definition > Tables and search for sn_fin_manufacturer.
- Open the table definition and click on the Application Access tab.
- Ensure Accessible from is set to All application scopes.
- Check the Can create checkbox.
- Save the record.
2.Create a Cross-Scope Privilege Record
Switch your current application scope back to the source scope (the scope where your Flow resides).
Navigate to System Applications > Cross-Scope Privileges> Click New
- Source Scope: Choose your flow's custom application scope.
- Target Scope: Choose the application scope that owns sn_fin_manufacturer (likeFinancials).
- Target Name: sn_fin_manufacturer.
- Target Type: Table.
- Operation: Create.
- Status: Allowed
Click Submit.
3. Check Restricted Caller Access
- Navigate to System Applications > Application Restricted Caller Access.
- Look for an auto-generated row where the target is sn_fin_manufacturer.
- If you see an entry with a status of Requested or Invalidated,
- change its status to Allowed.
Clear the instance cache using cache.do and check.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti