Rename the internal name of a Content Fragment variation in AEM
Adobe Experience Manager (AEM) updates only the display title (jcr:title) when a Content Fragment variation is renamed, while the internal variation name under jcr:content/data remains unchanged because it’s set when the variation is created. To resolve the issue, create a new variation with the desired internal name, copy the content, update its references, and remove the old variation after validation.
Description description
Environment
Adobe Experience Manager (all versions)
Issue/Symptoms
- Renaming a Content Fragment variation in the Content Fragment editor updates only its display label (
jcr:title). - The internal variation name, which is the node name under
jcr:content/data, remains unchanged. - Components and headless APIs, such as GraphQL, use the internal name to reference the variation.
- There is no supported way to directly change the internal name of an existing variation after it’s created.
Root cause
The internal name of a Content Fragment variation is set when the variation is created and is used as an identifier by AEM components and APIs. Renaming the variation in the UI updates only the display label (jcr:title), not the internal node name. This behavior is by design and maintains stable references for headless and component-based integrations.
Resolution resolution
Follow the steps below to resolve the issue:
- In the Content Fragment editor, create a new variation with the desired internal name and title.
- Manually copy the content from the original variation to the new variation.
- Update all references, such as pages, components, and GraphQL queries, to use the new variation name.
- Verify that all functionality works as expected with the new variation name.
- After completing the validation, remove the old variation to avoid confusion.