[SalesForce] Payload Error while Deploying Global Value Set with Language Translations in Production

I have a Custom Object that includes a Picklist which uses Global Value Set. Now, while deploying this to Production, it's giving me Payload Error while validating the Change Set.

Missing feature, Details: Installing this package requires the following feature and its associated permissions: Language Translation

My Change Set only contains the Picklist Field, Global Value Set, and the Language Translations. The Custom Object is already deployed in Production.

Is there a reason why I am unable to deploy this? TIA

Best Answer

The Issue was that I didn't check whether the Translations are Enabled in my Target Org.

You can set that by Going to Setup > Translation Setting > Enable.

Related Solutions

[SalesForce] Best way to support Language Translation on Record level

@Charles : Yes, I had gone ahead with the custom object option as there was not any room of making API calls just for translations. But did create per column for every language. in my case there were 12, so having 12 more columns on an object was better..sicne overall, record consumption would still be 2kb/record

Thanks JJ

[SalesForce] Error: Cannot change which global value set this picklist uses

I don't know how and why but when I changed the global picklist API name to match the field name. It worked!

<fields>
        **<fullName>CallStatus_MDE__c</fullName>**
        <externalId>false</externalId>
        **<globalPicklist>CallStatus_MDE</globalPicklist>**
        <label>Status</label>
        <required>false</required>
        <trackFeedHistory>false</trackFeedHistory>
        <trackHistory>false</trackHistory>
        <trackTrending>false</trackTrending>
        <type>Picklist</type>
    </fields>

Best Answer

Related Solutions

[SalesForce] Best way to support Language Translation on Record level

[SalesForce] Error: Cannot change which global value set this picklist uses

Related Topic