Upgrade Impact | MSTR Version / Data Engine Version | Upgrade Engine Tag(s) | Choice available to Customers |
SQL changes for LIVE Dossiers and Documents if text input is used in filtering/search condition | 2021 / NA | Not tagged F16877 F22679 | - Accept this security enhancement. Customer should only see integrity manager SQL differences for LIVE dossiers and documents if there's any string conditions in 2020GA. Report/Cubes do not show differences under integrity manager. |
0 or null metric columns are visible now. Related to Show/Hide NULL. | 2019 / 2019 | DE117141 | - Change the Hidden project level VLDB setting by modifying the VLDB.xml for 10.9-10.11 behavior if customer is on Data Engine Version 2019 or above. |
Different data or slower performance may be observed. UseLookUpForAttributes flag is correctly passed into inner non-aggregation function. | 2019 / 2019 | DE86726 | - Accept the new correct data which is accurate OR |
Metric-only pass will return null when all the data is filtered out. | 2019 / 2019 | DE75549 / DE101467 | - Accept the new correct data OR |
Different data or default selector elements may change. Related to Trim string setting | 10.11 / 2019 | US95205 | - Customer needs to clean data using ETL in the source OR |
Different data may be observed for metric values. Related to Relative tolerance for calculating equality between double-type data | 2019 / 2019 | DE118648 | - Accept new correct data OR |
Small metric data change. Related to data precision for double value in parallel or sequential aggregation | 10.5 / NA | DE121578 | - Accept the new metric data which has only very small difference |
Different metric data may be observed. Agg From base Derived metric is wrongly calculated at grand total level | 2020 / 2020 | DE150215 | - Accept the new correct data which is accurate OR |
Min, Max Relation VLDB is retired now defaulting to Min Relation. Performance is the primary factor and data can be changed when MIN relation is used vs MAX. | 2019 / 2019 | DE111564 / US111329 | - Accept new data OR |
Dossier shows incorrect data because filter is not applied when running dossier the first time. Then, remove the metric from grid and add same metric back, the grid shows correct data because filter is applied. Engine logic is wrong when the attribute group Patterns is used in filter. | 2020 / 2020 | DE139263 | - Accept new data OR |
No data to right data. | 2019 / NA | DE119354 | Customers would not argue why we go from No data to Right data. |
Wrong metric data to correct metric data. Derived Attribute based on 2+ attribute is now joint child as opposed to each child as 1:M with Derived Attribute. | 2019 / 2019 | DE93077 | - Accept new correct data OR |
Wrong metric data to correct metric data when derived metric is based on attribute + fact and we ignored the fact leading to wrong data. | 2020 / 2020 | DE145994 | - Accept new correct data OR |
SQL change for performance only. The fix is to improve the performance by applying the filter directly to the dataset. | 2020 / 2020 | DE133951 | - Customers should not see data change due to this. |
SQL change for security. Secure Freeform SQL report’s text prompt answer(s) using prepared statements | 10.5 / NA | F5749 | - Customers should not see data change due to this. |
SQL change for unified Quoting Behavior for Warehouse Identifiers | 2020 / 2020 | F11007 | - Customers should not see data change due to this. |
SQL change for performance when extra SQL passes are generated when the metric join type is set to be an Outer Join and SQL Global Optimization is set to Level 4 | 2020 / 2020 | DE129926 | - Customers should not see data change due to this. |
SQL change for performance for filter expression containing 'IS NULL' or 'IS NOT NULL' clause. | 2019 / 2019 | DE72287 | - Customers should not see data change due to this. |
