In a flow in our custom scope, creating a record results in error: Scope does not have create access

Bart Jan Bultma
Kilo Sage

We have a custom app for some changes in Hardware Asset Management.


In this application I am creating a Flow to create a bunch of new records in the table pc_hardware_cat_item.

However, at the step to create a record, I get an error saying 'Scope does not have create access to table pc_hardware_cat_item.

 

In order to solve this I have made the following changes:
In table settings of pc_hardware_cat_item, in the tab application access, I have set can create and can update to true. Accessible from was already set to 'All application scopes'.

scope issue 2.PNG

 

In table Application Cross-Scope Access I have created three records for read, write and create operations, from source scope HAM (our custom scope) to target scope Global, on target name pc_hardware_cat_item.

scope issue.PNG

 
It still is not working. What else can I do to fix this?

1 ACCEPTED SOLUTION

Bart Jan Bultma
Kilo Sage

I found the problem with this issue.

 

Changing the application access on a table has a caching issue. Cache.do didnt help, but waiting for a day did work! The next day the issue was resolved.

Another way to fix this caching issue without having to wait a day is to use a background script to flush the tables cache. In this knowledge article there is more about this issue and the background script I used:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0695145

View solution in original post

3 REPLIES 3

Ankur Bawiskar
Tera Patron
Tera Patron

@Bart Jan Bultma 

Did you try to delete the flow action and add it again and then activate and test?

Also try to clear instance cache using cache.do and then logout and login again

Regards,
Ankur
✨ Certified Technical Architect  ||  ✨ 9x ServiceNow MVP  ||  ✨ ServiceNow Community Leader

Hello Ankur,

I have removed the flow step and recreated it (albeit a bit simpler) and have cleared the cache, still the same errors as before. 

BartJanBultma_0-1698236486335.png

 

As an extra test I have recreated the flow but that returns the same error.

 

Bart Jan Bultma
Kilo Sage

I found the problem with this issue.

 

Changing the application access on a table has a caching issue. Cache.do didnt help, but waiting for a day did work! The next day the issue was resolved.

Another way to fix this caching issue without having to wait a day is to use a background script to flush the tables cache. In this knowledge article there is more about this issue and the background script I used:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0695145