MRM BI 22.09 is available as of November 1, 2022. This release includes new features, enhancements, and resolved issues. Reference the numbers in parentheses if you have questions for support.

General

🟪 Enhancement: The staging tables will now be automatically reseeded if AutoCleanupStaging is activated in Staging.BILoadingTaskWrapper with a default threshold of 75%. Alternatively, the BIStaging_CleanupLog stored procedure can be called separately, allowing for customization of the seed threshold. (628688)

🟪 Enhancement: The route key On-demand used as a substitute for the label of the route is mapped as the RouteTemplatKey in MRM BI. This field has been added to the BIRouteSummary view and RPS Data Source & Cache. In addition, the RouteName will automatically use this value if no label is specified, in line with the On-demand UI and reports. (700694)

🟩 Resolved Issue: When loading routes and jobs into the MRM BI database from the staging tables in specific datasets with measures, the loads took an unusually long time to be processed, affecting the following loading items (700696):

JobCoreAlert
RouteCoreAlert
Routes

🟩 Resolved Issue: The Route Planner datatype for projected violation has been changed to BigInt. This change resulted in an arithmetic overflow when extracting specific routes/stops, which has been solved. (621752)

🟩 Resolved Issue: When changing the datatype of a column in specific conditions, the entity view was not dropped before migrating the data. This issue led both the migration and rebuild processes to fail. (623222)

🟩 Resolved Issue: The Extract Stored procedures used an invalid number (messageid) when rethrowing an error, affecting the interpretation of the actual error cause. (623288)

🟩 Resolved Issue: When the On-demand driver key was not a numeric value, it could not generate a numeric driver ID, causing its insertion into the staging table to fail. (688977)