Skip to content

Releases: TabularEditor/TabularEditor

Tabular Editor 2.27.2

29 Sep 11:50
@otykier otykier
2.27.2
9b25883

Choose a tag to compare

View all tags
Tabular Editor 2.27.2 Latest
Latest

Warning

There are breaking changes in Tabular Editor 2.27.0 regarding deployment of models through the Tabular Editor CLI. By default, Shared Expressions are now no longer deployed, unless the -S / -SHARED switch is specified.

Bugfixes in 2.27.2

  • DAX formatting for UDFs should now work correctly, see #1303
  • Fixed a regression with the CLI -S (script) switch, which no longer did anything in 2.27.0 and 2.27.1.
  • TMDL input box now takes an unlimited amount of characters (instead of cutting off at 32K)

Bugfixes and improvements in 2.27.1

  • The MSAL.NET client library was updated to 4.72.1, which is the latest library that's not deprecated but also known to "play nicely" with the AS client library for connecting to the XMLA endpoints of Power BI / Azure Analysis Services.
  • Fixed a bug where the "msalruntime" DLLs were not properly included in the .zip / .msi versions of Tabular Editor 2. In newer versions of the MSAL.NET client library, these DLLs are required. Before this fix, users who did not have the DLLs preregistered in their machines GAC would face issues while attempting to connect, as discussed in #1269, #1290, #1297. The inclusion of these DLLs in the .zip / .msi files for Tabular Editor explains why the size of these files have also gone up substantially.
  • A "Fix Expression Editor" tab has been added to the Edit Best Practice Rule dialog, so you no longer need to edit the BpaRules.json file to a specify a FixExpression. Thanks to @mlonsk for this contribution!

New in 2.27.0

  • Tabular Editor now supports DAX UDFs, including the following features:
    • Batch rename
    • Automatic formula fixup both for function names, and for object references inside the function body
    • Functions appear in the Show dependencies dialog
  • Tabular Editor now also supports Calendars, including the following features:
    • Automatic formula fixup for calendar names
    • Calendars appear in the Show dependencies dialog
  • There is a new Import TMDL... option in the Model menu, which is useful when you want to bring in objects from a TMDL script, such as packages of UDFs from https://daxlib.org.

Improvements in 2.27.0

  • Updated AMO/TOM to 19.104.1
  • Added a new authentication option, "Microsoft Entra MFA", which will force the account selector pop-up. This is useful in case you want to use a different account to connect to Power BI / Azure Analysis Services, than the one connected as your Work & School Account in Windows.
  • The Schema Name property is now shown and can be edited on EntityPartition objects. Thanks @rubenhillstar
  • Support for BindingInfo, QueryGroups and better validation when copying/pasting objects, in order to avoid subsequent "invalid object reference" errors, when subsequently saving the changes to Analysis Services.
  • Added a new UI and CLI deployment option, -S / -SHARED, to indicate that Shared Expressions should be deployed. Omitting this switch during a deployment (-D / -DEPLOY) operation will cause the Shared Expressions to be left as is. See also #1258.
  • As the number of CLI switches you had to add to perform a full overwrite deployment has become a bit unwieldy, we've added a new -F / -FULL switch. In other words, the following commands are now equivalent:
tabulareditor.exe "c:\path\to\database.tmdl" -D "localhost" "model" -O -C -P -S -R -M
tabulareditor.exe "c:\path\to\database.tmdl" -D "localhost" "model" -F

Bugfixes in 2.27.0

Other news

The TOMWrapper library including the namespaces and classes needed to run the Best Practice Analyzer is now available as a standalone solution/project which targets both .NET Framework and .NET 6 / .NET 8. Huge thanks to @mthierba for his contributions to this! If there is a demand, we will look into packaging this library on NuGet.

Contributors

mthierba, mlonsk, and rubenhillstar
Assets 4
Loading

Tabular Editor 2.27.1

25 Sep 11:08
@otykier otykier
2.27.1
07e1d44

Choose a tag to compare

View all tags
Tabular Editor 2.27.1

Warning

There are breaking changes in Tabular Editor 2.27.0 regarding deployment of models through the Tabular Editor CLI. By default, Shared Expressions are now no longer deployed, unless the -S / -SHARED switch is specified.

Bugfixes and improvements in 2.27.1

  • The MSAL.NET client library was updated to 4.72.1, which is the latest library that's not deprecated but also known to "play nicely" with the AS client library for connecting to the XMLA endpoints of Power BI / Azure Analysis Services.
  • Fixed a bug where the "msalruntime" DLLs were not properly included in the .zip / .msi versions of Tabular Editor 2. In newer versions of the MSAL.NET client library, these DLLs are required. Before this fix, users who did not have the DLLs preregistered in their machines GAC would face issues while attempting to connect, as discussed in #1269, #1290, #1297. The inclusion of these DLLs in the .zip / .msi files for Tabular Editor explains why the size of these files have also gone up substantially.
  • A "Fix Expression Editor" tab has been added to the Edit Best Practice Rule dialog, so you no longer need to edit the BpaRules.json file to a specify a FixExpression. Thanks to @mlonsk for this contribution!

New in 2.27.0

  • Tabular Editor now supports DAX UDFs, including the following features:
    • Batch rename
    • Automatic formula fixup both for function names, and for object references inside the function body
    • Functions appear in the Show dependencies dialog
  • Tabular Editor now also supports Calendars, including the following features:
    • Automatic formula fixup for calendar names
    • Calendars appear in the Show dependencies dialog
  • There is a new Import TMDL... option in the Model menu, which is useful when you want to bring in objects from a TMDL script, such as packages of UDFs from https://daxlib.org.

Improvements in 2.27.0

  • Updated AMO/TOM to 19.104.1
  • Added a new authentication option, "Microsoft Entra MFA", which will force the account selector pop-up. This is useful in case you want to use a different account to connect to Power BI / Azure Analysis Services, than the one connected as your Work & School Account in Windows.
  • The Schema Name property is now shown and can be edited on EntityPartition objects. Thanks @rubenhillstar
  • Support for BindingInfo, QueryGroups and better validation when copying/pasting objects, in order to avoid subsequent "invalid object reference" errors, when subsequently saving the changes to Analysis Services.
  • Added a new UI and CLI deployment option, -S / -SHARED, to indicate that Shared Expressions should be deployed. Omitting this switch during a deployment (-D / -DEPLOY) operation will cause the Shared Expressions to be left as is. See also #1258.
  • As the number of CLI switches you had to add to perform a full overwrite deployment has become a bit unwieldy, we've added a new -F / -FULL switch. In other words, the following commands are now equivalent:
tabulareditor.exe "c:\path\to\database.tmdl" -D "localhost" "model" -O -C -P -S -R -M
tabulareditor.exe "c:\path\to\database.tmdl" -D "localhost" "model" -F

Bugfixes in 2.27.0

Other news

The TOMWrapper library including the namespaces and classes needed to run the Best Practice Analyzer is now available as a standalone solution/project which targets both .NET Framework and .NET 6 / .NET 8. Huge thanks to @mthierba for his contributions to this! If there is a demand, we will look into packaging this library on NuGet.

Contributors

mthierba, mlonsk, and rubenhillstar
Loading

Tabular Editor 2.27.0

24 Sep 13:15
@otykier otykier
2.27.0
82e71bd

Choose a tag to compare

View all tags
Tabular Editor 2.27.0

Warning

There are breaking changes in this release regarding deployment of models through the Tabular Editor CLI. By default, Shared Expressions are now no longer deployed, unless the -S / -SHARED switch is specified.

New in 2.27.0

  • Tabular Editor now supports DAX UDFs, including the following features:
    • Batch rename
    • Automatic formula fixup both for function names, and for object references inside the function body
    • Functions appear in the Show dependencies dialog
  • Tabular Editor now also supports Calendars, including the following features:
    • Automatic formula fixup for calendar names
    • Calendars appear in the Show dependencies dialog
  • There is a new Import TMDL... option in the Model menu, which is useful when you want to bring in objects from a TMDL script, such as packages of UDFs from https://daxlib.org.

Improvements in 2.27.0

  • Updated AMO/TOM to 19.104.1
  • Added a new authentication option, "Microsoft Entra MFA", which will force the account selector pop-up. This is useful in case you want to use a different account to connect to Power BI / Azure Analysis Services, than the one connected as your Work & School Account in Windows.
  • The Schema Name property is now shown and can be edited on EntityPartition objects. Thanks @rubenhillstar
  • Support for BindingInfo, QueryGroups and better validation when copying/pasting objects, in order to avoid subsequent "invalid object reference" errors, when subsequently saving the changes to Analysis Services.
  • Added a new UI and CLI deployment option, -S / -SHARED, to indicate that Shared Expressions should be deployed. Omitting this switch during a deployment (-D / -DEPLOY) operation will cause the Shared Expressions to be left as is. See also #1258.
  • As the number of CLI switches you had to add to perform a full overwrite deployment has become a bit unwieldy, we've added a new -F / -FULL switch. In other words, the following commands are now equivalent:
tabulareditor.exe "c:\path\to\database.tmdl" -D "localhost" "model" -O -C -P -S -R -M
tabulareditor.exe "c:\path\to\database.tmdl" -D "localhost" "model" -F

Bugfixes in 2.27.0

Other news

The TOMWrapper library including the namespaces and classes needed to run the Best Practice Analyzer is now available as a standalone solution/project which targets both .NET Framework and .NET 6 / .NET 8. Huge thanks to @mthierba for his contributions to this! If there is a demand, we will look into packaging this library on NuGet.

Contributors

mthierba and rubenhillstar
Loading

Tabular Editor 2.26.0

28 Mar 23:24
@otykier otykier
2.26.0
ae777e4

Choose a tag to compare

View all tags
Tabular Editor 2.26.0

Improvements in 2.26.0

  • Updated AMO/TOM to 19.90.0. This update includes the latest AS engine features including the GA version of TMDL. There are also changes to how authentication is performed, which should solve issues such as #1256. Moreover, the library will now use the currently signed in Entra ID account when connecting.
    • Note: If you need the MFA account selector popup when connecting to the XMLA endpoint of Azure AS / Power BI, you can force it open by entering a single blank character as the username (leave password blank).
  • When adding an RLS expression to a table, we now set the Model permission to Read in alignment with TE3. See #1236.
  • 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 source comments for more details.

Bugfixes in 2.26.0

  • When deploying a model excluding partitions, or including partitions except those that are governed by incremental refresh policies, Tabular Editor will no longer deploy the properties related to the refresh policy (SourceExpression, RollingWindowGranularity, etc.) on the table object.

Other news

The TOMWrapper library including the namespaces and classes needed to run the Best Practice Analyzer is now available as a standalone solution/project which targets both .NET Framework and .NET 6 / .NET 8. Huge thanks to @mthierba for his contributions to this! If there is a demand, we will look into packaging this library on NuGet.

Contributors

mthierba
Loading

2.25

05 Jul 11:02
@otykier otykier
2.25
59a889d

Choose a tag to compare

View all tags
2.25

Improvements in 2.25.0

  • Updated AMO/TOM to 19.84.1 which contains improvements to the TMDL serializer.
  • The CLI no longer outputs the server name/connection string, see #1209
  • Improved display of method signatures in the C# script autocomplete popup, see #1197

Important

TMDL is still a preview feature, meaning breaking changes could be introduced between new releases. If you face any issues deserializing a model after upgrading Tabular Editor, rollback to the latest version of Tabular Editor, then temporarily save the model as a regular .bim file, before serializing it to TMDL again using the latest version of Tabular Editor.

Bugfixes in 2.25.0

  • The "Open model from file" dialog should now also show database.tmdl files, see #1200
  • TMDL models are now also shown in "Recent files", see #1199
Loading

Tabular Editor 2.24.1

22 Apr 10:39
@otykier otykier
2.24.1
1b28ebe

Choose a tag to compare

View all tags
Tabular Editor 2.24.1

Improvements in 2.24.1

Important

TMDL is still a preview feature, meaning breaking changes could be introduced between new releases. If you face any issues deserializing a model after upgrading Tabular Editor, rollback to the latest version of Tabular Editor, then temporarily save the model as a regular .bim file, before serializing it to TMDL again using the latest version of Tabular Editor.

Improvements in 2.24.0

  • Updated AMO/TOM to 19.77.0.
  • Tabular Editor will now add a __TEdtr annotation to your model when metadata is saved to disk (either as Model.bim, Database.json or TMDL). This annotation is used by Microsoft to track usage of Tabular Editor and may be required for certain features to work correctly in Power BI / Fabric.
  • When new tables are added to a Direct Lake model, and the model is subsequently saved, or when a Direct Lake model is deployed, Tabular Editor now executes a refresh of the model. This is needed in order for the tables to be initially "reframed", otherwise, all DAX queries hitting the tables would fall back to DirectQuery mode.
  • We now use Compatibility Level 1605 as the default for new Power BI / Fabric models.

Bugfixes in 2.24.0

  • Saving a TMDL model using the -D switch of the CLI should no longer give an "access denied" error, see #1188
Loading

Tabular Editor 2.24.0

09 Apr 13:37
@otykier otykier
2.24.0
35b89a0

Choose a tag to compare

View all tags
Tabular Editor 2.24.0

Improvements in 2.24.0

  • Updated AMO/TOM to 19.77.0.
  • Tabular Editor will now add a __TEdtr annotation to your model when metadata is saved to disk (either as Model.bim, Database.json or TMDL). This annotation is used by Microsoft to track usage of Tabular Editor and may be required for certain features to work correctly in Power BI / Fabric.
  • When new tables are added to a Direct Lake model, and the model is subsequently saved, or when a Direct Lake model is deployed, Tabular Editor now executes a refresh of the model. This is needed in order for the tables to be initially "reframed", otherwise, all DAX queries hitting the tables would fall back to DirectQuery mode.
  • We now use Compatibility Level 1605 as the default for new Power BI / Fabric models.

Bugfixes in 2.24.0

  • Saving a TMDL model using the -D switch of the CLI should no longer give an "access denied" error, see #1188

Important

TMDL is still a preview feature, meaning breaking changes could be introduced between new releases. If you face any issues deserializing a model after upgrading Tabular Editor, rollback to the latest version of Tabular Editor, then temporarily save the model as a regular .bim file, before serializing it to TMDL again using the latest version of Tabular Editor.

Loading

Tabular Editor 2.23.1

12 Mar 22:07
@otykier otykier
2.23.1
ef84269

Choose a tag to compare

View all tags
Tabular Editor 2.23.1

Bugfixes in 2.23.1

  • Fixed an issue that would sometimes cause an error when opening a model with a DataCoverageDefinition, see #1186.

Improvements in 2.23.0

  • We now support the Data Coverage Definition property on DirectQuery partitions (when the model is at Compatibility Level 1603 or higher).
  • TMDL now uses the same default serialization as Power BI Desktop, so you should see fewer diffs the first time you save a model with Tabular Editor, that was originally created in Power BI Desktop and saved as PBIP.
  • The Current Model serialization options tab is now visible under File > Preferences even when a model hasn't previously been saved in Tabular Editor.

Important

TMDL is still a preview feature, meaning breaking changes could be introduced between new releases. If you face any issues deserializing a model after upgrading Tabular Editor, rollback to the latest version of Tabular Editor, then temporarily save the model as a regular .bim file, before serializing it to TMDL again using the latest version of Tabular Editor.

Note

We do not currently have any options available for customizing which objects get serialized as individual files, when using TMDL. If you would like to see this feature, please let us know!

Bugfixes in 2.23.0

  • Fix for #1173
  • Fix for #1178
  • Fix for #1182
  • When using the (default) UTF8 encoding for TMDL, we now save the files without the BOM (byte-order-mark), in alignment with Power BI Desktop.
Loading

Tabular Editor 2.23.0

27 Feb 12:21
@otykier otykier
2.23.0
ef9b841

Choose a tag to compare

View all tags
Tabular Editor 2.23.0

Improvements in 2.23.0

  • We now support the Data Coverage Definition property on DirectQuery partitions (when the model is at Compatibility Level 1603 or higher).
  • TMDL now uses the same default serialization as Power BI Desktop, so you should see fewer diffs the first time you save a model with Tabular Editor, that was originally created in Power BI Desktop and saved as PBIP.
  • The Current Model serialization options tab is now visible under File > Preferences even when a model hasn't previously been saved in Tabular Editor.

Important

TMDL is still a preview feature, meaning breaking changes could be introduced between new releases. If you face any issues deserializing a model after upgrading Tabular Editor, rollback to the latest version of Tabular Editor, then temporarily save the model as a regular .bim file, before serializing it to TMDL again using the latest version of Tabular Editor.

Note

We do not currently have any options available for customizing which objects get serialized as individual files, when using TMDL. If you would like to see this feature, please let us know!

Bugfixes in 2.23.0

  • Fix for #1173
  • Fix for #1178
  • Fix for #1182
  • When using the (default) UTF8 encoding for TMDL, we now save the files without the BOM (byte-order-mark), in alignment with Power BI Desktop.
Loading

Tabular Editor 2.22.1

08 Feb 09:34
@otykier otykier
2.22.1
ce7a093

Choose a tag to compare

View all tags
Tabular Editor 2.22.1

Bugfixes in 2.22.1

  • Fixed an issue that caused on-premises models saved to TMDL to get deserialized with an "Unknown" Compatibility Mode, in turn causing crashes when making subsequent changes to the model, see #1176.
  • Updated AMO/TOM to 19.76.0.

New in 2.22.0

Important

TMDL is still a preview feature, meaning breaking changes could be introduced between new releases. If you face any issues deserializing a model after upgrading Tabular Editor, rollback to the latest version of Tabular Editor, then temporarily save the model as a regular .bim file, before serializing it to TMDL again using the latest version of Tabular Editor.

  • With TMDL preview-9, we now have a set of new options available, for configuring how the TMDL is serialized. You can find these options under File > Preferences > Serialization (for any models that were previously saved as TMDL, you can change these settings under File > Preferences > Current Model):

image

Note

We do not currently have any options available for customizing which objects get serialized as individual files, when using TMDL. If you would like to see this feature, please let us know!

Bugfixes in 2.22.0

  • Extended Properties on Perspectives are now correctly saved when using the (legacy) save-to-folder feature, see #1165
Loading