Considerations for Migrating Calculation Matrices and Procedures
Before you migrate your calculation matrices and calculation procedures as decision
matrices and expression sets respectively, review these migration recommendations and the
post-migration behavior of these components.
Required Editions
Available in: Lightning Experience
Available in: Enterprise, Unlimited, and Developer
Editions for clouds that have Business Rules Engine enabled
Migration Recommendations
If a calculation matrix is used in a calculation procedure, avoid changing the matrix name
and the matrix column names. Modifying a matrix that’s referenced in a calculation procedure
results in a variable name mismatch between the matrix and the procedure.
Ensure that you don’t change the matrix column data types when the matrix is referenced in a
calculation procedure.
Ensure that the matrix’s column names don’t have spaces and special characters.
Ensure that the variable names in the calculation procedure don’t have spaces and special
characters.
Migrate calculation procedures and matrices as expression sets and decision matrices
respectively to a sandbox environment first. If everything works as expected, deploy the
expression sets and decision matrices from the sandbox environment to the production
environment.
If a calculation procedure references a calculation matrix, first migrate the calculation
matrix. For more information, see Migration
Scenarios and Workflow.
Post-Migration Behavior
The migrated expression set and decision matrix versions are inactive.
When a calculation procedure from a managed package is migrated as an expression set, the
expression set is an unmanaged component.
When a calculation matrix from a managed package is migrated as a decision matrix, the
decision matrix is an unmanaged component.
The calculation procedures and calculation matrices in the managed packages remain
unchanged.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.