TabularEditor/TabularEditor3 3.13.0

Tabular Editor 3.13.0

on GitHub

Tabular Editor 3.13.0 downloads:

• Download Tabular Editor 3.13.0 (64 bit) (recommended)
• Download Tabular Editor 3.13.0 (32 bit)
• Portable versions: x64, x86
• MSI version: x64, x86

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

Prerequisites

Tabular Editor 3.3.0 (and newer) uses .NET 6. You may have to install the .NET 6.0 Runtime for Desktop before you can launch Tabular Editor 3.3.0 (or newer). Starting from 3.3.1, the Tabular Editor 3 installer will download and install these prerequisites, if they are missing.

New in 3.13.0

Check out our release blog to get a brief overview of the most important updates in this release.

Improvements in 3.13.0

• Unused variable warnings are now only shown when the variable declaration block is complete, and only the variable name itself is highlighted. Moreover, there is a new option where you can toggle off these warnings under Tools > Preferences > DAX Editor > Code Assist.
• VertiPaq Analyzer in TE3 now uses the same default settings as in DAX Studio. You can also configure the "Read statistics from DirectQuery tables" option now, under Tools > Preferences > VertiPaq Analyzer.
• We've made a small change to how the Refresh Policy on a table appears in the Properties view, to better align with TOM. This change also lets you add annotations/extended properties to Refresh Policies, which previously wasn't possible. C# scripts can still use the Refresh Policy properties directly on the Table object, but we recommend updating scripts to access these properties through the Table.RefreshPolicy object instead.
• When selecting a table or column in the TOM Explorer, we now highlight (with bold font) any relationships the object is involved in, see #865. This feature can be disabled under Tools > Preferences > TOM Explorer.
• We now display the main storage mode (Import, DirectQuery, DirectLake, etc.) of the model, in the title bar.
• In addition to tables, it is now possible to view relationships starting from a specific column in the "Dependencies" view. Right-click on a column and choose "Show dependencies", then choose the "Show relationships starting from this column" option, see this comment.
• We now show a warning in the Messages view when objects are in an unprocessed state. This applies to both tables, columns and partitions. It also solves #1153.
• We now show a warning in the Messages view when a column uses a sort-by-column that has IsAvailableInMDX set to false (as this would otherwise produce an error when the model is saved/deployed). See #868.
• We've updated AMO/TOM to use the latest version 19.72.0. This library also includes an updated version of TMDL, which should fix a deserialization issue, when a table has incremental refresh policy applied.
• When serializing a model using TMDL, we now also output a database.tmdl file, which contains metadata at the database level (name, compatibility mode, compatibility level, etc.), which should improve the overall TMDL experience.

Bugfixes in 3.13.0

• Fixed an issue where undo'ing (Ctrl+Z) the removal of a Refresh Policy from a table, would not restore the configuration of that Refresh Policy.
• Fixed an issue where the DAX editor auto-complete would suggest incorrect items for window function parameters, when the window function was used as a filter argument for CALCULATE or CALCULATETABLE.
• Fixed a bug that prevented adding/removing levels to hierarchies, when connected to an instance of Power BI Desktop, even though this is a supported modeling operation.
• Fixed an issue where the "Calculate" refresh option did not appear for regular tables.
• Fixed an issue where evaluating only the current selection of a DAX Query would not work, if a line comment was directly above the first EVALUATE statement in the selection, see #912.
• Tabular Editor should now let you "Open from folder", when the folder contains ".tmdl" files (previous versions of TMDL used the ".tmd" extension). See #1175.
• The logic for determining if a table is a "Date Table" was a bit too restrictive, which could cause false circular dependency errors in some cases, or incorrect display of overridden filter contexts in the DAX debugger (due to the implicit filter removal associated with date tables).

Coming from Tabular Editor 2.x?

Watch this video to get an idea of the new 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

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