Loading

Understanding XMD Retrieval Behavior When Dataset and Lens Share the Same API Name

Дата публикации: Jun 8, 2026
Описание

Extended Metadata (XMD) files in CRM Analytics define formatting and display customization for datasets and lenses.

A scenario can arise where both a dataset and a lens can share the same API name. This can lead to confusion during metadata retrieval or deployment because the retrieval process does not distinguish between the dataset’s XMD and the lens’s XMD when the names match and its retrieve the available XMD of the API name regardless of strict to datasets and lenses. And the reason for this flexibility is for the Internal development and entity level reference of its components.

When retrieving wave XMD through the Metadata API, the system will return the XMD associated with the dataset and it’s type if both a dataset and a lens share the same API name. This is due to the current platform design.

This is expected system behavior, but developers who are unaware of it may experience discrepancies during deployments or find that the retrieved XMD is not the one intended.

Решение

To avoid this conflict, assign unique API names to your datasets and lenses, or follow the guidance below if identical names cannot be avoided.


If sharing the same API name is unavoidable, explicitly retrieve or deploy each component with its correct metadata reference, or remove the unintended XMD, which is retrieved from source org.

Establish and follow clear naming conventions within development teams to maintain long-term consistency.

Номер статьи базы знаний

005132047

 
Загрузка
Salesforce Help | Article