Error overview
You may run into this Salesforce validation error when deploying changes to one of these standard objects, in particular VoiceCall, VideoCall, OrderSummary, or less commonly, CollaborationGroup - we have not seen this error happening on any other objects.
We've seen users running into this error when one of the mentioned objects (e.g. VoiceCall) is included in their PR (pull request), and the PR fails the validation in Gearset Pipeline.
An example of the error message in our app would look as below:
Message reported by Salesforce: "Entity cannot be untracked."
Metadata type affected: CustomObject
Component name: VoiceCall
Explanation of the error
The cause of the error is this part of object's XML: <enableFeeds>false</enableFeeds>.
We've learned that when enableFeeds is set to false instead of true, it causes the validation to fail.
Resolution
Below we're explaining how to resolve the error depending on how you're making your deployment in Gearset.
Workaround for failed PR validation in Gearset Pipeline
To resolve the error when a pull request in your Gearset Pipelines fails the validation:
Navigate to the feature branch in your Version Control System (e.g. GitHub, Azure DevOps, Bitbucket etc)
Amend the
enableFeedsin object's XML.
Change it to:<enableFeeds>false</enableFeeds>as shown on the above screenshot.Re-validate the PR in your Gearset Pipeline. Changes made in the feature branch should be automatically pulled by Gearset into the feature branch from which we've originally created a PR, and this should help with your validation being successful.
Workaround for deployments made via Compare and deploy
Does the error happen when running a direct Compare and deploy (e.g. Git to org validation)?
If so, then follow one of these steps:
First, manually amend the object's XML in the Git branch that was selected as the source of your deployment.
You'd need to make that change directly in your Version Control System. Once the XML is amended, re-run the comparison in Gearset, and re-validate your deployment package.Alternatively, you can download the deployment package (.zip) created in Gearset, make the change locally in the object's XML, then use the amended deployment package (.zip) as the source of your deployment. And re-validate it against the target org.
By doing so, you'd need to run a new comparison in Gearset where the .zip file is selected as the source of your deployment.
Guidelines on how to download and amend the deployment package from Gearset: How can I change the deployment package before deploying?
Useful sources
More details on the issue can be found on Force 201 blog.
Note: The lack of this line of code <enableFeeds>true</enableFeeds> within the object's XML may also lead to the same validation error.
Resolution would be to add it the missing code in the source environment directly to that object's XML file.
Is the VoiceCall object failing during a Flow deployment?
Are you running into a similar error during a Flow deployment?
For example:
"field integrity exception: unknown (The object "VoiceCall" can't be updated through a flow.)"
Resolution
Check if Service Cloud Voice is enabled in the target org (or any other package/feature set that enables
VoiceCall).If Service Cloud Voice is enabled, it's possible that the deployment user in your Salesforce org is missing a "Contact Center Admin (Partner Telephony)" Permission Set.
Enabling above permission should resolve the issue.
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.