After code deployment to AEM, jcr:primaryType gets... - Adobe Experience League Community

View profile · 27-01-2021

Hi Everyone, we tried to implement synonyms in AEM. We followed the steps in this blog:

https://www.albinsblog.com/2020/05/how-to-enable-search-synonyms-in-aem-with-lucene.html

It is already working on the local however to implement this changes to AEM instance, we need to add the changes to the solution and build. After building the solution, it is no longer working in AEM instance.

Expectation:

Actual Result:

I would like to know if you have encountered this issue?

0424 · ‎31-01-2021

Hi ,

This issue we recenty encounter and its because when we package the oak synonynms it will have only one content.xml file which includes all nodes and its types information like nt:unstructured.

So instead of putting same structure in IDE for build we need to add content.xml in each level with node details primary type.

Like in your case content.xml on same level of analyser folder and need to put the .content.xml whith primaryType as nt:unstructure, and instead of <jcr:root> you need to add <analyser>. Same for other node also.

Please let me know if you require more info 🙂

0424 · ‎27-01-2021

It seems the primary type has changed from a file to a folder here. Please click on the folder and check the properties. You can modify the jcr:primaryType=sling:Folder to the correct primaryType by doing a comparison on local setup.

Usual types can be:

sling:OsgiConfig, dam:Asset etc.

Also share the logs here which can help identify the issue further.

After code deployment to AEM, jcr:primaryType gets converted to nt:folder from nt:unstructured

Accepted Solutions (0)

Answers (2)

Answers (2)