Not able assigned child change request after Yokohama release
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-21-2025 01:20 AM - edited ‎05-21-2025 01:30 AM
Hi All,
getting an issue while assigning a child change request to my current change request. issue is happend just after Yokohama release,
please suggest to how to troubleshoot.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-21-2025 01:43 AM
Please provide more details and screenshots to understand better your situation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-21-2025 01:46 AM
so what debugging did you perform?
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-21-2025 01:49 AM
Have you tried addind via a script?
var child = new GlideRecord('change_request');
if (child.get('sys_id_of_child')) {
child.parent = 'sys_id_of_parent';
var result = child.update();
gs.print('Update result: ' + result);
}
If this works, problem is likely UI or client script related. If it fails, deeper business rule or ACL issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-21-2025 03:39 AM
thank your response but we are not using script, instead we are just clicking on the edit button in child change related list after adding change request from the selected box it will not get added to parent change