Why would client scripts stop working for one table?

davejr
Giga Contributor

For one table only in one environment today the client scripts are not working.

for example, in an onLoad client script,

I have to start the script box with onLoad() to get the code to execute,

and it is only for one table, (it is an extension of the task table)

but also the case for older client scripts for that table

I cannot see any change to the table itself to cause this.

1 ACCEPTED SOLUTION

Jim Coyne
Kilo Patron

You might have a script error in another Client Script or UI Policy that is failing and that will cause code which would normally run after that to not run.



You can use your browser's developer tools/console to see if an error is happening, or take a look at this post - Internet Explorer Really Can Be Your Friend


View solution in original post

12 REPLIES 12

Pradeep Sharma
ServiceNow Employee
ServiceNow Employee

Hi David,



You can check the history to see how it got updated. Please find the screenshot attached for your reference.


Viewing a Record's Change History - ServiceNow Wiki


Screen Shot 2015-03-17 at 12.15.38 AM.JPG


The client scripts that were not changed also stopped working.


The feature that automatically executes the onLoad (or onChange) code for that table stopped working.


Thank you, but it is not catalog client scripts, and our eureka upgrade was months ago. This is more recent.