Tabular Editor 3.19.0

Tabular Editor 3.19.0 .NET 8 downloads:

Tabular Editor 3.19.0 .NET 6 downloads:

If you haven't used Tabular Editor 3 before, you are eligible to a 30 day trial, which can be activated after installation. You can also purchase a license.

Important

.NET 6 is out-of-support as of November 2024. If you are not able to install the .NET 8 Desktop runtime now, please contact your IT organization to plan ahead, as we will no longer be providing .NET 6 builds of Tabular Editor 3 after December 2024. Alternatively, use our portable builds, which include the required .NET runtime.

New in 3.19.0

This release is all about quality-of-life improvements and bugfixes.

Check out our release blog for a brief overview and a video showing the most important updates in this release.

  • Our DAX code editors now support the Expand selection shortcut (Ctrl+Shift+E), which expands the selection to the next logical code block. This is useful, for example, when the cursor is inside a DAX function call, and you want to select the entire function call. Repeatedly pressing Ctrl+Shift+E will expand the selection to the next logical code block, eventually selecting the entire DAX expression.
  • We've modified how execution of DAX queries work, due to popular demand:
    • The Execute action (F5) will now execute only the selected portion of the query when text is selected. If no text is selected, the entire query will be executed.
    • Execute Selection (Shift+F5) will also execute the selected portion similar to the Execute action above, but when nothing is selected this action only executes the EVALUATE statement under the cursor.
    • We've introduced an Execute full query action (no default keybinding), in case you need a way to execute the full query without changing your current selection.
    • Last, but certainly not least, you can now execute partial code. To do this, simply select a portion of code, such as a table or scalar expression anywhere inside your query (even in comments) and hit F5. Tabular Editor will take care of wrapping scalar expressions in curly braces, wrapping column references in a call to DISTINCT, and adding the EVALUATE statement, such that a valid DAX query will be sent to the server.
  • Across all of our DAX editors, the vertical scrollbar will now indicate the location of any warnings/errors, as well as applicable Code Actions in the Improvements and Readability categories. Mouse over the scrollbar indicator to see a tooltip with a description of the issue, and click to navigate directly to it. This is especially useful when working with large DAX expressions, queries or scripts. If you find this feature distracting, it can be toggled off under Tools > Preferences > Text Editors > Show indicators on scrollbar.
  • Pin, Unpin, and Delete functionality for the Recent Files and Recent Models menus: Added the ability to pin items to the top of the "Recent Files" and "Recent Models" menus, unpin them, or delete them entirely using a new right-click pop-up menu. Pinned items are visually marked with an icon and prioritized at the top of the menus.
Note

As a reminder, all shortcuts can be customized under Tools > Preferences > Keyboard. The shortcut keys mentioned in this document are the default settings.

Improvements in 3.19.0

  • We have improved the Data Refresh view so progress events that relate to the same table, are now being grouped together. This makes it easier to understand the progress of the refresh operation, especially when refreshing large models with many tables.
  • When jumping to a specific line of code outside the range of code currently visible in the editor, we now scroll the editor such that the destination line is vertically placed at the center of the editor, rather than near the top/bottom.
  • A new right-click menu action has been added to the DAX query results grid, which will let you show the actual query that was executed (as Tabular Editor may modify the query to add a row limit, or to turn a partial selection into a valid query as mentioned above).
  • The "Load Semantic Model from Database" dialog now restores preferences for recently connected servers, including Authentication mode, username (excluding passwords), connection mode, and status bar color.
  • Updated AMO/TOM to 19.87.2.
  • Our offline schema detection (based on our M query parser) now fully supports the use of PowerPlatform.Dataflows, see #970.
  • When copying/duplicating tables in the model, the inserted table is typically renamed (to ensure uniqueness of table names in the model). When this happens, we now automatically fix-up DAX expressions of objects within that table. For example, calculated columns or Row-Level Security filter expressions on the table, are now updated to use the name of the inserted table. You can toggle off this behavior under Tools > Preferences > Modeling operations > Clipboard operations.
  • The summary page of the Deployment Wizard has been slightly improved, so that it now shows the source and destination Compatibility Levels in case they differ. It also shows a warning icon and a tooltip if the source Compatibility Level is lower than the destination.

Bugfixes in 3.19.0

  • The Data Refresh view will no longer scroll to the top when new progress events are added to the list.
  • Data Refresh operations are disabled when connected to a model in Power BI Desktop, as Desktop does not support refresh operations initiated from external tools.
  • Fixed an issue with the Rewrite table filter as scalar predicate code action not properly qualifying columns with the table name after the rewrite, potentially causing the resulting DAX to be invalid.
  • Fixed an issue with the Split multi-column filter into multiple filters action, where filters would be deleted, when the original filter contained more than 2 operands.
  • When hitting F12 (Go to definition) on an object reference inside a DAX Script, the editor will now correctly jump to the object definition inside the script (if it is present), rather than switch to the Expression Editor.
  • When connected to the Power BI XMLA endpoint or an instance of Azure Analysis Services, attempting to impersonate multiple roles in a Pivot Grid, a Data Preview, or a DAX Query, should now work correctly (instead of only the first role in the list being applied).
  • Various bugfixes in the M analyzer, to support more complex M queries for purposes of offline schema detection. For example, we are now able to correctly infer the table schema resulting from an M query that uses a custom function, such as the one in this discussion.
  • Fixed a bug which would cause a crash when selecting both a table and a column (in another table) in the TOM Explorer, and then invoking the right-click menu.
  • Fixed an issue where clicking the "Back" button in the deployment wizard after selecting the Microsoft Entra MFA authentication option incorrectly triggered a login pop-up. The "Back" button now properly navigates to the previous step without attempting to authenticate.
  • Fixed "Object reference not set to an instance of an object" bug when clicking on the "Export build..." button in the Deployment Wizard (regression in 3.17.0).
  • Fixed the JSON DDL request failed: Unrecognised JSON Property: expressions-error upon deploying a model against Analysis Services on SQL Server 2016 or 2017, while the "Deploy shared expressions" option was unchecked.
  • Fixed the Value cannot be null. (Parameter 'source') when attempting to import or update the table schema from a Dataflows entity that does not define any columns.

Coming from Tabular Editor 2.x?

Watch this video to get a quick tour of the main features in Tabular Editor 3. Also, make sure to check our onboarding guide.

Tabular Editor 3 major features overview:

  • Fully customizable IDE, with multi-monitor, Hi-DPI support and themes
  • New powerful DAX code editor with auto-complete, syntax checking, code folding and much, much more
  • *Workspace mode, allowing you to save your changes to disk and synchronise model metadata to Analysis Services simultaneously
  • *Preview table data with infinite scrolling, create PivotGrids or write DAX queries to browse the model or test calculation logic
  • *Schedule data refreshes
  • Update Table Schemas on both Provider and Structured Data Sources (yes, even for M queries!)
  • Create data model diagrams
  • Create DAX scripts that allow you to edit multiple measures or other calculated objects in a single document
  • Record C# scripts and save as macros (formerly known as "Custom Actions")
  • VertiPaq Analyzer integration
  • DAX debugger
  • DAX Optimizer integration
  • Code Actions to easily refactor you DAX.

*=Only while connected to an instance of Analysis Services or Power BI