Skip to content

Releases: TabularEditor/TabularEditor3

Tabular Editor 3.12.1

01 Dec 15:37
@otykier otykier
3.12.1
d1efbf2
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Tabular Editor 3.12.1

Downloads

Tabular Editor 3.12.1 downloads:

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

  • Fixed an issue that caused a crash in the DAX Editor, when typing out new measure definitions in the query, see #1183.

New in 3.12.0

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

  • Tabular Editor now displays a "What's New" page when the application is updated. The page informs you of new Tabular Editor features, along with community updates and other relevant news for Tabular Editor users. If the page is hidden, you can access it from the Help > What's New. You can disable this feature by unchecking Tools > Preferences > Updates and Feedback > Show "What's New" page on startup.
  • When prototyping new measures, it is quite common to specify them within the DEFINE block of a DAX query. In this update, we've added an easy way to create/update model measures based on measures defined within the DAX query. On the toolbar, through the Query menu, and through the right-click context menu of the DAX query editor, you will see 4 new options light up, which work very similarly to the "Apply" actions in DAX Scripts, with the exception that only a measures' name and expression is applied (since it's not possible to specify other properties like Description, Display Folder, etc. through a DAX query). More details in the blog post.
  • Please be aware that we're now using a new certificate to sign the binaries, in case your IT organization needs to expclitly approve 3rd party code certificates. The new certificate is issued by GlobalSign GCC and the certificate is issued directly to Tabular Editor ApS.

Improvements in 3.12.0

  • We have hidden the special RowNumber column from the various VertiPaq Analyzer views, to align with other tools (DAX Studio, DAX Optimizer, etc.).
  • AMO/TOM has been updated to 19.69.6.2, meaning Tabular Editor 3 now supports the latest data modelling features. For example, we now support the Model.DirectLakeBehavior property, letting you control whether DirectQuery fallback on DirectLake models should occur or not.
  • TMDL has also been updated to the latest version.

Note

TMDL is still in preview and should not be used in production. We're aware of a deserialization issue in AMO/TOM 19.69.6.2, when a table has an incremental refresh policy applied. This will be fixed in the next release of AMO/TOM.

  • You can now create BPA rules that inspect DAX tokens returned from the IDaxDependantObject.Tokenize() method, the same way as in TE2.
  • We now show a warning in the DAX editor, when a variable is declared but never used. See #934. Such variables should generally be removed to keep your DAX tidy.
  • When importing tables or updating table schema from a T-SQL source, where the partition references a Stored Procedure, we now provide an option to execute the Stored Procedure, in cases where the resulting schema cannot be statically determined. This can happen, for example, when the stored procedure uses temp tables. The user is always prompted with an option to cancel the operation, before the stored procedure is executed.
  • Tabular Editor now allows importing tables from Snowflake using Native Query, see #949. Note: For this option to be available, you must specify a database name in the Snowflake connection dialog.
  • You can now refresh individual tables or partitions in Direct Lake mode (this operation is also known as "framing").
  • Adding tables to a model in Direct Lake mode, will no longer prompt you for the type of partition to create (defaulting to an Entity Partition in Direct Lake mode).

Bugfixes in 3.12.0

  • Fixed an issue where the Rename Variable context menu option would not always be available, see #692.
  • Fixed an issue where username/passwords were not properly persisted for ODBC data connections. Tabular Editor will now prompt if the ODBC credentials are missing.
  • Fixed an issue where a Snowflake DSI ODBC connection string was not generated correctly, see #993.
  • When Tabular Editor generates T-SQL during table import/schema updates, we no longer use the IIF keyword, since this is not supported on Azure Synapse (dedicated SQL pools), see #1007.
  • When Tabular Editor generates the deployment TMSL script, we now automatically add a dummy partition to tables governed by incremental refresh, in case no partitions have been defined (otherwise, deployment would fail).
  • The Best Practice Analyzer should now gracefully handle BPA rules where the rule expression itself has an error (just like TE2).
  • Fixed an issue where the Last accessed column of VertiPaq Analyzer did not show correct info.
  • Fixed a minor glitch with VertiPaq Analyzer buttons not indicating correct state.
  • Emojis in the DAX editor should no longer cause random crashes, although auto-complete, auto-formatting, etc. will still not work.
  • Fixed an issue where setting the OLS Column Permission to "None" would cause the TOM Explorer to lock up.
  • Fixed a glitch in the "Save as Macro" dialog, which could cause a crash in some cases.
  • M partitions containing a comment on the last line should no longer produce an error when performing a schema update through Analysis Services/Power BI, see #1167.
  • The auto-complete popup should now have a suitable width on its first appearance, see #1152.

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

Assets 2
Loading

Tabular Editor 3.12.0

28 Nov 07:44
@otykier otykier
3.12.0
d1efbf2
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Tabular Editor 3.12.0

Tabular Editor 3.12.0

Downloads

Tabular Editor 3.12.0 downloads:

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

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

  • Tabular Editor now displays a "What's New" page when the application is updated. The page informs you of new Tabular Editor features, along with community updates and other relevant news for Tabular Editor users. If the page is hidden, you can access it from the Help > What's New. You can disable this feature by unchecking Tools > Preferences > Updates and Feedback > Show "What's New" page on startup.
  • When prototyping new measures, it is quite common to specify them within the DEFINE block of a DAX query. In this update, we've added an easy way to create/update model measures based on measures defined within the DAX query. On the toolbar, through the Query menu, and through the right-click context menu of the DAX query editor, you will see 4 new options light up, which work very similarly to the "Apply" actions in DAX Scripts, with the exception that only a measures' name and expression is applied (since it's not possible to specify other properties like Description, Display Folder, etc. through a DAX query). More details in the blog post.
  • Please be aware that we're now using a new certificate to sign the binaries, in case your IT organization needs to expclitly approve 3rd party code certificates. The new certificate is issued by GlobalSign GCC and the certificate is issued directly to Tabular Editor ApS.

Improvements in 3.12.0

  • We have hidden the special RowNumber column from the various VertiPaq Analyzer views, to align with other tools (DAX Studio, DAX Optimizer, etc.).
  • AMO/TOM has been updated to 19.69.6.2, meaning Tabular Editor 3 now supports the latest data modelling features. For example, we now support the Model.DirectLakeBehavior property, letting you control whether DirectQuery fallback on DirectLake models should occur or not.
  • TMDL has also been updated to the latest version.

Note

TMDL is still in preview and should not be used in production. We're aware of a deserialization issue in AMO/TOM 19.69.6.2, when a table has an incremental refresh policy applied. This will be fixed in the next release of AMO/TOM.

  • You can now create BPA rules that inspect DAX tokens returned from the IDaxDependantObject.Tokenize() method, the same way as in TE2.
  • We now show a warning in the DAX editor, when a variable is declared but never used. See #934. Such variables should generally be removed to keep your DAX tidy.
  • When importing tables or updating table schema from a T-SQL source, where the partition references a Stored Procedure, we now provide an option to execute the Stored Procedure, in cases where the resulting schema cannot be statically determined. This can happen, for example, when the stored procedure uses temp tables. The user is always prompted with an option to cancel the operation, before the stored procedure is executed.
  • Tabular Editor now allows importing tables from Snowflake using Native Query, see #949. Note: For this option to be available, you must specify a database name in the Snowflake connection dialog.
  • You can now refresh individual tables or partitions in Direct Lake mode (this operation is also known as "framing").
  • Adding tables to a model in Direct Lake mode, will no longer prompt you for the type of partition to create (defaulting to an Entity Partition in Direct Lake mode).

Bugfixes in 3.12.0

  • Fixed an issue where the Rename Variable context menu option would not always be available, see #692.
  • Fixed an issue where username/passwords were not properly persisted for ODBC data connections. Tabular Editor will now prompt if the ODBC credentials are missing.
  • Fixed an issue where a Snowflake DSI ODBC connection string was not generated correctly, see #993.
  • When Tabular Editor generates T-SQL during table import/schema updates, we no longer use the IIF keyword, since this is not supported on Azure Synapse (dedicated SQL pools), see #1007.
  • When Tabular Editor generates the deployment TMSL script, we now automatically add a dummy partition to tables governed by incremental refresh, in case no partitions have been defined (otherwise, deployment would fail).
  • The Best Practice Analyzer should now gracefully handle BPA rules where the rule expression itself has an error (just like TE2).
  • Fixed an issue where the Last accessed column of VertiPaq Analyzer did not show correct info.
  • Fixed a minor glitch with VertiPaq Analyzer buttons not indicating correct state.
  • Emojis in the DAX editor should no longer cause random crashes, although auto-complete, auto-formatting, etc. will still not work.
  • Fixed an issue where setting the OLS Column Permission to "None" would cause the TOM Explorer to lock up.
  • Fixed a glitch in the "Save as Macro" dialog, which could cause a crash in some cases.
  • M partitions containing a comment on the last line should no longer produce an error when performing a schema update through Analysis Services/Power BI, see #1167.
  • The auto-complete popup should now have a suitable width on its first appearance, see #1152.

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

Assets 2
Loading

Tabular Editor 3.11.0

25 Sep 13:23
@otykier otykier
3.11.0
68da71e
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Tabular Editor 3.11.0

Tabular Editor 3.11.0

Downloads

Tabular Editor 3.11.0 downloads:

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 DirectLake 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 DirectLake 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 the MATCHBY 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 named status 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

Assets 2
Loading

Tabular Editor 3.10.1

23 Aug 20:07
@otykier otykier
3.10.0
68da71e
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Tabular Editor 3.10.1

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

  • Fixed a bug that caused a crash whenever the user attempted to type a DAX expression in the DAX Debugger's Watch Expression window.

New in 3.10.0

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

Note

This version of Tabular Editor will let you import tables / update table schemas on models that already have a DirectLake connection. The Import Table Wizard does not yet support creating a new DirectLake connection on an empty model. This will be added in a future release.

Warning

Once you make any changes to a DirectLake dataset through the XMLA endpoint, you will no longer be able to open that dataset in the Web Modelling feature of Fabric.

  • C# scripts now support preprocessor directives to determine which version of Tabular Editor you're using. This allows you to write scripts that are compatible with both Tabular Editor 2 and Tabular Editor 3.

Improvements in 3.10.0

  • We're now using using the latest version of AMO/TOM. This update adds support for Binary XML, which should help speed up XMLA operations. More details in this Microsoft blog post.
  • We also updated TMDL to preview-3, which includes a number of bugfixes.

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.

  • When cloning objects, we now add the suffix "-Copy" instead of " Copy", to reduce the risk of leaving trailing blanks in object names, see #940.
  • The auto-complete popup now automatically adjusts its width to fit the widest item inside of it. See #965.
  • When a backup .bim file is saved for a Power BI Desktop model, we now use the name of the .pbix file, instead of the database GUID, see #958.
  • Table Preview performance improvements.

Bugfixes in 3.10.0

  • Fixed a bug that prevented Synonyms (linguistic metadata) to be persisted, when using Save to Folder.
  • Fixed a bug where the backup .bim file had an incorrect timstamp, see #967.
  • Fixed a bug that prevented the user from cancelling the deployment when the backup save fails for any reason.
  • Find Panel on Table Preview should now generate valid DAX search expressions behind the scenes, see #955.
  • Fixed an issue that caused the "Go to definition (F12)" action to be disabled when the caret was placed on a DAX function, see #962.
  • Fixed a bug that prevented loading models from .vpax files in some cases.
  • The height of the "result count" panel in DAX queries should now automatically adjust to fit its content.
  • The Properties grid now correctly displays multi-line expressions that happen to start with one or more line breaks, just like when editing the expression inside the grid.
  • Fixed a bug that could cause Pivot Grid to get stuck in an infinite error-message loop, when columns that were added to the Pivot Grid were deleted from the remote model.
  • Fixed a bug where macros added to the menu bar, would stop working after a restart of Tabular Editor.
  • Fixed a bug where attempting to perform a Schema Update on multiple tables originating from the same source table, would fail for all except one.

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

Assets 2
Loading

Tabular Editor 3.9.0

23 Aug 20:06
@otykier otykier
3.9.0
68da71e
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Tabular Editor 3.9.0

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

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

  • Customers on one of the Azure for Government cloud, can now specify the base url that Tabular Editor 3 should use, when connecting to the Power BI REST API, such as when importing tables from a Power BI Dataflow. This setting is specified under Tools > Preferences > Power BI > Power BI Service.
  • When selecting more than one cell in a DAX query result or a Pivot Grid, we now show a summary of the values selected in the application status bar (sum, minimum, maximum, average, etc.). Hold down Shift/Ctrl to select ranges the way you'd usually do. Shift+click on a column header will select all cells in that column. See #475.

Improvements in 3.9.0

  • We've rearranged some of the pages and sections of the preferences dialog, making it easier to navigate.
  • We're now using the latest version of TOM/AMO (19.65.7.2) and TMDL preview-3.
  • We've also updated AdomdClient to 19.65.7.2, which should improve the performance of our Pivot Grid component.
  • VertiPaq Analyzer has been updated to version 1.2.18.
  • When a calculated table is left with a blank expression, we now show the error icon immediately in the TOM Explorer.
  • It is now possible to add objects to Pivot Grids or Diagrams, even when those documents do not have focus (assuming no more than one such document is open). Moreover, you can now create a Pivot Grid by right-clicking on a measure, saving a few clicks, when you just need to test the value of a measure.
  • We now show an error message, if attempting to assign an expression that produces a value of type 'Variant' to a calculated column (this is not allowed).
  • We've added a separate option for saving zipped model.bim backups under Tools > Preferences > Model Deployment. You can now choose to have backups saved upon every deployment, upon every save (while connected to an instance of Analysis Services), or both. Note, this feature is not available for TE3 Desktop Edition. This also fixed issue #796.
  • We've added additional info columns to VertiPaq Analyzer, to align with those available in DAX Studio.

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.

Bugfixes in 3.9.0

  • Fix false "Circular dependency" errors, encountered both in the DAX Editor, as well as in the TOM Explorer / Messages View. See issues #920 and #931.
  • Fixed an issue that prevented the Search and Replace dialog from searching in floating (undocked) document windows.
  • Various stability improvements (should fix #937, among other things).
  • Fixed a crash that would occur when attempting to format DAX code containing window functions.
  • Fixed a bug that caused Tabular Editor to use the System proxy when choosing Proxy Type "None" under Tools > Preferences > Proxy settings, and vice versa.
  • Semantic Analyzer now works correctly with the DETAILROWS function, see #938.
  • Fixed an issue where changing the name of a macro would not update the folder structure of macros, until the application was restarted.
  • Fixed a bug that caused certain column and hierarchy properties to be read-only, preventing users from correctly setting up calculated tables, relationships, etc., while connected to Power BI Desktop. See #929 and #930.
  • Fixed a crash in the DAX editor, when using the WINDOW function with certain parameters.
  • Fixed an issue with the M parser not interpreting [] correctly, preventing the offline schema comparer from inferring metadata from an M expression such as PowerPlatform.Dataflows([]). See #936.
  • Fixed an issue where the PivotGrid would crash if a measure had a malformed format string assigned.
  • Fixed an issue where the Semantic Analyzer would assign "Variant" as the data type of an expression resulting from the use of SWITCH with one or more branches returning BLANK.
  • Fixed a few bugs related to column filters on table previews. When getting the list of unique values of a column, we now read the first 5000 values (in ascending order). Previously, only 500 values were read, with no ordering specified, causing inconsistent behavior. See #924.

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

Assets 2
Loading

Tabular Editor 3.8.0

26 Jun 10:00
@otykier otykier
3.8.0
68da71e
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Tabular Editor 3.8.0

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.

Improvements in 3.8.0

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

  • Tabular Editor 3 now lets you open Power BI Desktop project (.pbip) files or folders containing .pbip files. When such a folder contains multiple datasets, a list is shown, letting you select which one to open.
  • The June 2023 update of Power BI Desktop now supports a much larger range of modelling operations that can be performed through external tools ("hardening"). In other words, when you connect Tabular Editor to Power BI Desktop (June 2023 or newer), you will now be able to add/edit calculated columns, calculated tables, relationships, hierarchies, and much more.
  • We're now using the latest version of TOM/AMO (19.65.4).

Note: TMDL and Power BI Desktop Projects (.pbip) is still in preview, and as such, these features must also be considered preview features of Tabular Editor 3. Make sure to keep a Model.bim / Database.json backup of your model metadata to avoid losing work.

Bugfixes in 3.8.0

  • Dependency view now has much better performance for models with large and complex dependency graphs.
  • Some users have reported that editing certain properties, through the Properties view, caused the application to crash. This should no longer be the case.
  • Semantic Analyzer should no longer report errors when a DAX query contains both query-scoped columns and query-scoped tables.
  • Semantic Analyzer now correctly handles DAX expressions containing UTF-32 characters (emojis), although the DAX editor still has issues dealing with these. In general, we recommend avoiding the use of emojis in DAX expressions.
  • Fixed a bug where repeatedly hitting Ctrl+Z (Undo) would clear the Expression Editor and even bring in unrelated expressions.
  • Perspective Editor now correctly updates to reflect when new objects are added/removed to/from the model.
  • VertiPaq Analyzer should no longer crash when a model contains Dynamic Format Strings.
  • Fixed a regression with importing tables from Snowflake, which caused columns to have incorrect datatypes assigned.
  • Fixed a regression with update schema/importing tables Snowflake, where the implicit data source properties had to be re-entered in the connection dialog.
  • Fixed an issue where the toolbar buttons related to the Expression Editor would disappear, if the Expression Editor was docked as a tool window (i.e. not as a document window).
  • DAX editors now perform a new semantic analysis, when changes that can impact DAX semantics are made to the model. This should ensure that the error messages shown in the DAX editor are always valid.
  • Fixed an issue where the DAX debugger would be unavailable, even for seemingly simple DAX queries.

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

Assets 2
Loading

Tabular Editor 3.7.1

22 May 07:23
@otykier otykier
3.7.1
68da71e
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Tabular Editor 3.7.1

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.

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

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

Assets 2
Loading

Tabular Editor 3.6.0

19 Apr 13:35
@otykier otykier
3.6.0
68da71e
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Tabular Editor 3.6.0

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

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

  • Tabular Editor 3 now has native support for Databricks. This means you can now connect to a Databricks SQL endpoint when importing tables using the Table Import Wizard. For more information, see our release blog post.
  • We added support for the new DAX functions RANK and ROWNUMBER introduced in the April 2023 update of Power BI Desktop. In addition, our code complete now shows all available keywords for the <Blanks> and <Order> arguments of the window and ORDERBY functions.

Minor improvements in 3.6.0

  • We no longer perform a (potentiallys slow) conflict check before saving changes to the workspace database. The assumption is that each developer uses their own personal workspace database, so conflicts should not occur.
  • C# scripting: The IAnnotationObject interface has been extended with a ClearAnnotations() method.
  • When adding a dynamic format string expression to a measure, we now clear the static format string property (as it is not possible for measures to have both static and dynamic format strings assigned).
  • Updated TOM to 19.61.1.4.
  • Default Compatibility Level for new Power BI models created with Tabular Editor, is now 1601. Moreover, the "create new model" dialog now lets you specify any compatibility level.

Bugfixes in 3.6.0

  • Oracle download instructions updated to instruct users to use the ODAC (not ODP.NET) drivers.
  • Removed restrictions on special characters in database names, when opening or creating a new database.
  • Fixed an issue that caused the database name property within the .bim / database.json file, to be updated with the name of the workspace database.
  • DAX debugger stability improvements.
  • .tmuo files are no longer saved, when the "Create user options (.tmuo) file" option is unchecked.
  • Fixed an issue where code complete would sometimes "absorb" closing brackets.
  • Semantic Analyzer no longer reports an error when using SELECTEDMEASURE (and related functions) in the context of measure expressions and format string expressions.
  • Fixed an issue where the M query generated for new tables imported from an existing implicit (SQL) data source, would not work correctly when attempting to refresh the table.
Assets 2
Loading

Tabular Editor 3.5.1

28 Mar 23:03
@otykier otykier
3.5.1
c1a9448
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Tabular Editor 3.5.1

*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 and improvements in 3.5.1

  • Updated TOM to 19.60.0.
  • Fixed an issue with the Edit Relationship dialog showing an incompatible data type warning, even if the data types on both columns are identical, see #855. Moreover, when connected to an instance of Analysis Services, the dialog now displays RI violation and duplicate value warnings.
  • Fixed an issue that would sometimes cause the application to freeze when opening a file or folder structure from disk.
  • Fixed an issue that prevented editing RLS expressions when a role contained a "." in its name.
  • When an object is shown in multiple display folders, the TOM Explorer didn't correctly refresh its properties in all places. This has been fixed.
  • "Model" is now treated as a reserved word in the Semantic Analyzer, see #852.
  • The .pbitool file (used for External Tool integration with PBI Desktop) now uses the updated TE3 icon.
  • The Create Workspace Database dialog now validates the database name, preventing special characters that are not supported by Analysis Services.
  • Fixed an issue with auto-indent overwriting characters in the DAX editor. See #857.
  • You can now create add tables/calculation groups directly to a table group through the table group's right-click context menu.
  • Fixed an regression in 3.5.0, where importing columns or performing a schema update on a table from an MS SQL-flavored data source, would result in the wrong data type being assigned to the column.
  • Fixed an issue where closing a bracket or parenthesis would sometimes "snap" the cursor to the wrong position in the DAX editor.

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

Assets 2
Loading

Tabular Editor 3.5.0

15 Mar 23:52
@otykier otykier
3.5.0
f931cab
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Tabular Editor 3.5.0

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.

Improvements in 3.5.0

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

  • Updated TOM to 19.57.2.4.
  • This release introduces Table Groups which lets you organise tables into "folders" in the TOM Explorer. Learn more.
  • Default shortcut for uncommenting code now set to Ctrl+U
  • Tabular Editor will now attempt to automatically reconnect to Analysis Services, when the session timeout has expired. This means it should no longer be necessary to close and reopen table previews, DAX query windows and Pivot Grids. See #650, #803.
  • Added a new set of overloaded C# script methods Macro(...). These are an alias for CustomAction(...). The API documentation has been updated accordingly.
  • When using Tabular Editor in Workspace Mode, incremental refresh partitions are not overridden upon workspace database updates. Moreover, a new serialization option Ignore incremental refresh partitions is now available, and enabled by default for new models. This option will make sure that partitions governed by incremental refresh, are not serialized when saving a model as a .bim or folder structure. This makes it easier to integrate models using incremental refresh with version control.
  • Added toolbar button to toggle display folders in the Perspective Editor view. Toggling a Display Folder in the Perspective Editor, will toggle all objects within that folder. The Perspective Editor now also provides a visual indication if a table or folder contains both items that are included in the perspective, and items that are not.
  • Tabular Editor now has full support for Oracle data sources. You must have the ODP.NET managed drivers installed, which is also a requirement if you want to import data from Oracle in Power BI Desktop.

Bugfixes in 3.5.0

  • Auto-format should no longer erase code when the DAX Editor is configured to use tabs
  • "Open macro" button in the Macros view will now be enabled whenever a macro is selected
  • It should no longer be necessary to reset the window layout, in order for the Perspective Editor view to appear
  • Main Menu bar will no longer reset when a macro is added as a new button
  • Fixed a bug that sometimes prevented Tabular Editor from opening a .bim file or .json folder structure containing Power BI specific TOM properties.
  • ResolveObjectPath now supports the "old" path format, similar to TE2. See #1077.
  • BPA rules that rely on the Expression property on tables, should no longer fail.
  • Macros can now be saved/compiled even if their name contains a double quote.
  • Fixed various issues with the CustomAction(...) C# script method.
  • Perspective Editor now correctly deals with hidden tables containing visible measures.
  • Fixed an issue that prevented setting the Default Measure property on the Model object through the Properties View.
  • Calculate Table context menu option will no longer show when working offline.
  • Fixed an issue that caused the C# autocomplete dropdown to "absorb" a period key press.
  • Fixed an issue with the semantic analyzer reporting incorrect parameter usage to the DAX XIRR function.
  • Relationship Editor now allows creating relationships between columns of different, but compatible, data types.
  • Fixed the "The key didn't match any rows" error, when attempting to perform a schema update on a table using an M Partition.
  • Tables using incremental refresh policy now work with the Update Table Schema feature.

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

Assets 2
Loading