TabularEditor/TabularEditor3 3.7.1

Tabular Editor 3.7.1

on GitHub

• Download Tabular Editor 3.7.1 (64 bit) (recommended)
• Download Tabular Editor 3.7.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.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.

Bugfixes in 3.7.1

• Fixed the "Object reference not set to an instance of an object", which would occur when attempting to create a new model using a workspace database.

New in 3.7.0

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

• This release introduces the Metadata Translations Editor, which provides a fast an easy way to view, compare and edit all metadata translations applied across model objects.
• Tabular Editor 3 now supports the new Tabular Model Definition Language (TMDL) as a format for saving/loading model metadata. You can enable TMDL (preview) serialization mode under Preferences > Tools > Save-to-folder.

Minor improvements in 3.7.0

• Now using latest version of VertiPaq Analyzer. This fixes an issue with collecting stats on models with Dynamic Format Strings, among other things.
• We now show a more meaningful error message, when a paste operation fails because of incompatible model metadata.
• Analysis Services trace events that are received after a data refresh job completes, are now correctly assigned to that job, enabling proper propagation of error/warning messages, as well as progress counts. See #735.
• The data preview window is now able to use the DAX OFFSET function, which enables the preview to show all rows of non-DirectQuery tables, even when a model is in DirectQuery mode (such as when hybrid tables are present in the model), see #500, #837.
• When deplying a model as a new database, we now add a dummy partition to tables that use incremental refresh policy, when no partitions are present in the model metadata, to ensure the deployment succeeds.
• Data preview retains any filters applied, when a table is refreshed/processed. See #780.
• When a table does not contain columns in a non-queryable state, the data preview now uses the table name directly in the generated DAX query, instead of wrapping it in a call to SELECTCOLUMNS. This should speed up the data preview on older versions of Analysis Services. See #126.
• TE3 now uses the latest version of Microsoft.Identity.Client.
• Offline schema detection now supports using Shared (M) Expressions which define custom functions.

Bugfixes in 3.7.0

• There was a problem in the newest version of AdomdClient used in 3.6.0, which causes a Pivot Grid to fail with an XML error message, when connected to the Power BI XMLA endpoint. We have downgraded AdomdClient to 19.55.3.1, which solves this issue for now.
• Fixed an issue where local instances of Power BI Desktop were not shown in the "Local instances" dropdown.
• Fixed an issue where TE3 would not allow loading a model that did not have a database name specified.
• The "Please Wait" dialogs should no longer obstruct Azure AD sign-in windows.
• Stability improvements.
• Fixed an issue where the application would crash when attempting to copy/paste measures with dynamic format strings, see #1099.
• DAX scripting of measures with format strings/dynamic format strings, now works as intended.
• Query-scoped columns are now handled correctly by the DAX semantic analyzer and auto-complete feature. See #890.
• Open Model/File dialogs now correctly filters "database.json" files instead of showing all .json files in a folder.
• Fixed some visual issues with buttons on various prompt dialogs.
• Fixed an issue where the database selection is incorrect, when the list is filtered. See #886.
• Fixed an issue where the "Save Model" action (Ctrl+Alt+S) was not enabled, even though the message bar indicated that the model had unsaved changes.
• Fixed an issue with "phantom" semantic errors in the DAX Editor, see #792.
• Preview data should now respect the format string assigned to a column, see #820.
• DAX query results should now show the time portion of DateTime values, when it is not 00:00:00.

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