Skip to main content

KI-51

Conflicting custom labels not correctly retrieved in non-namespace orgs

Created date

04/15/2021

Updated date

03/19/2025

Status

Done

Related work item(s)

PLTFM-534

Description

If a custom label exists in a non-namespace org with the same API Name as a Medical Information Cloud Content Management custom label (e.g., {CM_Due_Date}) or a CM_ or IM_ prefix, you will not be able to retrieve the conflicting custom label via API https://{instanceUrl}/services/apexrest/mvn/i18n/v1/labels

Affects Versions

MIC V10

Impacted capabilities

Content Management

Steps to Reproduce

  1. Create a custom label in a non-namespace org with the same API Name as a MIC-Content custom label (e.g., {CM_Due_Date}).

  2. Retrieve the new custom label via the I18N API (https://help.mavens.com/mic-content/en/documents/mcm-api.html) endpoint (https://{instanceUrl}/services/apexrest/mvn/i18n/v1/labels). The translation service does not correctly retrieve the custom label.

Workaround

Customers should avoid using duplicate names and prefixing custom labels with CM_ or IM_.

Fix version

Resolution notes

Salesforce released a new Labels Apex API that allows for dynamic retrieval of custom labels in Apex.