Starting with the release of MicroStrategy ONE (March 2024), dossiers are also known as dashboards.
The following is a full list of MicroStrategy Data Engine changes that may be seen when upgrading to MicroStrategy 2019 which improves
intuitiveness & consistency in various workflows. These changes are to both defect fixes and enhancements for a more stable and robust reporting platform. To find out if you are hitting any of the scenarios listed below, take advantage of MicroStrategy Integrity Manager and the Upgrade Analysis Dossier. In leveraging these you can review how these changes are impacting your environment during an upgrade to the latest release of MicroStrategy. Please also see this article for more details:
Data Engine changes impacting the upgrade to MicroStrategy 2019 releaseInternal ID | Impact | Community Article Name | Motivation For Change | Data Engine Version | MicroStrategy Version |
US86780 US128114 | Data | KB40049: Individual metric columns hidden with all zero or null values in MicroStrategy 10.9 through 10.11, reverted in 11.0 | Intuitiveness | 2019 | 2019 |
DE55671 | SQL, Data | KB439678: Incorrect join columns are used with level metrics using outer joins | Intuitiveness | 2019 | 2019 |
DE67219 | Data | KB440051: Count Metric displays double dashes (--) for calculated group instead of expected data in MicroStrategy 10.9 | Intuitiveness | 2019 | 2019 |
DE75537 | CSI, Data | KB442186: User encounters unspecified error in a visualization after manipulating dossier, save-as, and running the newly saved dossier | Consistency | 2019 | 2019 |
F9810 | SQL, Data | KB44184: Dossier shows different data when In-Memory Intelligent Cube dataset is changed to Live mode. | Consistency | 2019 | 2019 |
DE76765 | SQL, Data | KB441510: In a dossier, a smart metric defined on another metric that is missing from dataset goes from NULL to 0 when Live Intelligent Cube is switched to I-Memory mode. | Consistency | 2019 | 2019 |
DE93995 | Data | KB442258: The metric can be calculated in the field group even if it is deleted from the dataset while its components still exist with remove missing unit setting enabled | Intuitiveness | 2019 | 2019 |
DE74150 | Data | KB442259: The metric can be calculated in the grid even if it is deleted from the dataset while its components still exist with remove missing unit setting enabled after | Intuitiveness | 2019 | 2019 |
DE114739 | CSI, Data | KB442260: For a data import intelligent cube which contains attribute with derived geo role, delete table operation may hit error, if Data Engine Version set to 11 | Intuitiveness | 2019 | 2019 |
DE46107 | CSI | KB440734: Error "cannot be found.Item" is encountered in Dashboard when visualization refers to a metric which is deleted from the dataset | Intuitiveness | N/A | 2019 |
DE39290 | Data | KB440659: Sort order in report services document fails to take effect in MicroStrategy 10.4 and earlier | Intuitiveness | N/A | 2019 |
DE52300 | Data | KB439632: Derived element calculations cause metrics based on day data to display as null in MicroStrategy 10.7 and up. | Intuitiveness | N/A | 2019 |
F6760 | SQL | Multi-Source Report Pre and Post Statements (In-Memory) | Consistency | N/A | 2019 |
F8433 | SQL | Multi-Source Report Pre and Post Statements (Live Connect) | Consistency | N/A | 2019 |
DE84254 | SQL | KB442295 : New SQL Generation Wildcard (!i) for Job Priority | Intuitiveness | N/A | 2019 |
US88224 | SQL | KB442289: New SQL pattern for Impala and Hive sources for "insert into values()" | Intuitiveness | N/A | 2019 |
DE76773 | CSI, Data | KB441477: Filtering on warehouse null values in Dossier shows different behavior between Live connect and In-Memory cube. | Consistency | N/A | 2019 |
DE94796 | SQL | KB442276: SQL execution fails with error "Too many key parts specified; max 16 parts allowed." against MySQL database when 17+ attributes on the report and an index for intermediate SQL pass is being built for 17+ attributes | Intuitiveness | N/A | 2019 |
DE95629 | Data | KB442282- Default format of attribute form is formatted as scientific when the form type is Big Decimal and value is greater than 99999999999 | Intuitiveness | N/A | 2019 |
DE63693 | CSI, Data | KB440559: Incorrect metric value displayed when dependent metric isn't placed in the same grid in MicroStrategy 10.x | Intuitiveness | N/A | 2019 |
US49823 | Data | KB440052: Subtotals for calculated group element display double dashes (--) in VI Dashboard in MicroStrategy 10.7 and below | Intuitiveness | N/A | 2019 |
DE69807 | Data | KB442277-The received cardinality from the server is not correct for the external dataset | Intuitiveness | N/A | 2019 |
DE120325 | Data | KB442372: In MicroStrategy 11.1 and higher, the nullcheck setting will convert date/timestamp null to 12/31/1899 | Intuitiveness | 2019 | 2019 |
DE94307 | SQL | KB442143: SQL mismatch is reported for intermediate table column data type after running an Integrity Manager comparison test between two MicroStrategy releases | Intuitiveness | N/A | 2019 |
DE88346 | CSI | KB483219: Three Attributes in a template do not join on the common table as expected. | Consistency | 2019 | 2019 |
DE114779 | Data, CSI, SQL | KB483237: Unspecified error when loading a Visualization | Consistency | 2019 | 2019 |
DE104792 | Data | KB482990: CurrentDate function returns no data | Intuitiveness | N/A | 2019 |
DE84933 | CSI | KB440874: "Object used in this report was not selected during prompting" error message is displayed when running a subset report which has a filter on attribute that is deleted from the Intelligent Cube | Intuitiveness | N/A | 2019 |
DE93738 | SQL | KB44152: Analytical Engine SQL displays 'ascending' value as 'false' instead of 'true' for a metric using NTile function | Consistency | 2019 | 2019 |
DE99286 | SQL | KB441377: Full Outer Join Optimization implemented in MicroStrategy 11.0 for databases that do not support Full Outer Joins | Consistency | 2019 | 2019 |
DE75549 | Data | KB483350: Conditional metric shows nothing when aggregated | Intuitiveness | 2019 | 2019 |
KB442652
