Hi solva87,I have also faced similar issue in content data schema and had to add pksequence in the schema to avoid this. But now, I am also getting the same error(invalid XML) while using any field in the javascript template with syntax as <%= content.@attributeName %>Was you able to resolve this is...