In March 2024, we released the first version of DAX Optimizer. Over the past few months, we have made minor improvements to existing features, which were included in the 1.1 release without a formal announcement. Our focus has been on developing new features and significant enhancements for the upcoming 1.2 release.
Here’s a preview of what’s to come. In the coming days, we will provide more detailed descriptions of the new features. Stay tuned!
CI/CD automation
We are introducing a command-line tool to execute DAX Optimizer in a batch service. This allows you to automate the extraction of the VPAX file using the VPAX command line, perform the analysis with the DAX Optimizer command line tool, and define subsequent actions based on the analysis results. For instance, you could halt the deployment of a model if it displays specific issues.
These command-line tools are compatible with Windows, macOS, and Linux, supporting a wide range of automation scenarios.
Detection of “unsafe” DAX expressions
We continually add new types of DAX code improvements to identify issues beyond just performance concerns. For example, we now detect expressions that could potentially yield incorrect results and suggest how to rewrite the code to ensure accuracy based on specific requirements.
New impact analysis for detected issues
Until version 1.1, DAX Optimizer assigned the same relevance to each issue as the corresponding measure. To better prioritize issues for resolution, version 1.2 introduces a new impact evaluation for each issue. This enhancement aims to improve and distinguish the Issues and Measures views. The upgraded visualization will apply to existing models without requiring a new analysis.