Content Fragments with a Nested Composite Multifield

[#1]

Request for Feature Enhancement (RFE) Summary:	Ability to Save a Content Fragment with a Nested Composite Multifield
Use-case:	1. Add a nested composite multifield to a content fragment model. 2 . Add content to the fragment then try to save.
Current/Experienced Behavior:	Cannot save the content fragment with the nested composite multifield.
Improved/Expected Behavior:	Ability to save the content fragment with the nested composite multifield.
Environment Details (AEM version/service pack, any other specifics if applicable):	Adobe Experience Manager 6.5.15.0
Customer-name/Organization name:	Olu Oladipo / Verizon
Screenshot (if applicable):
Code package (if applicable):

multifield.png ‏38 KB

[#2]

I am guessing but requesting others to feel free to share your thoughts. Content fragments having composite or nested muktifields which again are composite are tricky in nature. May be the enhancement can support saving the data in desired format, but the ability to query using graphql may become an issue since graphql requires schema of the cf to be known before hand and introducing custom structure in between may break the design, and perhaps is the reason Adobe advises using nested content fragments to accomplish the same. I agree from an authoring standpoint this is a valid use case but Adobe may have to provide alternative means to meet both use cases.

Thanks 

[#3]

@olugboyega 

Thanks for proposing this idea

This has been reported to the engineering under the internal reference SITES-15648. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.

[#4]

Thank you, @kautuk_sahni