We are thrilled to share the news about the latest release of Tabular Editor 3, featuring two big new updates. The first was announced during the brilliant European FabCon in Stockholm, namely that our Enterprise Edition customers are eligible to free DAX Optimizer access, starting with this release. This also means that the DAX Optimizer Integration feature in Tabular Editor 3 is out of preview and generally available. The second big update is called Code Actions. It’s a productivity feature designed to take your DAX code editing experience to the next level, turning common code refactoring and improvements into a one-click maneuver.

Highlighted features and improvements in the October 2024 release of Tabular Editor 3:
1. DAX Optimizer Free Access
2. Code Actions
3. Value Filter Behavior — Highlighted features and improvements in the October 2024 release of Tabular Editor 3

Want to get your hands on the newest release? Head on over to our downloads page to get it!

New features

DAX Optimizer GA with Free Access

Our official launch of the DAX Optimizer integration into Tabular Editor 3 also means we now offer our Enterprise Edition Customers free access to DAX Optimizer through our partnership with Tabular Tools. So, if you are an Enterprise Edition license holder with a paid subscription, you can redeem 4 DAX Optimizer runs per day against a single model. All you must do is register an account with Tabular Tools, retrieve your redemption code from within Tabular Editor 3, and then you can start optimizing your model! You can read all about how to do this in our accompanying blog dedicated to how you can redeem your DAX Optimizer license.

Figure 1: DAX Optimizer integration allows you to understand your DAX issues, locate them, and fix them inside your development environment.

Having DAX Optimizer available is like having your own personal DAX expert (without the Italian accent) sit with you and go through your DAX line by line, suggesting improvements and ensuring optimal performance. And having DAX Optimizer inside Tabular Editor 3 allows you to understand your DAX issues, see where they occur, and fix them without leaving your development environment. We also ensured that using DAX Optimizer in Tabular Editor 3 is as secure as possible, which is why obfuscating your model when uploading it to the DAX Optimizer service is switched on by default!

The October 2024 release also ensures that all the newest features of DAX Optimizer are supported, such as the new evaluation metrics that were part of DAX Optimizer 1.2

Code Actions

Ever needed a hand to ensure your DAX is well-written? Well, now you don’t have to remember all the best practices and readability advice, as Tabular Editor 3’s Code Actions help you write better DAX faster.

Code Actions are part of all the DAX editors inside Tabular Editor 3 and discretely provide one-click suggestions on improving your DAX. The current release has 29 different code actions available, divided into three distinct categories: Improvements, Readability, and Rewrites – and we plan to add more in future releases iteratively.

Below are some examples of how Code Actions work:

Figure 1: Examples of Code Actions being used in Tabular Editor 3 — Figure 2: Examples of Code Actions being used in Tabular Editor 3

In the GIF, the available Code Actions are shown as a screwdriver or lightbulb with squiggles underlining the code. The Code Action menu is available throughout the UI and can be accessed using the shortcut ‘ctrl+.’ The DAX code is then adjusted so the variables are prefixed with _underscore and the first letter capitalized. Additionally, table names are added to columns, and finally, the aggregator SUM is used instead of the SUMX iterator.

To get a list of all the Code Actions that Tabular Editor 3 provides, please refer to our documentation.

Opening Model from DB: New Authentication option

The October release uses the latest Analysis Services client library (AMO/TOM) from Microsoft. A behavior change in this library causes users to be signed in automatically when choosing the Integrated authentication option, if a Microsoft Workplace or School Account is associated with their Windows account. However, often times when connecting to the Power BI XMLA endpoint, or Azure Analysis Services instances, you may want to choose a different account for signing in. In this case, choose the Microsoft Entra MFA authentication option, to ensure that you are prompted with the Microsoft Entra ID account selector.

Figure 3: **Microsoft Entra MFA** is a new authentication option useful when connecting to a Power BI/Fabric workspace or an Azure Analysis Services instance, as the **Integrated** option will default to the account associated with your Windows login.

Improvements

We’ve made several other improvements in the October 2024 release as well; here are our three highlights.

New Model Property: Value Filter Behavior

The latest Power BI/Fabric Semantic Model compatibility level includes a new property that controls the notorious Auto-exits behavior, impacting how the SUMMARIZECOLUMNS function deals with multiple filters applied to the same table. This property is available on Power BI / Fabric models at compatibility level 1606 or higher.

Figure 03: Setting the Value Filter Behavior property — Figure 4: Setting the Value Filter Behavior property

The ‘Value Filter Behaviour’ property has three different values that you can specify

1. Automatic: This is the default setting and it currently makes the Coalesced behavior kick in (in which multiple filters on a table are combined into a single filter based on actual values within the table, i.e. “auto-exists”).

2. Independent: This ensures that filters on the same table are kept separate.

3. Coalesced: This enforces the value filter behavior for the semantic model, combining the filters on the same table into one.

For more information on this property and its implications, please refer to Microsoft’s release blog post: Power BI October 2024 Feature Summary

Recent Items preferences

Thank you, Ed Hansberry, for your suggestion on our GitHub forum. We’ve listened and added a new setting in the preferences pane based on your feedback. Now, users can easily customize the number of recent items displayed in the file menu and the recent server menu. As an extra bonus, users can also clear those lists whenever they wish. We highly value all the input we get from our users, so please keep them coming!

Figure 4: New preference setting for recent items in files, models and servers — Figure 5: New preference setting for recent items in files, models and servers

Diagram performance on large models

We have updated our diagram component to make it considerably faster on very large models, so you can continue to build that galaxy star schema you have always wanted.

Bug Fixes

We have made multiple bug fixes in 3.18.0; please see our release notes for full details.

Better support for “FormatString” measures

We have fixed an issue where the semantic analyzer would show a warning due to the internal “FormatString” measures in DAX Expressions, which also blocked the ability to debug DAX queries where such a measure was present. However, note that debugging the “FormatString” measure itself is still not possible.

If you have any feedback or experience any bugs, please reach out to us in our community forum. We look forward to hearing from you

Tabular Editor 3: October 2024 Release