Correct, the ANS spec does not "require" that they are unique. Composer "tries" to, but there are edge cases around cut & paste and clipboard that are gaps here.
I was tracking this because in theory we could use the new validation service to detect and warn on this.
I assume you mean the "content_elements" items inside the ANS when you refer to "duplicated content". Can you clarify if that's what you mean or are you referring to something else?
Madsack has been using Arc XP for a few years, this is a client that relies heavily on backend scripts to automate tasks. I believe that many clients will follow this path of automation as their solutions evolve.
In that context, they are having issues dealing with content because content element IDs are not unique.
I would like this feature to be reviewed and consider making these IDs unique.
Paula Molinero
Correct, the ANS spec does not "require" that they are unique. Composer "tries" to, but there are edge cases around cut & paste and clipboard that are gaps here.
I was tracking this because in theory we could use the new validation service to detect and warn on this.
Hi Fatih,
Yes, I'm referring to the content element items inside the ANS. It was confirmed to me that they are not unique IDs.
Hi Paulo,
I assume you mean the "content_elements" items inside the ANS when you refer to "duplicated content". Can you clarify if that's what you mean or are you referring to something else?
Madsack has been using Arc XP for a few years, this is a client that relies heavily on backend scripts to automate tasks. I believe that many clients will follow this path of automation as their solutions evolve.
In that context, they are having issues dealing with content because content element IDs are not unique.
I would like this feature to be reviewed and consider making these IDs unique.