Metadata Type CustomObjectTranslation Does Not Support PersonAccount
Last updated 2022-02-10 ·Reference W-827210 ·Reported By 44 users
Summary
When deploying CustomObjectTranslation or Translation page layouts, you can get the below error as Person Accounts are not considered custom objects by the Metadata.
moduleapi.isv.packaging.exception.PackageExportException: Failure(s) during upload:
package.xml:Cannot retrieve translation for object:PersonAccount
Repro
1. Enable Person Account feature
2. Create person account page layouts
3. Extract the metadata using the package.xml below
<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
<types>
<members>Account-de</members>
<name>CustomObjectTranslation</name>
</types>
<types>
<members>PersonAccount-Admin Privatperson Layout</members>
<members>PersonAccount-Gewerblich Selbstständige Layout</members>
<members>PersonAccount-Privatperson Layout</members>
<name>Layout</name>
</types>
<version>31.0</version>
</Package>
4. Retrieved metadata files cannot be deployed again and fail with the following error message:
“Invalid layout type: Person Account”.
The error is caused by the page layout translations for the PersonAccount in the Account-de.objectTranslation file:
<layouts>
<layout>Admin Privatperson Layout</layout>
<layoutType>PersonAccount</layoutType>
<sections>
Workaround
1. Remove the language translations from their package/change set.
2. Remove all custom fields with a parent object "Person Account" from their package.
Reported By (44)
























Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.