Tabular Editor 3.24.0

Tabular Editor 3.24.0 downloads:

• Download Tabular Editor 3.24.0 (x64) (recommended)
• Download Tabular Editor 3.24.0 (ARM64)
• Portable versions: x64, ARM64
• MSI version: x64, ARM64

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.

---

Note

We are now providing native ARM64 builds in addition to regular 64-bit (x64) builds. 32-bit (x86) builds have been discontinued.

New in 3.24.0

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

DAX Package Manager

Find and install DAX packages for Power BI with a single click! This new feature integrates with https://daxlib.org, which serves as an open gallery of community-authored reusable packages of DAX code (in the form of DAX User-Defined Functions). Dozens of packages and hundreds of UDFs are already available, with more coming every day. Learn more.

Organize UDFs by namespaces

The concept of "namespace" doesn't exist in DAX, yet the recommendation is to name UDFs in such a way that ambiguities are avoided and that the origin of the UDF is clear. For example DaxLib.Convert.CelsiusToFahrenheit (using '.' as namespace separators). In this update, we show UDFs hierarchically by their namespace in the TOM Explorer, making it easier to manage and navigate multiple such UDFs. There's a toggle button just above the TOM Explorer, if you prefer to see a flat list of UDFs instead.

This feature also adds a "Namespace" property to UDFs, allowing you to customize the namespace of each UDF individually, without changing the name. Think of it as Display Folders for UDFs. This is useful, for example if you want to batch rename (F2) multiple UDFs to get rid of the namespaces in their names, but you still want to keep them nicely organized in the TOM Explorer. Learn more.

Note

This organizational feature in Tabular Editor doesn't affect DAX code - function calls remain the same regardless of namespace organization.

Improvements in 3.24.0

• Updated the Microsoft.AnalysisServices client library to v. 19.106.1, which includes fixes to TMDL serialization issues, among other improvements.
• Updated the Dax.Vpax library to v. 1.11.0, which adds support for calendars and UDFs, among other improvements.
• UDFs now have the Batch Rename option (F2) in the context menu. This is useful if you want to rename multiple UDFs at once, e.g. to add or remove a common prefix or suffix, or to change the "namespace" of multiple UDFs at once.
• UDFs and Calendar objects can now be dragged in to C# scripts and DAX code editors just like other objects (measures, columns, etc.).
• Substantial improvements have been made to our DAX editors support for Visual Calculations. This is relevant when editing UDFs or DAX Queries. For example, we no longer show false error messages when using a Visual Calculation function in a UDF, as long as no model objects are referenced in that UDF or any UDF it calls. The auto-complete will now also suggest Visual Calculation functions and visual column references when appropriate. Axis keywords (ROWS, COLUMNS) are now also properly supported in Visual Calculations.
• We added a Show/hide calendars toggle button next to the Show/hide partitions button above the TOM Explorer. The button is only shown when working on a model at Compatibility Level 1701 or higher.
• We now show a warning in the tooltip of any week-based DAX time intelligence functions, if the current model does not contain a calendar with weekly granularity (without which these functions will not work).
• The Pivot Grid Field List can now be toggled on or off using the dedicated button in the Pivot Grid toolbar.
• Saved Pivot Grids now retain the settings for Show empty values on columns and Show empty values on rows.
• Our C# editor now has auto-complete support for UDFs and Calendars on the Selected object. For example, you can now type Selected.Calendars to get a list of the currently selected calendars in the TOM Explorer.
• You can now export TMDL scripts for multiple objects at once, by multi-selecting objects in the TOM Explorer, right-click and choosing and choosing Export script > TMDL > To clipboard / To file from the context menu.
• Tabular Editor now lets you open .pbism files, which are commonly found in Power BI Project folders.
• Added a Fix Expression Editor to the BPA Rules Editor, which allows you to write BPA fix rules directly inside the Editor.

Bugfixes in 3.24.0

• Fixed bugs related to dragging/dropping objects in the TOM Explorer, and also show a warning message when a drag/drop operation fails.
• When connecting to models in PBI Desktop (September 2025 or newer), you should now (again) be able to perform refresh operations from within TE3.
• Fixed a bug where Calendars would appear next to measures/columns of a table, instead of inside the "Calendars" collection in the TOM Explorer.
• Our Semantic Analyzer will no longer show a false error when using certain UDF parameter type hints in combinations that are valid, for example: (a: TABLE EXPR) => .... For more details, see #1492.
• UDFs no longer show false error messages when column references cannot be immediately resolved. For example, an UDF defined as (t) => SUMX(t, [SomeColumn]) will no longer show an error on [SomeColumn], as the expression may be valid when the UDF is called with a table that contains a column named SomeColumn.
• Using UDF expression parameters in calls to LOOKUPVALUE or GROUPBY no longer results in false errors from the Semantic Analyzer.
• The Semantic Analyzer now correctly deals with DAX variables that shadow outer variables (or UDF parameters) with identical names (e.g. (a) => VAR a = <expression> ...)
• When creating a Calendar Column Association, we no longer show the "Unknown" time unit in the dropdown, as this is not a valid option anyway.
• Fixed a bug where processing-related buttons ("Clear completed", "Clear All", "Cancel", "Pause") remained active when switching between models, instead of being properly disabled for the new model.
• Fixed an issue that could cause the application to freeze when modifying a PivotGrid during its refresh process. To prevent this, context menu actions have been removed and some PivotGrid toolbar items are now disabled while the PivotGrid is refreshing.
• Fixed a bug where we showed false warnings about constant expressions when using CALCULATE in conjunction with parameterless functions such as SELECTEDMEASURE., see #1495.
• Fixed a regression from 3.23.0 where users would see an "Unhandled exception" when opening a DAX Optimizer analysis report for a specific object.
• UDFs will now be properly formatted when calling the FormatDax method through a C# script. See #1500.
• Allow x64 version to be installed on ARM machines again.
• Don't suggest adding the table name in front of visual columns (code action DI004), as only simple column references are supported in Visual Calculations.
• Search results are now properly cleared when the document in which the hit was found, is closed. This would previously cause an unhandled exception when double-clicking on a search result from a closed document.
• Keywords consisting of multiple words (for example ASC BLANKS FIRST in the ORDERBY function), and axis keywords for visual calculations (ROWS, COLUMNS) are now formatted correctly.

---

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 P...

Tabular Editor 3.23.0

Tabular Editor 3.23.0 downloads:

• Download Tabular Editor 3.23.0 (x64) (recommended)
• Download Tabular Editor 3.23.0 (ARM64)
• Portable versions: x64, ARM64
• MSI version: x64, ARM64

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.

---

Note

We are now providing native ARM64 builds in addition to regular 64-bit (x64) builds. 32-bit (x86) builds have been discontinued.

New in 3.23.0

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

• The Table Import Wizard now supports Fabric SQL Databases and Fabric Mirrored Databases as data sources, both for Import and Direct Lake mode models, in line with the announcement in the Power BI Desktop July 2025 update.
• Native ARM64 support.
• Preparations for upcoming Power BI features (which we can't disclose just yet).

Improvements in 3.23.0

• Main window now remembers its position & size. Can be disabled in Preferences > Tabular Editor > User Interface > Layout.
• Messages view now copies the selected cell rather than the whole row by default, Ctrl+Shift+C can be used to copy the whole row as before. There is a new right click context menu with these (Copy Cell, Copy Row) options as well.
• Updated 3rd party dependencies including AMO/TOM to v. 19.103.2.
• A new word wrap option is now exposed in toolbar, menu (Edit > Word Wrap) and preferences window (Text Editors > General). Line wrap indicators can also be enabled in the preferences.
• The C# script editor's auto complete now provides more flexible search (i.e. search for partial matches and search by capital letters).
• You can now use the "Apply" or "Apply selection" action on DAX queries containing DEFINE COLUMN or DEFINE TABLE statements, in addition to DEFINE MEASURE statements. This will create the corresponding calculated columns or calculated tables in the model, or update their DAX expressions if they already exist.
• Peek definition window now lets user scroll the main DAX editor instead of swallowing mouse scroll inputs while the mouse is on it.
• Peek definition window height is now adjusted more tightly.
• Semantic Analyzer no longer shows "Multiple column cannot be converted to a scalar value" errors, when there are other, more indicative error messages.

Bugfixes in 3.23.0

• Fixed a bug where you would have to enable Allow unsupported modelling operations in order to make any changes to a model in Power BI Desktop, even though modelling operations were supported.
• Fixed a bug where main window exceeds screen dimensions depending on resolution and DPI scaling.
• Fixed toolbar customization settings such as "Large icons", "Show ScreenTips on toolbars" etc. not persisting after restarting TE3.
• Fixed a visual glitch where TOM Explorer's Perspective and Language drop-down controls have duplicate buttons.
• Fixed a bunch of issues with "Peek definiton" feature:
  • Peek definition is closed on undo/redo operations
  • Peek definition is invisible when used on the last line of DAX editor
  • Peek definition turns invisible when the line ending of the peeked reference is deleted
  • Peek definition is also closed when trying to instead close auto-complete popup with ESC
  • Peek definition is also closed when trying to instead clear rectangular-selection with ESC
  • When a new line is added to the left of peeked reference, peek definition turns invisible and empty padding space incorrectly appears above the peeked reference
  • Fix empty padding space appearing under the wrong line if the caret is on a different line than the peeked reference when the peek definition is triggered
• Calltips in the C# code editor are now sized correctly, ensuring that all of the calltip text is visible.
• Fixed a bug where Fabric Warehouses were not correctly listed in the Fabric connection dialog (instead they were shown as type "Unknown").
• DAX autocomplete should no longer suggest DAY for the <Interval> parameter of the PARALLELPERIOD function, as this is not a valid value for that parameter.
• Calltips will now update correctly when swapping between different syntax alternatives using the up/down arrows.
• Fixed a bug where code actions did not update correctly when switching between objects.
• Fix line numbers in code editors getting cut off when zoomed in.

---

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

---

Tabular Editor 3.22.1

Tabular Editor 3.22.1 downloads:

• Download Tabular Editor 3.22.1 (64 bit) (recommended)
• Download Tabular Editor 3.22.1 (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 activated after installation. You can also purchase a license.

Important

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

Bugfixes in 3.22.1

• Fixed a bug where the Data Refresh view would turn blank and not show additional refresh operations until the app was restarted. See #1461.

New in 3.22.0

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

(Enterprise Edition only) Tabular Editor 3 now fully supports Direct Lake over OneLake and Direct Lake over SQL. This means:

• The Table Import Wizard has new import options for Fabric Warehouses and Lakehouses. You no longer need to know the SQL analytics endpoint of the Warehouse/Lakehouse you wish to connect to. Instead, we show you a list of all the Warehouses/Lakehouses in your workspace, allowing you to choose the one you wish to use.
• On the last page of the Table Import Wizard, you can choose whether to use Direct Lake in OneLake or SQL mode, or whether to configure the table for plain old "import" mode.
• When the model contains tables in Direct Lake over OneLake mode, you can now also add tables in Import mode, in order to create mixed mode/hybrid models.
• When previewing data in Direct Lake tables, we no longer restrict the number of rows returned (so you can freely scroll through all the data in the table, just like in Import mode). Be aware that all columns are swapped into the Semantic Model in the Fabric capacity when you perform a data preview. Consider using a DAX Query if you are concerned about memory consumption on your Fabric capacity.

Note

We no longer configure Direct Lake models to use a case sensitive collation. If you plan to use Direct Lake over SQL with a Fabric Warehouse that uses a case sensitive collation, you must manually fill out the Collation property of your semantic model before adding any tables or other objects.

Improvements in 3.22.0

• When saving a model as a single file, the Save file dialog now suggests "model.bim" as the default file name.
• Updated various dependencies to their latest versions, including AMO/TOM to 19.98.0.3. This update fixes longstanding authentication issues with Work or School accounts and repeated sign in promts.
• DAX query editor support for the MPARAMETER keyword, see #1467.
• Our DAX editors now support word based auto complete search terms. In other words, if you type sales ytd in the editor, the auto complete will now suggest measures such as [Sales Margin YTD], [Sales Revenue YTD], etc.
• With the June 2025 update of Power BI Desktop, external tools can now perform any write operation on the semantic model. As such, we no longer restrict the modeling operations available in Tabular Editor, when connecting to a model in this or newer versions of Power BI Desktop.

Bugfixes in 3.22.0

• Added exception handling when encountering IOException's during save-to-folder operations (where we sometimes need to delete folders in the folder structure, which can be blocked by file system locks placed by version control systems).
• Fixed a bug where certain keyboard shortcuts (both default and customized) didn't work when the "What's new" page was focused.
• When assigning a custom keyboard shortcut that is already assigned to another command, we now show a warning message and remove the shortcut from the other command, to avoid ambiguity.
• Fixed a bug where the Semantic Analyzer showed a false error message when using unqualified column references in a DAX window function. See #1460.
• Fixed a bug that could sometimes cause the Data Refresh view to freeze, requiring an app restart to resolve. See #1461.
• Fixed several smaller DAX editor issues related to auto complete, auto formatting, and syntax highlighting of keywords.
• Query Group names (i.e. "display folders" for Shared M expressions and M partitions) can now be modified. Also, if pasting an object with a query group into a model that doesn't contain said query group, it will be created automatically, so as to avoid the error message on subsequent Save / Deployment of the model.
• Fixed a bug where it was sometimes not possible to Undo previous changes, after saving the model metadata back to the server.

---

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

---

Tabular Editor 3.21.0

Tabular Editor 3.21.0 .NET 8 downloads:

• Download Tabular Editor 3.21.0 (64 bit) (recommended)
• Download Tabular Editor 3.21.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 activated after installation. You can also purchase a license.

---

Important

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

New in 3.21.0

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

Improvements in 3.21.0

• We've made even more visual tweaks and improvements to our Diagram view in this release:
  • Icons visually indicate column data types.
  • Double-arrows when a relationship uses bi-directional cross filtering
  • A chevron button in the top-right corner of the table allows you to quickly toggle between various ways of displaying the columns in the table: All columns, key columns only, or no columns at all.
  • Various font size adjustments and other minor tweaks
• Updated AMO/TOM to the latest version 19.94.1.1.
• We have added a new property on the Model object, MetadataSource, which includes information about where the model metadata was loaded from. This is useful for C# scripts, for example if a script needs to iterate files in the same folder structure that the model metadata was loaded from. See the API docs for more information.
• DAX Optimizer users can now also view the results for RLS and Calculation Item expressions through our DAX Optimizer Integration.
• You can now script individual objects as TMDL (Tabular Model Definition Language) through the TOM Explorer. This is useful when you want to copy TMDL scripts from Tabular Editor to Power BI Desktop. Right-click an object and choose Export script > TMDL. You'll have the option of exporting the script to a file or directly to the clipboard.

Bugfixes in 3.21.0

• Sorting by "Progress" or "Duration" in the Data Refresh view should now work correctly. Moreover, the "Duration" is no longer reset at the end of the refresh operation, for certain objects.
• Various bugfixes related to the view of progress events in the Data Refresh view. For example, progress events should now arrive even if a previous session has expired (for example when Tabular Editor was idle for 60 minutes or more).
• When partition deployment is disabled, or enabled but with incremental refresh partitions skipped, we now also leave the refresh policy settings on the table untouched (i.e. Source Expression, Polling Expression, etc.)
• The Semantic Analyzer should no longer report an error when tables are connected by only inactive relationships, and a relationship is activated using the USERELATIONSHIP function.
• Fixed a bug where the Semantic Analyzer determined the wrong resulting data type when using the GENERATESERIES function.
• Fixed a bug with the Semantic Analyzer reporting false "not found" errors when DEFINEing and referencing tables and columns inside a DAX script/query.
• It is no longer possible to assign an empty name to an object through the TOM Explorer.
• Certain words that were previously treated as reserved keywords, will no longer produce a semantic error, when used as unquoted table / variable references.
• Fixed a bug where the DAX debugger didn't correctly gray out the inactive branch when using IF.EAGER or IF with only 2 parameters.
• When opening a model with a workspace connection (i.e. Tabular Editor 3's Workspace Mode feature), we now correctly show the Microsoft Entra MFA prompt, if this was the authentication method used when the connection to the workspace database was originally established.
• Our code editors now fully supports wide characters / unicode emojis (note, this is not an endorsement of emojis in DAX, but it is now possible to use them without breaking the editor :)).
• If the .tmuo file contains invalid JSON, Tabular Editor will now show an error message and continue loading the model without the options specified in the file, instead of causing an unhandled exception.
• Fixed a bug where the Refresh Policy options would not appear in the Properties grid on a table in a model loaded from disk, if the table did not have any partitions specified in the loaded metadata.
• The Ctrl+U (Uncomment Code) and Ctrl+/ (Toggle comments) shortcuts were not working properly because of conflicts with other editor keyboard shortcuts. We have removed the default shortcuts from the conflicting commands. If you need keyboard bindings for the Editor.Lowercase and Editor.Uppercase commands (previously Ctrl+U and Ctrl+Shift+U respectively), you can set these up through Tools > Preferences > Keyboard.

---

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

---

Tabular Editor 3.19.0

Tabular Editor 3.19.0 .NET 8 downloads:

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

Tabular Editor 3.19.0 .NET 6 downloads:

• Download Tabular Editor 3.19.0 (64 bit)
• Download Tabular Editor 3.19.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 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](https://docs.tabulareditor.com/onboarding/index.h...

Tabular Editor 3.18.0

Tabular Editor 3.18.0 .NET 8 downloads:

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

Tabular Editor 3.18.0 .NET 6 downloads:

• Download Tabular Editor 3.18.0 (64 bit)
• Download Tabular Editor 3.18.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 activated after installation. You can also purchase a license.

---

Important

.NET 6 will be going out-of-support in 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.18.0

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

• Our DAX Optimizer integration is now out of preview, and we've also made a few updates, so that it now supports the new evaluation metrics that were part of DAX Optimizer 1.2. Oh, and by the way - all Enterprise Edition Tabular Editor 3 users now get 4 free DAX Optimizer runs per day. Download Tabular Editor 3.18.0 from one of the links above, and get your DAX Optimizer redemption code through the Help > About Tabular Editor menu item.
• We're happy to introduce a new feature across all DAX editors in Tabular Editor 3: Code Actions. This productivity feature discretely provides suggestions for improving your DAX code and lets you apply the suggestion with a single click. For example, the feature can be used to remove unused variables, follow best practices for column and measure references, rewrite table filters as more efficient column filters, and much, much more. We plan to add additional actions in future releases, so stay tuned!
• After we upgraded to the latest version of the Microsoft AMO/TOM client library, the behavior of the Integrated authentication option changed, such that the Entra ID account selector/MFA popup is no longer shown, if the Windows OS is already connected to an Entra ID account. As such, we've added a new authentication option, Microsoft Entra MFA, which will force the account selector/MFA popup to appear, letting you choose a different account than the one currently logged in to Windows, if needed.

Improvements in 3.18.0

• The user interface preferences have been expanded to allow hiding model source details from the title bar, helping to protect sensitive information during recordings and presentations.
• The user interface preferences now include a new "Recent Items" section. This section enables customization of the number of recent files and models displayed in the file menu and the servers displayed in recent connections. The new preferences also allow clearing these items.
• The Semantic Analyzer now shows a warning if a variable is used directly as the 1st argument of CALCULATE or CALCULATETABLE. Since variables are unaffected by context transitions or modified filter contexts, using a variable this way is most likely unintentional.
• Our SQL editor now uses an improved color scheme, making it easier to distinguish SQL keywords from identifiers.
• Upgraded AMO/TOM and other dependencies to their latest versions.
• We're now using Compatibility Level 1606 for new Power BI / Fabric semantic models. At this level, a new Model property ValueFilterBehavior is available, which can be used to control the auto-exist behavior of SUMMARIZECOLUMNS.
• We've added support for the TOM ChangedProperties collection (on Tables, Measures, Columns, and a few other objects). This collection is used on composite or Direct Lake models, to indicate that a property (such as a column Name) has changed, and should no longer be synchronized from the underlying source.
• Upgraded VertiPaq Analyzer to latest version (1.7.2), which fixes an issue regarding extracting stats on a model containing Field Parameters / Group By Columns.
• Upgraded our version of the Snowflake .NET connector to v. 4.1.0. This addresses the following vulnerabilities: CVE-2023-34230 and CVE-2023-51662.
• The diagram component should now be considerably faster when working with large diagrams with many relationships.
• Columns in the Data Preview can now be hidden by right-clicking on the column header and selecting "Hide This Column". To show hidden columns, right-click on a column header and select "Column chooser". This will bring up a window from where you can access previously hidden columns.

Bugfixes in 3.18.0

• Fixed a bug where the "Server" dropdown in the Load semantic model from database dialog would not show recently used servers.
• Data Preview settings (sort order, filters, etc.) are now preserved after refreshing the preview, resolving a previous bug where settings were not maintained.
• Fixed a crash which could happen when undoing (Ctrl+Z) while or immediately after using the "Rename" refactoring in a DAX editor.
• The main UI is now properly locked from user interactions while the "Please wait" dialog is shown, such as when performing a table schema update.
• Semantic Analyzer should no longer show a warning when referencing the internal "FormatString" measure in a DAX expression. As a consequence, it is now possible to debug queries that contain such references (even though the FormatString expression itself cannot currently be debugged), see #1377.

Known issues in 3.18.0

• If you're getting the error message Can't obtain account information for '(e-mail)' while trying to refresh the token. it usually helps to perform the operation again. This is an issue in the newer versions of the AMO/TOM client libraries. You should also be able to avoid this issue by choosing the Microsoft Entra MFA authentication option, instead of the Integrated option, when initially connecting.

---

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 your DAX.

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

Tabular Editor 3.17.1

Tabular Editor 3.17.1 .NET 8 downloads:

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

Tabular Editor 3.17.1 .NET 6 downloads:

• Download Tabular Editor 3.17.1 (64 bit)
• Download Tabular Editor 3.17.1 (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 activated after installation. You can also purchase a license.

---

Bugfixes in 3.17.1

• Fixed a bug related to OS regional settings, which would cause a crash upon entering the Preferences dialog for the first time.

New in 3.17.0

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

• We're excited to let you know, that Tabular Editor 3 is now available for .NET 8. We will continue to support .NET 6 until the end of 2024, however we recommend switching to the .NET 8 version as soon as possible. In our testing, the .NET 8 version starts up ~20% faster, while also consuming less memory.
• The portable builds of Tabular Editor 3 now include the relevant .NET runtime, so you no longer need to install the .NET 6/8 Windows Desktop runtime separately.

Important

.NET 6 will be going out-of-support in 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.

Improvements in 3.17.0

• DAX query results and table previews now show the "long time format" for datetime values, rather than "short time". This way, seconds are also shown in the result grid.
• Shared expressions can now be excluded from being deployed using the Deployment Wizard. This enhancement allows you to retain existing shared expressions on the destination server as-is, when deploying a model, even if shared expressions were created/deleted/modified in the model being deployed.
• The DAX debugger Locals window now lets you "inspect" results, similar to the Watch window. By default, inspector results are shown in a popup dialog rather than as a new DAX Query, but you can control this behavior under Tools > Preferences > DAX Debugger. Click the magnifying glass icon next to the value in the Locals or Watch view to inspect the value. See the updated DAX Debugger documentation for more information.
• When debugging a scalar predicate in a filter argument of CALCULATE or CALCULATETABLE, the Locals view now shows additional details about the scalar predicate and the resulting filter expression. See the updated DAX Debugger documentation for more information.
• DAX scripts can now be applied when the script contains semantic errors. A warning will be shown if there are any semantic errors to make the end user aware if they want to proceed with the current errors or cancel and fix the semantic errors. Syntax errors, on the other hand, will still prevent the script from being applied.
• Added auto-complete support for a few more DAX INFO.* functions.
• The DAX Optimizer Integration (Preview) feature now lets you switch between personal or group accounts in group licensing scenarios. You can choose which account you want to use, through the Options dropdow menu. See also #1288. Moreover, you can now change the Fixed or Ignored status of an issue directly from the DAX Optimizer Results view.
• The Table Import Wizard and Update Table Schema feature now supports Databricks Multicloud, in addition to Azure Databricks. For more information, see the discussion on #1347.
• The Preferences for the VertiPaq Analyzer were expanded to configure the column batch size. This preference controls the number of columns processed at a time during column statistics analysis and it can be found under Tools > Preferences > VertiPaq Analyzer. The default value for this preference is 50.
• Custom formatting applied to Pivot Grids (icons, data bars, highlighted cells, etc.) is now preserved when the Pivot Grid layout is saved to a file and later reloaded.
• Pivot Grids now also preserve any sorting applied to fields when the grid is refreshed or when the grid layout is saved to a file and later reloaded.

Bugfixes in 3.17.0

• Fixed an bug introduced in 3.16.0, which caused an application freeze for several seconds after loading a diagram file (.te3diag)
• Fixed an issue that prevented saving the options in the "Find/Replace" dialog box between sessions, when using the "Find all" button. Now, the last search preferences will be retained in the next session.
• Fixed an issue that prevented the deployment of deletions for data sources, roles, and role members to an existing model. Previously, the corresponding checkboxes in the Deployment Wizard were disabled when there were no data sources or roles in the model. Now, these checkboxes remain enabled when deploying changes to an existing model, allowing for the deployment of these object's deletions.
• Fixed an issue that prevented files with the .ovpax extension from opening as a file or model. The possibility to open .ovpax files and models is now supported.
• Fixed a bug where the wrong file type might have been suggested by the file dialog window when exporting obfuscated files from the VertiPaq Analyzer. Now, when exporting an obfuscated file, the save dialog will correctly suggest using the ".ovpax" extension.
• Fixed a bug where toolbar buttons would stay disabled when the Expression Editor was docked as a tool window rather than as a document tab.
• Fixed a bug that prevented opening semantic models saved as ".tmdl" with Power BI Project files (PBIP).
• Fixed a bug that caused the application to hang during manual activation.
• Macro recorder should no longer generate duplicate code. Moreover, the recorder should now also generate code when objects are deleted.
• Auto formatting settings for DAX Editors, including DAX Query, DAX Script, and DAX expressions in the Expression Editor, are now applied instantly, without the need to restart the application.
• Fixed an issue where unchecking the Encrypt connection option did not disable encryption in the connection string for Microsoft SQL Server data sources.
• Fixed a bug where ODBC username and password were not added to the connection string when importing tables or updating table schema. This issue would prevent users from importing tables or updating table schema when using ODBC connections against some data sources, such as Snowflake or Oracle.
• Fixed a bug where it was not possible to list the ODBC DSNs when importing tables, if no User DSNs were present on the machine.
• When querying schema information from an ODBC source, we now use various fallbacks, which should improve compatibility with more ODBC drivers, such as the Oracle in OraClient12Home1 driver.
• Fixed a bug where data sources referenced in M queries would appear as implicit data sources in the Import Table Wizard.
• Fixed a bug where some Pivot Grid toolbar buttons would remain disabled, after a Pivot Grid was reloaded from a file.
• Fixed a bug where constants in M expressions (such as Order.Ascending) would result in an Unknown identifier error, when using the Update Table Schema feature. See #1362.
• When using the DAX DIVIDE function with a non-numeric 3rd argument, the DAX parser now correctly determines the resulting data type to be Variant.
• Fixed a bug that prevented Tabular Editor from loading model metadata from a TMDL folder with no database.tmdl file.

Note

Microsoft has announced that TMDL is in GA as of August 2nd, 2024. Please note that Tabular Editor 3 is using a version of the AMO/TOM client library, which was released before TMDL was announced as GA. This version should still be fully compatible with TMDL, however, we recommend keeping a backup of your ...

Tabular Editor 3.17.0

Tabular Editor 3.17.0 .NET 8 downloads:

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

Tabular Editor 3.17.0 .NET 6 downloads:

• Download Tabular Editor 3.17.0 (64 bit)
• Download Tabular Editor 3.17.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 activated after installation. You can also purchase a license.

---

New in 3.17.0

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

• We're excited to let you know, that Tabular Editor 3 is now available for .NET 8. We will continue to support .NET 6 until the end of 2024, however we recommend switching to the .NET 8 version as soon as possible. In our testing, the .NET 8 version starts up ~20% faster, while also consuming less memory.
• The portable builds of Tabular Editor 3 now include the relevant .NET runtime, so you no longer need to install the .NET 6/8 Windows Desktop runtime separately.

Important

.NET 6 will be going out-of-support in 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.

Improvements in 3.17.0

• DAX query results and table previews now show the "long time format" for datetime values, rather than "short time". This way, seconds are also shown in the result grid.
• Shared expressions can now be excluded from being deployed using the Deployment Wizard. This enhancement allows you to retain existing shared expressions on the destination server as-is, when deploying a model, even if shared expressions were created/deleted/modified in the model being deployed.
• The DAX debugger Locals window now lets you "inspect" results, similar to the Watch window. By default, inspector results are shown in a popup dialog rather than as a new DAX Query, but you can control this behavior under Tools > Preferences > DAX Debugger. Click the magnifying glass icon next to the value in the Locals or Watch view to inspect the value. See the updated DAX Debugger documentation for more information.
• When debugging a scalar predicate in a filter argument of CALCULATE or CALCULATETABLE, the Locals view now shows additional details about the scalar predicate and the resulting filter expression. See the updated DAX Debugger documentation for more information.
• DAX scripts can now be applied when the script contains semantic errors. A warning will be shown if there are any semantic errors to make the end user aware if they want to proceed with the current errors or cancel and fix the semantic errors. Syntax errors, on the other hand, will still prevent the script from being applied.
• Added auto-complete support for a few more DAX INFO.* functions.
• The DAX Optimizer Integration (Preview) feature now lets you switch between personal or group accounts in group licensing scenarios. You can choose which account you want to use, through the Options dropdow menu. See also #1288. Moreover, you can now change the Fixed or Ignored status of an issue directly from the DAX Optimizer Results view.
• The Table Import Wizard and Update Table Schema feature now supports Databricks Multicloud, in addition to Azure Databricks. For more information, see the discussion on #1347.
• The Preferences for the VertiPaq Analyzer were expanded to configure the column batch size. This preference controls the number of columns processed at a time during column statistics analysis and it can be found under Tools > Preferences > VertiPaq Analyzer. The default value for this preference is 50.
• Custom formatting applied to Pivot Grids (icons, data bars, highlighted cells, etc.) is now preserved when the Pivot Grid layout is saved to a file and later reloaded.
• Pivot Grids now also preserve any sorting applied to fields when the grid is refreshed or when the grid layout is saved to a file and later reloaded.

Bugfixes in 3.17.0

• Fixed an bug introduced in 3.16.0, which caused an application freeze for several seconds after loading a diagram file (.te3diag)
• Fixed an issue that prevented saving the options in the "Find/Replace" dialog box between sessions, when using the "Find all" button. Now, the last search preferences will be retained in the next session.
• Fixed an issue that prevented the deployment of deletions for data sources, roles, and role members to an existing model. Previously, the corresponding checkboxes in the Deployment Wizard were disabled when there were no data sources or roles in the model. Now, these checkboxes remain enabled when deploying changes to an existing model, allowing for the deployment of these object's deletions.
• Fixed an issue that prevented files with the .ovpax extension from opening as a file or model. The possibility to open .ovpax files and models is now supported.
• Fixed a bug where the wrong file type might have been suggested by the file dialog window when exporting obfuscated files from the VertiPaq Analyzer. Now, when exporting an obfuscated file, the save dialog will correctly suggest using the ".ovpax" extension.
• Fixed a bug where toolbar buttons would stay disabled when the Expression Editor was docked as a tool window rather than as a document tab.
• Fixed a bug that prevented opening semantic models saved as ".tmdl" with Power BI Project files (PBIP).
• Fixed a bug that caused the application to hang during manual activation.
• Macro recorder should no longer generate duplicate code. Moreover, the recorder should now also generate code when objects are deleted.
• Auto formatting settings for DAX Editors, including DAX Query, DAX Script, and DAX expressions in the Expression Editor, are now applied instantly, without the need to restart the application.
• Fixed an issue where unchecking the Encrypt connection option did not disable encryption in the connection string for Microsoft SQL Server data sources.
• Fixed a bug where ODBC username and password were not added to the connection string when importing tables or updating table schema. This issue would prevent users from importing tables or updating table schema when using ODBC connections against some data sources, such as Snowflake or Oracle.
• Fixed a bug where it was not possible to list the ODBC DSNs when importing tables, if no User DSNs were present on the machine.
• When querying schema information from an ODBC source, we now use various fallbacks, which should improve compatibility with more ODBC drivers, such as the Oracle in OraClient12Home1 driver.
• Fixed a bug where data sources referenced in M queries would appear as implicit data sources in the Import Table Wizard.
• Fixed a bug where some Pivot Grid toolbar buttons would remain disabled, after a Pivot Grid was reloaded from a file.
• Fixed a bug where constants in M expressions (such as Order.Ascending) would result in an Unknown identifier error, when using the Update Table Schema feature. See #1362.
• When using the DAX DIVIDE function with a non-numeric 3rd argument, the DAX parser now correctly determines the resulting data type to be Variant.
• Fixed a bug that prevented Tabular Editor from loading model metadata from a TMDL folder with no database.tmdl file.

Note

Microsoft has announced that TMDL is in GA as of August 2nd, 2024. Please note that Tabular Editor 3 is using a version of the AMO/TOM client library, which was released before TMDL was announced as GA. This version should still be fully compatible with TMDL, however, we recommend keeping a backup of your TMSL (.bim) files, just in case.

---

Coming from Tabular Editor 2.x?

Watch this video to get an idea of t...

Tabular Editor 3.16.2

Tabular Editor 3.16.2 downloads:

• Download Tabular Editor 3.16.2 (64 bit) (recommended)
• Download Tabular Editor 3.16.2 (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 uses .NET 6. If you're using the portable version, you may have to manually install the .NET 6.0 Runtime for Desktop before you can launch Tabular Editor 3.

---

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

Improvements in 3.16.2

• Rolled back AMO/TOM to 19.79.1.1, as the 19.80.0 version introduced various issues related to MFA authentication and other XMLA connectivity issues. See #1317 and #1322.

Bugfixes in 3.16.1

• Fixed a bug that prevented saved diagram files (.te3diag) from being opened correctly, see #1313

Improvements in 3.16.1

• DAX query results now show the "long time format" for datetime values, rather than "short time". This way, seconds are also shown in the result grid.

New in 3.16.0

We have substantially overhauled how Pivot Grids work in this release. Some highlights include:

• Pivot Grid layouts can now be saved and loaded to/from files! A new file format, .te3pivot is used to store a JSON representation of the Pivot Grid layout.
• Hidden objects (measures, columns, hierarchies) can now be used in a Pivot Grid, and object renames should no longer cause the Pivot Grid to lose its layout or clear any filters.
• A new and improved Pivot Grid Field List, which is now shown by default, and provides a more familiar experience when adding fields to the Pivot Grid.

Head on over to the Pivot Grid documentation to learn more about these changes.

Improvements in 3.16.0

• Reduced the number of useless/redundant error messages that are shown, when DAX expression contain syntax/semantic errors.
• DAX scripts now support unspecified/empty expressions. This allows you to specify a DAX script that does not modify existing expressions on objects, or a script that explicitly sets an expression to be empty.
• You can now export DAX query results to CSV/Excel. Look for the Export data and Export data (all results) options under the Query menu.
• When exporting VertiPaq Analyzer statistics, we now suggest a default name for the VPAX file based on the database name.
• We changed the default keyboard shortcuts for Editor.Dax.CollapseAllFolds, Editor.Dax.ExpandAllFolds and Editor.Dax.ToggleAllFolds from Ctrl+Alt+(key) to Ctrl+Shift+(key). This is to avoid conflicts with certain characters that require the AltGr key (which is equivalent to Ctrl+Alt) to be typed on non-US keyboards. The Ctrl+Shift+(key) shortcuts were previously used by Editor.Dax.CollapseFold, Editor.Dax.ExpandFold and Editor.Dax.ToggleFold. Their defaults have been changed to Ctrl+(key).
• Updated AMO/TOM to 19.80.0.
• Menus and toolbars are now locked in place by default, preventing accidental repositioning. To unlock them, go to Tools > Customize... > Options and uncheck the Lock menus and toolbars option.
• Our DAX semantic analyzer now supports the WITH VISUAL SHAPE syntax used in DAX queries that contain visual calculations. Note that debugging such queries is not yet supported (as only measures can be debugged, and visual calculations are not measures).
• Show a warning when debugging a Pivot Grid cell value or DAX query that includes calculation items in the filter context (which the TE3 debugger currently doesn't support).

Bugfixes in 3.16.0

• Pressing control-key combinations that do not have any keybinding assigned, should no longer cause special control chars to be inserted in code editors.
• Macros that have been modified and saved, should no longer execute multiple times when invoked through the UI.
• The .Output() method should now show the output dialog on subsequent macro executions, even when the Don't show more outputs option was checked on a previous execution.
• Unquoted table name references that also happen to be DAX keywords (such as Currency), will no longer be treated as keywords during auto-formatting (i.e. they will not be capitalized). Moreover, certain object properties in DAX scripts can now also be empty. View the updated DAX Scripts documentation for more information.
• Errors during DAX script execution are now handled gracefully, and the changes made by the script before the error was encountered, are automatically rolled back.
• Fixed a bug where macro buttons assigned to custom toolbars did not persist after restarting the application.
• Fixed a bug that would cause Tabular Editor to crash when using the ForEach<T>(IEnumerable<T>, Action<T>) extension method in a C# script.
• Fixed bugs regarding removing/resetting shortcut keys, which did not work correctly for some commands.
• Fixed a bug where the Save button would remain disabled after a refresh operation finishes.
• Fixed a bug where certain actions could cause the TOM Explorer to lock up and not behave correctly until the application was restarted.
• Fixed a bug where deleting an object in the TOM Explorer would cause the selection to jump to the Model node, rather than the closest parent node of the deleted object.
• Fixed several bugs related to Pivot Grids.
• The semantic analyzer should no longer produce false errors when comparing against BLANK() in expressions such as "string value" IN { BLANK() }.
• Fixed a bug where changing serialization settings did not persist when a model was loaded from a TMDL folder. See #1285.
• When sorting a column in the Table Preview, where the column has IsAvailableInMDX = false (that is, no attribute hierarchies have been created for the column), we will not fallback to issue TOPN queries, since TOPNSKIP doesn't support sorting by columns with no attribute hierarchies.

---

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

---

Tabular Editor 3.16.1

Tabular Editor 3.16.1 downloads:

• Download Tabular Editor 3.16.1 (64 bit) (recommended)
• Download Tabular Editor 3.16.1 (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 uses .NET 6. If you're using the portable version, you may have to manually install the .NET 6.0 Runtime for Desktop before you can launch Tabular Editor 3.

Bugfixes in 3.16.1

• Fixed a bug that prevented saved diagram files (.te3diag) from being opened correctly, see #1313

Improvements in 3.16.1

• DAX query results now use the "long time format" for datetime values, rather than "short time". This way, seconds are also shown in the result grid.

New in 3.16.0

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

We have substantially overhauled how Pivot Grids work in this release. Some highlights include:

• Pivot Grid layouts can now be saved and loaded to/from files! A new file format, .te3pivot is used to store a JSON representation of the Pivot Grid layout.
• Hidden objects (measures, columns, hierarchies) can now be used in a Pivot Grid, and object renames should no longer cause the Pivot Grid to lose its layout or clear any filters.
• A new and improved Pivot Grid Field List, which is now shown by default, and provides a more familiar experience when adding fields to the Pivot Grid.

Head on over to the Pivot Grid documentation to learn more about these changes.

Improvements in 3.16.0

• Reduced the number of useless/redundant error messages that are shown, when DAX expression contain syntax/semantic errors.
• DAX scripts now support unspecified/empty expressions. This allows you to specify a DAX script that does not modify existing expressions on objects, or a script that explicitly sets an expression to be empty.
• You can now export DAX query results to CSV/Excel. Look for the Export data and Export data (all results) options under the Query menu.
• When exporting VertiPaq Analyzer statistics, we now suggest a default name for the VPAX file based on the database name.
• We changed the default keyboard shortcuts for Editor.Dax.CollapseAllFolds, Editor.Dax.ExpandAllFolds and Editor.Dax.ToggleAllFolds from Ctrl+Alt+(key) to Ctrl+Shift+(key). This is to avoid conflicts with certain characters that require the AltGr key (which is equivalent to Ctrl+Alt) to be typed on non-US keyboards. The Ctrl+Shift+(key) shortcuts were previously used by Editor.Dax.CollapseFold, Editor.Dax.ExpandFold and Editor.Dax.ToggleFold. Their defaults have been changed to Ctrl+(key).
• Updated AMO/TOM to 19.80.0.
• Menus and toolbars are now locked in place by default, preventing accidental repositioning. To unlock them, go to Tools > Customize... > Options and uncheck the Lock menus and toolbars option.
• Our DAX semantic analyzer now supports the WITH VISUAL SHAPE syntax used in DAX queries that contain visual calculations. Note that debugging such queries is not yet supported (as only measures can be debugged, and visual calculations are not measures).
• Show a warning when debugging a Pivot Grid cell value or DAX query that includes calculation items in the filter context (which the TE3 debugger currently doesn't support).

Bugfixes in 3.16.0

• Pressing control-key combinations that do not have any keybinding assigned, should no longer cause special control chars to be inserted in code editors.
• Macros that have been modified and saved, should no longer execute multiple times when invoked through the UI.
• The .Output() method should now show the output dialog on subsequent macro executions, even when the Don't show more outputs option was checked on a previous execution.
• Unquoted table name references that also happen to be DAX keywords (such as Currency), will no longer be treated as keywords during auto-formatting (i.e. they will not be capitalized). Moreover, certain object properties in DAX scripts can now also be empty. View the updated DAX Scripts documentation for more information.
• Errors during DAX script execution are now handled gracefully, and the changes made by the script before the error was encountered, are automatically rolled back.
• Fixed a bug where macro buttons assigned to custom toolbars did not persist after restarting the application.
• Fixed a bug that would cause Tabular Editor to crash when using the ForEach<T>(IEnumerable<T>, Action<T>) extension method in a C# script.
• Fixed bugs regarding removing/resetting shortcut keys, which did not work correctly for some commands.
• Fixed a bug where the Save button would remain disabled after a refresh operation finishes.
• Fixed a bug where certain actions could cause the TOM Explorer to lock up and not behave correctly until the application was restarted.
• Fixed a bug where deleting an object in the TOM Explorer would cause the selection to jump to the Model node, rather than the closest parent node of the deleted object.
• Fixed several bugs related to Pivot Grids.
• The semantic analyzer should no longer produce false errors when comparing against BLANK() in expressions such as "string value" IN { BLANK() }.
• Fixed a bug where changing serialization settings did not persist when a model was loaded from a TMDL folder. See #1285.
• When sorting a column in the Table Preview, where the column has IsAvailableInMDX = false (that is, no attribute hierarchies have been created for the column), we will not fallback to issue TOPN queries, since TOPNSKIP doesn't support sorting by columns with no attribute hierarchies.

---

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

---