nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Copied node has cn:name equal to nodeid

CologneClaret

Hi all,

we have ACS 5.2.3 installed and have an issue when copying nodes using rules or scripts.

We have noticed that when a node is copied the new target node is not named after the source node. The cn:name is the nodeid.

This does not happen if we select in Alfresco Share and copy.

Has anyone else seen this issue and knows of a fix?

Thank you.

Find more posts tagged with

Alfresco Content Services

Accepted answers

CologneClaret

Thank you afaust. Sorry about the delayed response. I hadn't seen a message in my email.

The issue appeared to be due to some misconfiguration on the Alfresco server. Everything was working, and then suddenly for no apparent reason the ID issue appeared. It then disappeared again and then reappeared. There had been changes made to configuration files of which I was unaware. This was later resolved by the support company who had added new tools to the system :-(.

All comments

afaust

This is not really an issue, but rather a different behaviour for different APIs in use. The CopyService Java API has a copy and a copyAndRename operation. The simple copy operation will drop the name, so it defaults to the ID.

If your scripts use the ScriptNode.copy operation, they should internally be using copyAndRename, and then it would be a bug if the name is not based on the source node. This is also what Alfresco Share uses indirectly to perform a copy. If your scripts / rules somehow use (custom) Java code that uses the simple copy operation, then it's not a bug, rather the incorrect operations are used.

CologneClaret

EddieMay

Hi @CologneClaret ,

Glad you have it sorted & thanks for updating your post - helpful to other users.

Take care,