All Collections
Troubleshooting
Salesforce validation errors
Resolving validation errors - "You can't edit tab settings for DelegatedAccount, as it's not a valid tab."
Resolving validation errors - "You can't edit tab settings for DelegatedAccount, as it's not a valid tab."

Cause and solution to this Salesforce validation error

Valerio Chang avatar
Written by Valerio Chang
Updated over a week ago

Explanation of the error:

Users have reported the following to us:

  • If your source and target are both on or above the API version 50 (Winter ’21) and

  • you are deploying a profile that contains this in the source
    ​<tabVisibilities>
    ​<tab>standard-DelegatedAccount</tab>
    ​<visibility>DefaultOff</visibility>
    ​</tabVisibilities>

You will get the validation error:

You can't edit tab settings for DelegatedAccount, as it's not a valid tab.

This is happening because Salesforce API does not support DelegatedAccount in tabs. Please report this to Salesforce support.


Resolution:

If you are deploying from org to org, you can workaround this error by removing the DelegatedAccount custom object from your metadata filter. This will prevent the profile from retrieving the tab visibilities for this custom tab, and therefore not deploy this section.

If you are deploying from Git (where all components of a profile are retrieved) you can work around this and still deploy the Profile by:

  1. Downloading the deployment package, from the Download package button on the deployment summary page before the deployment.
    See here for more instructions:
    - How to replicate deployment errors with other tools?

  2. Edit the .profile file (using software that can view the XML such as Notepad, TextEdit or VS Code) to delete the four lines that reference standard-DelegatedAccount.

  3. Create a new comparison with Local files as the modified .profile file (with the valid package.xml) and deploy.

Hopefully this workaround will help you deploy your profile while this Salesforce metadata API bug is being investigated.

Disclaimer: This error is returned by Salesforce directly, rather than Gearset. Even so, we offer guidance based on our combined experience with the Metadata API. Where possible, we try to help guide you to fix or avoid this error. In the case that this isn't possible, we may need to direct you to Salesforce support for further clarification.

Did this answer your question?