GlideTableDescriptor is not allowed in scoped applications error - cloned form widget in scoped application its not working

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-16-2019 08:11 AM
Hi, I am trying to update a field back from widget's server script to the incident table in scoped application when i click on a button, all my widgets and table are in scoped app except form widget by that time i am getting error like "Write operation against 'x_70916_ticket_ticketing_app_table' from scope 'rhino.global' has been refused due to the table's cross-scope access policy". - Unable to write scoped table by clicking on a button (ng-click).
Later i cloned form widget into my scoped application and tried but now getting "GlideTableDescriptor is not allowed in scoped applications" and form is not working.
So can anyone suggest me what actions can take on this issue or is there any other alternative way to update a table field in scoped application through service portal upon clicking on a button.
- Labels:
-
Scoped App Development
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-16-2019 08:14 AM
Hi Vinodha,
Please go through the below threads, which might be helpful to you.
1. https://community.servicenow.com/community?id=community_question&sys_id=07a433e2dbd957003882fb651f9619bc
2. https://community.servicenow.com/community?id=community_question&sys_id=b3a00765db98dbc01dcaf3231f96198e
Hope this helps. Please mark the answer Correct?helpful based on the instance.
Regards,
Amlan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-25-2020 07:10 AM
If you still have this issue, what warning or error messages are in the system log?
I had a similar issue with a record producer accessed through the Service Portal. I opened the system log (syslog.list) and searched the "Message" for "*glidetransaction" ("GlideTableDescriptor" in your case) created recent enough to capture the error. This indicateed the GlideRecord that was not allowed. I had default values of the record producer variables similar to the errors.
Because you had an issue before cloning, you might also access constraints that require you review the ACL records.
Please mark this response as the answer if it resolves your issue.