Skip to main content

Resolving Vlocity deployment error - "INVALID_INPUT, An enabled decision matrix version cannot be updated/deleted.: [IsEnabled] (System Code)"

This document explains why you hit this Vlocity error when deploying a decision matrix and how to resolve it.

Richard Terry avatar
Written by Richard Terry
Updated this week

Explanation of the error

When deploying DecisionMatrixVersion data in Salesforce, the Decision Matrix Version needs to be an in-active state.

If the Decision Matrix Version is set to active you are still able to deploy metadata changes but all data related changes will trigger this error.

This also affects deployments of "new" Decision Matrix due to the order of the deployment. In this case if you deploy an active DecisionMatrixVersion, the metadata is deployed first and set in an active state. The data portion is now deployed and fails to deploy due to decision matrix version already being active.

How to resolve this error

In order to resolve this error we need to make sure that the Decision Matrix Version is in an inactive state when the data portion is deployed.

  1. When deploying a Decision Matrix Version, make sure that in the source environment it is in an in-active state.

  2. Make sure you deploy both the Decision Matrix Version metadata (Decision matrix definition version) and data (Vlocity - DecisionMatrixVersion) at the same time.
    This will make sure the the target is disabled before the data portion is deployed in case it's already present in the target.

  3. Make sure there is another Decision Matrix Version in the target that is active.

    If you have other comments in your org that use this decision matrix then Salesforce will not let you de-activate the only active version.

Assuming all of the above are true this should resolve your error.

Disclaimer: This error is returned by Salesforce directly, rather than Gearset. Even so, we offer guidance based on our combined experience with the 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?