When a developer assigns multiplebase templatesto a newdata templateinSitecore XM Cloud, any fields with thesame field name and field typearemergedinto a single field on content items based on that template.
If multiplebase templatesdefine a field with thesame name and type, Sitecore treats it as asingle merged fieldin the content item.
The field appearsonly oncein the content editor, andcontent authors can modify it just like any other field.
The field settings (such as default value, source, and validation rules) are inherited from thefirst base template in the inheritance order.
If different base templates define thesame field name but with different field types, Sitecore willtreat them as separate fields, which may cause issues.
Inherits from"SEO Data"and"Page Metadata"
Result:TheMetaTitlefield ismergedand appears only once in the content editor.
How Field Merging Works in XM Cloud:Example ScenarioBase Template 1: "SEO Data"Base Template 2: "Page Metadata"Final Data Template: "Landing Page"
Why Are the Other Options Incorrect?❌A. The field will not be displayed on the data item.
Incorrect because the fielddoes appearin the content editor, as long as at least one base template defines it.
❌B. Duplicate field names will appear on the data item.
Incorrect because Sitecoremergesidentical fields instead of displaying them multiple times.
However, if fields with thesame name but different typesexist, Sitecore maycreate conflicts.
❌C. XM Cloud will add a suffix to the field names to identify them.
Sitecore Templates and Field Inheritance– Sitecore Template Inheritance
How Sitecore Merges Fields from Multiple Base Templates– Field Merging in Sitecore
Best Practices for Data Template Design in XM Cloud– Sitecore Data Template Best Practices
References for Further Learning:.
