Skip to main content

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

This error occurs when a Permission Set references the unrecognized Sales Cloud Mobile app

David Martin avatar
Written by David Martin
Updated over a week ago

Explanation of the error

This Salesforce error may occur when deploying a Permission Set or removing a Permission Set that includes a reference to the Sales Cloud Mobile app in the applicationVisibilities field.

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

<applicationVisibilities>
<application>standard__SalesCloudMobile</application>
<visible>true</visible>
</applicationVisibilities>

The issue arises because Salesforce does not recognise standard__SalesCloudMobile as a valid Custom application in all orgs - especially if the app has not been enabled or is unavailable in the target org.

Resolution

To resolve this issue, follow these steps:

1. Remove the Sales Cloud Mobile visibility entry from the metadata

Remove the Sales Cloud Mobile visibility entry from the metadata

Manually delete the following lines of code from your local copy of the Permission Set XML file:

<applicationVisibilities>
<application>standard__SalesCloudMobile</application>
<visible>true</visible>
</applicationVisibilities>

2. Deploy the remaining metadata

Use Gearset to deploy the rest of the Permission Set without the Sales Cloud Mobile reference.

3. Manually add the Sales Cloud Mobile visibility in the target org

Once the deployment is complete:

  • Navigate to the Permission Set or Muting Permission Set in the target org.

  • Go to Assigned Apps and click Edit.

  • Move the Sales Cloud Mobile (standard__SalesCloudMobile) to Enabled Apps list and click on Save.

Useful resources

This is a Known Issue in Salesforce, so we'd encourage users to refer to the official documentation that outlines the summary, steps to reproduce, as well as current workaround.

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?