Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

We are facing an data loss on issue on reload of a content fragment with the custom composite multifield in AEM 6.5.

Avatar

Level 1

Hi Everyone,

 

We are facing an data loss  issue on reload of a content fragment with the custom composite multifield in AEM 6.5.

 

Issue description.

 

when we reload the content fragments , We are seeing the 2 post requests  <cfm-path>/cfm.content.json in network tab of developer tools, first request is having all the content fragments fields value except the composite multifield values(for composite multifield, the OOTB call is taking only the first field value of the composite multifield). This call is causing the data loss in JCR.

 

Any one has faced similar issue and any one have the solution to include/inject the all the custom composite multifield values to the <cfm-path>/cfm.content.json post request.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@pavandeshi 

 

Composite multifields are not supported OOTB. Hence, Adobe support might not be able to help you.

Recommendation is to create a hierarchy of CF instead, i.e. One set of the multifield should be a separate CF.

 

The parent CF should now reference these individual CF via CF multifield. 

You might also encounter issues with GraphQL queries with the current set-up. 

 

In case you need to go with composirte multifield, then please check if following links help

https://experience-aem.blogspot.com/2018/10/aem-6420-assets-content-fragments-coral-3-composite-mult... 

https://jimfrenette.com/aem/content-fragments/composite-multifield/

 


Aanchal Sikka

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

@pavandeshi 

 

Composite multifields are not supported OOTB. Hence, Adobe support might not be able to help you.

Recommendation is to create a hierarchy of CF instead, i.e. One set of the multifield should be a separate CF.

 

The parent CF should now reference these individual CF via CF multifield. 

You might also encounter issues with GraphQL queries with the current set-up. 

 

In case you need to go with composirte multifield, then please check if following links help

https://experience-aem.blogspot.com/2018/10/aem-6420-assets-content-fragments-coral-3-composite-mult... 

https://jimfrenette.com/aem/content-fragments/composite-multifield/

 


Aanchal Sikka

Avatar

Administrator

@pavandeshi Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.



Kautuk Sahni