question Re: Cloning a Taxonomy Issue in Employee Slate and Employee Center forum

Cloning a Taxonomy Issue

stevemkuk — Fri, 04 Feb 2022 09:59:10 GMT

I am trying to clone the Employee Taxonomy on Employee Center.

When I click on Clone a box appears asking for the name of the new copy

I enter and Name and click on OK and apart from the OK box turning blue nothing happens.

The box just stays on screen and eventually I click the X on the box to close the pop box as the Cancel button does nothing either!

I have tried to repair the application but makes no difference.

If I click OK without entering a name still nothing happens, no errors or messages.

I am using my admin account

Can anyone offer any assistance?

Thanks

Steve

Re: Cloning a Taxonomy Issue

Prasad Pagar — Fri, 04 Feb 2022 10:12:30 GMT

Hi @stevemkuk

Check if you have any errors in browser console

Thank you
Prasad

Re: Cloning a Taxonomy Issue

Rob Sestito — Fri, 04 Feb 2022 13:46:38 GMT

Hey Steve,

It may be random - but when was the last time you cleared your browser cache?

Maybe give that a shot, close all browser tabs down, restart and try again. See if the same thing keeps happening to you.

I know that having too much clogged cache on the browser can make things not work properly in random ways. Maybe that is keeping you from moving forward.

I would start with that real quick along with what Prasad said about checking if you are getting errors within your browser console.

Keep us posted,

-Rob

Re: Cloning a Taxonomy Issue

stevemkuk — Fri, 04 Feb 2022 15:02:22 GMT

Unfortunately clearing the cache didn't change anything.

I Get the following console errors

First I get the following when I click on Clone

dirty form focus
VM790:3 Uncaught SyntaxError: Unexpected identifier
at eval (<anonymous>)
at evalScript (js_includes_doctype.jsx?v=01-12-2022_1753&lp=Tue_Feb_01_09_49_10_PST_2022&c=16_464:84:29)
at GlideModal._evalScripts (js_includes_last_doctype.jsx?v=01-12-2022_1753&lp=Tue_Feb_01_09_49_10_PST_2022&c=16_464:7749:1)
at GlideModal._renderFromAjax (js_includes_last_doctype.jsx?v=01-12-2022_1753&lp=Tue_Feb_01_09_49_10_PST_2022&c=16_464:7555:6)
at e._responseReceived (js_includes_doctype.jsx?v=01-12-2022_1753&lp=Tue_Feb_01_09_49_10_PST_2022&c=16_464:16029:6)
at e._processReqChange (js_includes_doctype.jsx?v=01-12-2022_1753&lp=Tue_Feb_01_09_49_10_PST_2022&c=16_464:15887:6)
evalScript @ js_includes_doctype.jsx?v=01-12-2022_1753&lp=Tue_Feb_01_09_49_10_PST_2022&c=16_464:84
_evalScripts @ js_includes_last_doctype.jsx?v=01-12-2022_1753&lp=Tue_Feb_01_09_49_10_PST_2022&c=16_464:7749
_renderFromAjax @ js_includes_last_doctype.jsx?v=01-12-2022_1753&lp=Tue_Feb_01_09_49_10_PST_2022&c=16_464:7555
_responseReceived @ js_includes_doctype.jsx?v=01-12-2022_1753&lp=Tue_Feb_01_09_49_10_PST_2022&c=16_464:16029
_processReqChange @ js_includes_doctype.jsx?v=01-12-2022_1753&lp=Tue_Feb_01_09_49_10_PST_2022&c=16_464:15887
XMLHttpRequest.send (async)
_sendRequest @ js_includes_doctype.jsx?v=01-12-2022_1753&lp=Tue_Feb_01_09_49_10_PST_2022&c=16_464:15876
_makeRequest @ js_includes_doctype.jsx?v=01-12-2022_1753&lp=Tue_Feb_01_09_49_10_PST_2022&c=16_464:15848
(anonymous) @ js_includes_doctype.jsx?v=01-12-2022_1753&lp=Tue_Feb_01_09_49_10_PST_2022&c=16_464:15824
setTimeout (async)
_getXML0 @ js_includes_doctype.jsx?v=01-12-2022_1753&lp=Tue_Feb_01_09_49_10_PST_2022&c=16_464:15824
getXML @ js_includes_doctype.jsx?v=01-12-2022_1753&lp=Tue_Feb_01_09_49_10_PST_2022&c=16_464:15813
render @ js_includes_last_doctype.jsx?v=01-12-2022_1753&lp=Tue_Feb_01_09_49_10_PST_2022&c=16_464:7536
copyTaxonomyTree @ taxonomy.do?sys_id=1f5d5a40c3203010069aec4b7d40dd93&sysparm_record_target=taxonomy&sysparm_record_row=1&sysparm_record_rows=1&sysparm_record_list=ORDERBYname:522
onclick @ taxonomy.do?sys_id=1f5d5a40c3203010069aec4b7d40dd93&sysparm_record_target=taxonomy&sysparm_record_row=1&sysparm_record_rows=1&sysparm_record_list=ORDERBYname:362
taxonomy.do?sys_id=1f5d5a40c3203010069aec4b7d40dd93&sysparm_record_target=taxonomy&sysparm_record_row=1&sysparm_record_rows=1&sysparm_record_list=ORDERBYname:1

Then I get the following when I click on OK or Cancel

Uncaught ReferenceError: invokePromptCallBack is not defined
at HTMLButtonElement.onclick (taxonomy.do?sys_id=1f5d5a40c3203010069aec4b7d40dd93&sysparm_record_target=taxonomy&sysparm_record_row=1&sysparm_record_rows=1&sysparm_record_list=ORDERBYname:1:1)
onclick @ taxonomy.do?sys_id=1f5d5a40c3203010069aec4b7d40dd93&sysparm_record_target=taxonomy&sysparm_record_row=1&sysparm_record_rows=1&sysparm_record_list=ORDERBYname:1

Re: Cloning a Taxonomy Issue

Rob Sestito — Fri, 04 Feb 2022 15:53:24 GMT

Hmmm,

I am going to go with that this could be an actual system/application error issue.

If anyone else can assist here, great! Otherwise, a ticket to SN HI Portal may be needed to check on this.

Very sorry I could not help more.

-Rob

Re: Cloning a Taxonomy Issue

Daniel Pettet — Mon, 07 Feb 2022 05:30:58 GMT

The JS errors suggest an application error (client/server).

I also have an open case and have just escalated it to try and prioritise a fix.

But the next step is a challenge too. Anyone worked out how to get the EC portal to use a new taxonomy?

Re: Cloning a Taxonomy Issue

CasperJT — Fri, 18 Feb 2022 08:02:53 GMT

Getting the EC to use a different taxonomy should 'just' be to go to the portal page for EC and edit the Taxonomy related list:

Re: Cloning a Taxonomy Issue

kanoe1 — Fri, 01 Jul 2022 23:50:10 GMT

Hi there,

I'm experiencing the same issue. Were you able to resolve? If so, what was the resolution?

Thanks,
Kanoe

Re: Cloning a Taxonomy Issue

Prakhar26 — Mon, 04 Jul 2022 05:48:18 GMT

I think it's resolved. As of now I am not able to replicate the issue and everything seems to work fine.
Which version of Employee center apps are you using?

Re: Cloning a Taxonomy Issue

GoBucks — Mon, 25 Jul 2022 22:31:50 GMT

@Daniel Pettet did Support provide a fix? I am also experiencing the same issue as the original poster @stevemkuk

San Diego Patch 4
Employee Center 25.0.3 installed

When I try to clone the OOTB "Employee" taxonomy by clicking the "Clone" button and then filling out the following modal's "New Taxonomy Name" field, once I click the OK button, absolutely nothing happens.

Re: Cloning a Taxonomy Issue

GoBucks — Tue, 26 Jul 2022 14:13:01 GMT

@Prakhar was there a specific fix suggested for this? If you note my reply above, you can see that I'm still experiencing this issue.

Re: Cloning a Taxonomy Issue

GoBucks — Wed, 27 Jul 2022 15:36:26 GMT

Support helped me resolve this issue. Two options:

1) addressing a system property value by ensuring it is 'true' (OOTB, the property is true), OR

2) if the system property is chosen to be 'false', prior to the fix in Tokyo, one can edit the client script in the UI page of the modal.

Details on these options are here:

KB1005930 - Clone taxonomy is not working when "glide.ui.escape_all_script" is false

Re: Cloning a Taxonomy Issue

Brendan N1 — Sun, 06 Nov 2022 21:27:46 GMT

I also had this issue, though in my case I believe it was because I was attempting to clone into a custom scope, and there were cross scope errors blocking the clone. To get around this, I ran the function called by the Clone UI action manually via background script:

// Get employeeTaxonomyID from the default Employee taxonomy record var employeeTaxonomyID = "1f5d5a40c3203010069aec4b7d40dd93"; // Put your desired new taxonomy name here var newTaxonomyName = ""; gs.info(copyTaxonomyTree(employeeTaxonomyID, newTaxonomyName)); function copyTaxonomyTree(id, name) { var currentTaxonomyId = id; var newTaxonomyName = name; var newTaxonomyId = ''; var gr = new GlideRecord('taxonomy'); gr.get(currentTaxonomyId); if (gr.isValidRecord() && gr.canRead()) newTaxonomyId = new global.TaxonomyCopyUtil().copyTaxonomyTree(currentTaxonomyId, newTaxonomyName); return newTaxonomyId; }