function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
EmilyCobbEmilyCobb 

Issue deploy escalation rules with ant

I'm having problems deploying a new case escalation rule with ant. This is the first time we are using Case escalation rules in this org. Per all the documentation (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_escalationrules.htm) these should be deployable with ant / package.xml file. 
With my outbound change set, the Case escalation rule goes in an "escalationRules" folder and appears in the package.xml as: 
<types>
<members>Case.CaseEscalation</members>
<name>EscalationRule</name>
</types>
When I deploy this, I get the error message: 
All Component Failures: 
1.  package.xml -- Error: EscalationRule cannot be a component in a managed or unmanaged package. Remove EscalationRule from package.xml to deploy unpackaged components.

I've tried changing it to the plural to deploy the whole case object: 

<types>
<members>Case</members>
<name>EscalationRules</name>
</types>

And I get the error: 
All Component Failures:
1.  escalationRules/Case.escalationRules (Case.CaseEscalation) -- Error: Not in package.xml
 
Even though my folder structure and escalation rule matches that exactly. 
I've tried different combinations and can't seem to find any that deploy. Has anyone else run into this problem?

Thanks
Tarun J.Tarun J.
Can you check the version of your package?

EscalationRules components are available in API version 27.0 and later.

With API version 27.0 and later, it should work.
<types>
<members>Case.CaseEscalation</members>
<name>EscalationRule</name>
</types>

-Thanks,
TK

Did this answer your question? If not, let me know what didn't work, or if so, please mark it solved.
EmilyCobbEmilyCobb
API version is 38