Some PDIs are currently unavailable, and PDI actions are paused. View the latest updates here. Read More

Client Script onChange is not triggering at all

colin-lucwe
Tera Contributor

Hi everyone,

I’m currently facing an issue with a Client Script onChange script that is not being executed at all.

The strange thing is that it is not a logic issue inside the script — the script does not seem to trigger in the first place. I already added logging statements at the very beginning of the Client Script, but nothing appears in the console/logs when I change the field value.

Has anyone experienced a similar issue or has an idea what could prevent an onChange Client Script from firing?

Things I already checked:

The Client Script is active
The field name is correct
The script type is set to onChange
I tested with simple log statements at the first line
The field value is definitely changing
Are there any less obvious reasons why an onChange Client Script would not trigger at all? For example, any configuration settings, UI policies, field types, client conditions, or other dependencies that could block it?

Any hints or troubleshooting tips would be highly appreciated. Thanks!

1 REPLY 1

Ankur Bawiskar
Tera Patron

@colin-lucwe 

script please along with screenshots of the client script config and which form

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