Delete records from scoped application

Arun Chauhan
Giga Contributor

Hello,

We are publishing one of our integration application to ServiceNow store. To publish the application on the store, I am retrieving the update set XML on the ServiceNow instance. I am facing an issue while retrieving.

 Whenever I retrieve the update set XML, I can see some unwanted records in the ‘Application Files’ list. These records are created by default and I am not able to delete these. Please check below screenshot:

find_real_file.png

 I tried deleting them through Background scripts and Fix scripts but I am not able to delete these. Please note these records belongs to 'Table Subscription Configuration' table. Below is my script:

var gr = new GlideRecord('ua_table_licensing_config');
gr.addQuery('sys_id', '105693784f25d34078c5fd218110c794');
gr.query();
while (gr.next()) {
gs.debug("Deleting record with name : " + gr.name.toString());
gr.deleteRecord();
}

Even I added ‘Can delete’ in the Application Access for ‘Table Subscription Configuration’ table and added an ACL with ‘admin’ role on the table with delete operation. But the errors remains same.

I am getting below error :

*** Script: [DEBUG] Deleting record with name : x_sapo_iiq_catalog_spnt_transactions

Background message, type:error, message: Invalid delete of subscription management attributes

Please suggest.

 

1 ACCEPTED SOLUTION

Pradeep Sharma
ServiceNow Employee
ServiceNow Employee

Hello Arun,

 

You can either deactivate the records (If you have active checkbox) or move them to global scope if this is not required in your application scope.

 

Thanks,

Pradeep Sharma

View solution in original post

7 REPLIES 7

Thanks Pradeep for the suggestion. One more issue I am facing while publishing the application to the ServiceNow store.

I am getting error 'You do not own the vendor prefix for this scope'. The application is a private scoped application in a scope 'x_sapo_xx_catalog'. Our vendor prefix was 'sapo' when we developed the application on Eureka release but later on it changed to 'sap'. I am getting error whenever I try to publish the application from a instance with vendor prefix 'sap'.

I tried publishing from two different instances and I am getting the same error. The interesting thing is we did certification for Helsinki and Istanbul releases for the same application and at that time there was no issue, irrespective of we did publish from an instance with prefix 'sap'. 

Please suggest.

Hello Arun,

 

I just got a confirmation from my team that this issue is resolved. Please let me know in case you are still blocked.

 

Thanks,

Pradeep Sharma

Thanks Pradeep. Publish is working now.