KB297779: When creating a security filter using Command Manager, if the attribute being used in the security filter has a data type Big Decimal, the expression for the security filter has an incorrect value in MicroStrategy Developer 9.4.x onwards.

SUMMARY:
This issue has been classified as a defect by Strategy.  The impact is for Strategy Command Manager 9.4.x onwards when trying to create a security filter using a Big Decimal Data type.  A solution/code fix for this issue is available in current releases and a workaround is provided in the following document.
 
SYMPTOM:
When trying to create a security filter based on a column that has an underlying Big Decimal data type in Command Manager, when editing the security filter back in Developer, it will be noticed that the security filter has a default value of -2147483648.

 
STEPS TO REPRODUCE:

1. Create a security filter in Command Manager using the following syntax:

CREATE SECURITY FILTER "Security FIlter CM" FOLDER "Project Objects\MD Security Filters" IN PROJECT "Case 825865" EXPRESSION "Id@ID=6123057956188547100";

 
In which ID has a data type of BigDecimal.

1. Open the security filter in Developer and notice the filter has been changed to Id (ID) Exactly =-2147483648.

 
CAUSE:
This is a known issue in Strategy Command Manager 9.4.1 - 10.x.
 
ACTION:
Strategy will continue to investigate and post updates as soon as they are available.
 
WORKAROUND:
As a workaround, put the entire expression in single quotes, and put the BigDecimal ID in double quotes as seen below:
 

CREATE SECURITY FILTER "Security FIlter CM" FOLDER "Project Objects\MD Security Filters" IN PROJECT "Case 825865" EXPRESSION ‘Id@ID=”6123057956188547100"’;