How to override EmployeeTaxonomyUtilSNC with 1 sys_id of taxonomy I want to replace

[bbf35621]

Hi all!

I am working on connected content migration from Dev to Test following the ServiceNow doc. I want to deactivate the OOB employee taxonomy and use the taxonomy I created instead. So EmployeeTaxonomyUtilSNC is an OOB script include and it should never be edited. So I cloned the EmployeeTaxonomyUtil and make some custom change in initialize function like this,

Will that script override the EmployeeTaxonomyUtilSNC?

[Mark Roethof]

Hi there,

Why would you want to override the Script Include? Can you provide some background on that?

If it's just the out-of-the-box Taxonomy, why not deactivate it? And add your new Taxonomy. That has nothing to do with a Script Include.

Kind regards,
Mark

[bbf35621]

The issue was that the taxonomy with connected contents I created didn't appear in the portal in the Test instance when I migrated from Dev to Test and I only saw the Employee taxonomy instead of the custom taxonomy. So I need to deactivate the Employee taxonomy and use my custom taxonomy. So it was the update set capture issue for connected contents. So the architect guy suggested I use that SN doc by running a fixed script instead of using update sets to force "Add to the update set". It is my first time building taxonomy and adding connected content.

[Mark Roethof]

That's still no argument to do something with a Script Include.

That the Taxonomy did not come up while promoting through update set could be because not everything was captured. Taxonomy and topics will be captured in update set, though connected content = data, and by default not captured in an update set. You could add the connected content to your update set using the out-of-the-box create application file, perfectly fine to do so.

At the ServiceNow Academy it was mentioned exporting XML/importing XML for connected content, although I find that a bit of an unprofessional approach if you would need to do that on production. 

If the update set was correct, it could also well be a cashing issue. Again: nothing to do with a Script Include.

Kind regards,
Mark

[Sarah Travis]

As stated in the ServiceNow article on migrating topics and connected content linked in the OP: 

• This fix script is provided OOB, it refers to an OOB script include called "EmployeeTaxonomyUtil" and fetches taxonomy from that script include and runs for it. If you want to run for different taxonomy, you just need to update the script include with that taxonomy sys_id.