Tabular Editor 3.11.0
Tabular Editor 3.11.0 downloads:
- Download Tabular Editor 3.11.0 (64 bit) (recommended)
- Download Tabular Editor 3.11.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.11.0
Check out our release blog to get a brief overview of the most important updates in this release.
- As noted in last months' release notes, Tabular Editor did not let you create a Direct Lake dataset from scratch. This is now possible! The only prerequisite is that the model does not already have any tables or explicit data sources defined, and that its Compatibility Mode is set to PowerBI. Check out our blog post on DirectLake, if you want to learn more.
Warning
Once you make any changes to a Direct Lake dataset through the XMLA endpoint, you will no longer be able to open that dataset in the Web Modelling feature of Fabric.
Improvements in 3.11.0
- We're now using using the latest version of AMO/TOM and TMDL, which includes a number of bugfixes and stability improvements.
Note
TMDL is still in preview, and as such, this feature must also be considered a preview feature of Tabular Editor 3. Make sure to keep a Model.bim / Database.json backup of your model metadata to avoid losing work.
- Our DAX parser and autocomplete now supports the newly added 3rd parameter to
MINX
/MAXX
. Moreover, we now also provide suggestions for theMATCHBY
function, which can be used as an optional parameter of window functions. - The Native Query option of the Table Import Wizard is now available when importing from Databricks, provided a catalog has been specified.
Bugfixes in 3.11.0
- The list of reserved table names in DAX has been updated using the
$system.discover_keywords
DMV. The consequence is that our built-in DAX formatter now correctly applies quotes on certain table names, which are also reserved words. For example, a reference to a table namedstatus
will now always be quoted. See #991. - Autocomplete now suggests proper keywords for the <Skip> parameter of DAX window functions such as
RANK
, etc. - Batch Rename now works for folders, see #797.
- Fixed some issues regarding custom layouts, see #711. Also fixed an issue where customizations to the built-in menus, were not properly persisted.
- Fixed a bug in the Deployment Wizard, when the model contains an incremental refresh table with no partitions. In this case, the deployment wizard UI did not allow the user to skip partition deployment of this table which would cause an invalid TMSL to be generated generated (one with no partitions for the table in question).
- Fixed a bug, where running a DAX query with no whitespace between
EVALUATE
and the following expression would cause an error. - Fixed numerous issues with the DAX debugger. See #954, #971 and #984.
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