Guidelines for Creating and Editing Decision Matrices

Create a header for each column in a decision matrix and avoid spaces in header names.

Header names are used as input and output variables in expression set versions that call the matrix.

• Ensure that each row in a matrix is a unique combination of input values. If two rows have the same values in the input columns, only the first row is saved.
• Enter data in every cell of every decision matrix row. A decision matrix with empty data fields can't be saved. The exception is fields with the data type Boolean, which appear blank when set to false.
• For numeric data in matrix cells, ensure that every value in a column has the same number of decimal places. For example, 20 and 20.00 are considered as different values.

If a decision matrix version has more than 1,000 rows, you can see only the first 1,000 rows in the decision matrix builder.

UI-Based Editing: You can view and edit rows in the decision matrix builder if they have fewer than 1,000 rows.

• To modify a decision matrix version, ensure that the version isn’t active. If the version is active, deactivate the version.
• Avoid changing the data type of an existing column header. When you change the data type, the data in the column can be corrupted, requiring you to reenter all the data.

CSV-Based Editing:

You can edit rows in the decision matrix builder if they have more than 1,000 rows.

• If you use a CSV file to update the data in a decision matrix version, maintain consistency in the header names in the CSV file and the matrix.