Skip to main content

Resolving validation errors – "In field: application - no CustomApplication named standard__XXXX found"

How to resolve the "No CustomApplication named standard__XXXX" validation error when deploying permission sets.

Written by Richard Terry
Updated today

Note: standard__SalesCloudMobile has a unique issue.

If you are facing an issue with standard__SalesCloudMobile and have SalesCloud Mobile enabled in your orgs, take a look at this document.

Explanation of the error

This Salesforce error may occur when deploying a Permission Set or removing a Permission Set that includes a reference to a standard app "standard__XXXX" in the applicationVisibilities field.

This is caused by the following metadata block in the Permission Set XML:

<applicationVisibilities>
<application>standard__AdvancedTherapyManagement</application>
<visible>true</visible>
</applicationVisibilities>

Salesforce will let you enable standard apps in Permission sets even if the org does not have the standard app enabled.

This can be done via the UI, but will trigger a validation error when you try to deploy it via the metadata API.

Resolution

To resolve this error we need to remove the assigned app from the permission set

  1. In your source org open the permission set that is triggering this error.

  2. Open the Assigned Apps

  3. Select edit to see what Assigned apps are enabled for the permission set.

  4. Remove the standard app that is triggering the error.

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?