
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-27-2016 05:35 PM
...only works once?
i.e. when you change one of the fields, it fires. But if you then change the field again to a different value, it doesn't fire a second time (or third, fourth, etc).
Seems like a bug? Or is it a limitation?
Solved! Go to Solution.
- Labels:
-
Scripting and Coding

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-27-2016 06:04 PM
Apologies - I just found the issue. I didn't set these up, I'm just troubleshooting. I only just realised they weren't configured to "Always replace" on the Setter field definition. Sorry guys

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-27-2016 05:50 PM
Hi Steve,
Can you take a look at the field watcher and see if it reveals anything.
http://wiki.servicenow.com/index.php?title=Field_Watcher

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-27-2016 05:58 PM
I just see that it fires only once (the first time):
10:54:16 (809)DATA LOOKUP - onchange of ticket.subcategory
Basically, we're using the Category and Subcategory to auto-set the Assignment Group. So you pick Firewall, and it gets assigned to Networking, but if you change your mind and then select Server as the category instead, the Assignment Group doesn't change to Infrastructure (or whatever), it remains Networking.
Almost feels like it will only set the value if it's current value is null. i.e. even if I open an old ticket where the Assignment Group is already set, and I select a new Catagory, the change doesn't happen. So it's not that it only does it once on a new record or anything like that.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-27-2016 05:58 PM
Can you attach a snapshot of your data lookup definition.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-27-2016 06:04 PM
Apologies - I just found the issue. I didn't set these up, I'm just troubleshooting. I only just realised they weren't configured to "Always replace" on the Setter field definition. Sorry guys