- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-20-2025 02:16 AM
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-21-2025 11:36 PM
Hello @Bernard295C , thanks for your input. I verified the batch data, it was just fine.
I identified the issue was with the order of the script, that the batch input (u_action) was successfully captured in the log of the first script that got executed. So changing the order worked for me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-20-2025 02:24 AM
@DharshaniR wrote:This is the script I am using to log the input source fields(Action and IncidentNumber) in RTE entity mappings. I am able to get the log for ticket number but not for action. Any weird reason why?(function(batch, output) {for (var i = 0; i < batch.length; i++) {var a = batch[i].u_action;var b = batch[i].u_ticketnumber;gs.log('RTE PD:a ' + a);gs.log('RTE PD:b ' + b);})(batch, output);
Hello!
If the script isn't logging the u_action field, check the field name for accuracy, ensure it has values, confirm script scope, and verify batch data. Logging the entire batch element might help identify the issue:
javascript
gs.log('RTE PD:Batch Element ' + JSON.stringify(batch[i]));
I hope this helps!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-21-2025 11:36 PM
Hello @Bernard295C , thanks for your input. I verified the batch data, it was just fine.
I identified the issue was with the order of the script, that the batch input (u_action) was successfully captured in the log of the first script that got executed. So changing the order worked for me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-20-2025 09:34 PM