Rule Load

With this load, business rules can be written into a Jedox In-Memory (OLAP) database.

Settings

Data source	The data source must contain the following 4 columns: Column 1: rule definition. If the Rule is inactive the definition is prefixed with “#”. Column 2: optional comment for the Rule Column 3: optional external ID Column 4: optional timestamp
Target connection	Connection to a Jedox In-Memory (OLAP) database
Target cube	Cube in the Jedox In-Memory (OLAP) database
Load mode	The following modes are available:
	update All existing rules are deleted in the target cube and all rules of source are written to it. See Note below. insert All rules of the source that don't exist in the target cube (based on the definition of the rule) are added to the cube. delete All rules of the source that exist in the target cube (based on the definition of the rule) are deleted in the cube.

This structure is analogous to the organization of the rule extract. Rules that are read with the help of extracts from a Jedox database or manually created can therefore be written directly by referencing the data source. It is also possible to build a data source that adheres to this structure for rules with the desired extracts and transforms. As rules are matched based on the definition of the rule, it is important for modes "insert" and "delete" to use exactly the same rule syntax as in the OLAP database.

Note: load mode "update" cannot be used when the source rule extract has been filtered for generated rule instances. This is because update mode deletes all existing rules in the target cube. Rule instances cannot run without rules or rule templates, and so the load cannot run and you will receive a warning message "Instance rule cannot be loaded in mode update". The same behavior is achieved with the load mode "delete" when the source rule extract has been filtered by generated rule instances. The load cannot run and you will receive a warning message “Instance rules can not be deleted.”

Updated February 7, 2024