DW PH/Cloud Errors: Common Business Rule Errors – Solver Support

Summary

This article will provide guidelines on what to look for when troubleshooting a business rule that won't import into the Rules menu.

Article Sections

More Information
Best Practices When Correcting a Rule
Error Messages in Development Tools

More Information

Solver provides the ability for users to create their own business rules (SQL stored procedures) for data handling in Solver Cloud and Private Host. Directions on how to create a business rule can be found in this article. You may also subscribe to our Solver Academy for a more comprehensive step by step learning guide on how to create a business rule (click here).

This article assumes the user is familiar with all of the below prerequisites and/or can reference additional training material from resources such as w3 school or stack overflow for additional tutorials:

Familiarity with XML files
Familiarity with SQL
Familiarity with using the web browser Developer Tools (F12) to diagnose issues
Permissions to import business rules within the Solver application

Best Practice When Correcting a Rule

If a rule failed to import, likely there is at least one error in the rule syntax. This could be either an XML (rule headers / parameters) error, or a SQL (rule body) error. After you make the changes to correct the rule, it is recommended to first delete the existing rule before uploading the updated rule.

If the previous rule is not deleted prior to uploading an updated version of the same rule, you will need to refresh the page before importing the updated rule again. Otherwise, the rule will not import even if the syntax is correct.

Error Message in Dev Tools

Error Message	Cause	Solution
Error in publishing the rule	Typically it is referring to a SQL syntax error.	Troubleshoot the SQL syntax in the rule in SSMS. You can find the SQL body inside of the CDATA brackets. <![CDATA[ SQL body ]]>
Something went wrong: The rule name and stored procedure name should be the same. Please update the rule definition and re-import.	The rule name in the XML syntax is not the same as the rule names in the SQL syntax. All labels must match for the rule to import.	Right click and select "Open image in new tab" for locations of the rule names.
Error in geting Content of XML Tag	Missing the <![CDATA[ ]]> tag in the rule.	Add <![CDATA[ ]]> in the rule.
Value cannot be null. Parameter name: source	Either: Not having a parameter value selected in the business rule step in the job, or The business rule has been modified/deleted in the Rules tab, but not updated in the job	1. Select the appropriate parameter value for said rule in the job. If the rule does not have a parameter, add a dummy parameter to the rule. Reach out to Solver Support if you need assistance with this, as the rule syntax is slightly different in each rule. 2. If a rule is in a job and it has been modified/deleted in the Rules tab, you will need to delete the said rule from the job that is failing and re-add the updated rule back into the job.
Operand type clash: uniqueidentifer is incompatible with int	The columns CreatedBy and UpdatedBy have type int and need type UNIQUEIDENTIFIER.	Attached is a rule to run to address this error. FixBusinessRules.xml
Arithmetic Overflow converting numeric to data type numeric	This occurs when a value is too large to fit into a datatype numeric(28,16).	Contact Solver support. This is either SQL formatting the value into Scientific notation or we need to consider how to convert your tenant to use numeric(30,15) such as working with the Indian Rupee.