Content Fragment multifield | Community
Skip to main content
S
SarahBo2
Level 2
March 5, 2025
Solved

Content Fragment multifield

  • March 5, 2025
  • 5 replies
  • 845 views

Hi in my project Adobe Experience Manager as Cloud Service,
We're creating content fragment models. Is it possible to have multifield with different field type within the cf?
Multifield Structure Example:

multifield:

    textfield

    pathfield

    richtext

 

Thank you,

Sarah

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by martin_ecx_io

I'd agree with the others - nested CFs is generally the way to go and with the new CF editor view, navigating between them is much simpler than it used so be.

 

Sticking to standard field types is particularly important if you're accessing it via GraphQL as it understands how to putput standard content, but a custom multifield wouldn't be able to be output there.

5 replies

daniel-strmecki
Community Advisor and Adobe Champion
daniel-strmeckiCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
March 5, 2025

Hi @sarahbo2,

in the old CF editor, it is possible with a custom multifield. However, I haven't yet seen a solution for it for the new CF editor. It looks like Adobe is moving away from this approach and suggests creating separate CFs for such use-cases.

 

Good luck,

Daniel

    M
    Megha_kumari
    Level 2
    March 6, 2025

    Hi @sarahbo2 ,

    I recently faced a similar requirement in AEM as a Cloud Service, where I needed a multifield inside a Content Fragment Model (CFM) that included different field types.

    Since CFMs don’t support a multifield-like structure natively, I found that the best way to achieve this is by using a Nested Content Fragment Model.

      martin_ecx_io
      Community Advisor and Adobe Champion
      martin_ecx_ioCommunity Advisor and Adobe ChampionAccepted solution
      Community Advisor and Adobe Champion
      March 7, 2025

      I'd agree with the others - nested CFs is generally the way to go and with the new CF editor view, navigating between them is much simpler than it used so be.

       

      Sticking to standard field types is particularly important if you're accessing it via GraphQL as it understands how to putput standard content, but a custom multifield wouldn't be able to be output there.

        kautuk_sahni
        Community Manager
        kautuk_sahniCommunity Manager
        Community Manager
        April 16, 2025

        @sarahbo2 Did you find the suggestions helpful? If you need more information, please let us know. If a response resolved your issue, kindly mark it as correct to help others in the future. Alternatively, if you discovered a solution on your own, we'd appreciate it if you could share it with the community. Thank you !

        Kautuk Sahni
        Terms & ConditionsAccessibility statement

        Loading footer...