- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2023 01:10 AM
When opening the Change Schedule we are getting this error:
The error's full context is : TypeError: Cannot find function buildAncestorClassInfo in object
function () {...}. (sys_script_include.5d041e6767230300b410afa00585ef7e.script; line 73)
The affected script include : SoCModelBuilderSNC (read-only) and looking at the script :
it calls the buildAncestorClassInfo function in the ChangeCheckConflicts script include:
The function is obviously there, so my question is what might be causing it?
ChangeCheckConflicts (see attached for its script) is customized, and we can't revert it to OOB as it currently being used in several parts.
Any recommendation?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2023 03:30 AM
Thanks @Sandeep Rajput for the response.
As far as I can tell, nothing's wrong with the ACL config as well as the script itself in the script include.
Seems like that the only choice is to revert ChangeCheckConflicts to OOB and move the customizations to another custom script include to leverage the current custom functionalities.
Got it working after reverting it to OOB and moving the custom scripts elsewhere.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2023 02:04 AM
@jiral Check the ACLs for ChangeCheckConflicts script include. Also, compare the code of Custom version with the version available in the latest release spot any differences which is causing this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2023 03:30 AM
Thanks @Sandeep Rajput for the response.
As far as I can tell, nothing's wrong with the ACL config as well as the script itself in the script include.
Seems like that the only choice is to revert ChangeCheckConflicts to OOB and move the customizations to another custom script include to leverage the current custom functionalities.
Got it working after reverting it to OOB and moving the custom scripts elsewhere.