KB42660: Rows with metric value in the order of 0.00000000001 are eliminated by Analytical Engine in a report with view filter "metric different from 0" in MicroStrategy

SYMPTOM:
Rows with metric value in the order of 0.000000001 are eliminated by Analytical Engine in a report with view filter "metric different from 0" in Strategy.
The following steps demonstrate how to reproduce this issue in tutorial project:
Create Table Table1 (Column1 double);
Insert into Table1 Values (0.00000000001);
 

1. In tutorial warehouse, create an table and insert values with script below:
2. Import Table1 into project. Create a fact "Fact1" mapping to Column1. Create metric M1 with formula "Sum(Fact1)". Set the format of M1 as fixed decimal and "Decimal places" as "11".
   
3. Create and execute a report with M1 in columns as shown below:

• Add view filter "M1 Different from 0". The row with value "0.00000000001" will be eliminated by Analytical Engine and no data will display in the grid as shown below:

 
CAUSE:
The cause for this issue is that the precision for columns with double data type is lower than 0.00000000001 in Strategy Analytical Engine.
 
ACTION:
Use big decimal instead of double as the data type for Column1 with steps below:

1. Modify Fact1 and set a new column alias with big decimal data type. Set precision as 11 and scale as 2 as shown below:

• Update schema and use "#0#" instead of "0" in the view filter condition as shown below:

• Then, the row will not be eliminated as shown below:

 
NOTE:  Fore more details about big decimal data type, please refer to the following article:
 KB11195: Precision is lost when Analytical Engine calculations are performed on Big Decimal datatypes in MicroStrategy