Content Fragment multifield

Forum|Forum|1 year ago
March 5, 2025
5 replies
838 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

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.

kautuk_sahni

Employee

@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

martin_ecx_ioAccepted solution

New Participant

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.

M

Megha_kumari

New Participant

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.

daniel-strmecki

New Participant

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