Tabular Editor 2.24.1

• Windows installer: TabularEditor.2.24.1.Installer.msi
  • SHA256: 56026AE6EEF74747562423C8120A99B7AB5ED066AA9BA59B17627ACD0069ECC7
• Portable version: TabularEditor.2.24.1.zip
  • SHA256: 6A69897803986E74FD956346B585AAA1CE5FBE62C2BF5409882F9F5D178DE074

Improvements in 2.24.1

• Updated AMO/TOM to 19.79.1 which also includes an improved TMDL serializer.

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

Tabular Editor 2.24.0

• Windows installer: TabularEditor.2.24.0.Installer.msi
  • SHA256: 118CBE6F4061C6C6B61DF761AB03B873737264EFEF13AE332D52C46887FBA716
• Portable version: TabularEditor.2.24.0.zip
  • SHA256: 48D91A1BEAF79E85F8AAB3983769B4472CF1E019103E3FF184AA4A1EC7EECD32

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.

Tabular Editor 2.23.1

• Windows installer: TabularEditor.2.23.1.Installer.msi
  • SHA256: EB892BD0F05EE749E16D69D8007D170207DBCCBBF40C61D6C60982E4D845E350
• Portable version: TabularEditor.2.23.1.zip
  • SHA256: AD905B9346CEAC22446BEC868B78D102694A92B58E0E1DA0452924D57709F4A7

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.

Tabular Editor 2.23.0

• Windows installer: TabularEditor.2.23.0.Installer.msi
  • SHA256: B74B30FA6F5731E2D53ADF4B99FFDC665BC60D95C9A4151A514EBEFEB7B4FF9E
• Portable version: TabularEditor.2.23.0.zip
  • SHA256: F2C8D1B6963E4A4DA91F9E24536A014747157C65785990083B17790566E946CD

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.

Tabular Editor 2.22.1

• Windows installer: TabularEditor.2.22.1.Installer.msi
  • SHA256: FEB74166B24B2F1F9D0A294366A3ABFBBA4A5DE372C2EBD437ADC64ED6094ECA
• Portable version: TabularEditor.2.22.1.zip
  • SHA256: 0B3F4485F8E0CAFCEF41DC5EF6E364028F4C560CE71A82FF2EA9244DA426056E

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

• Updated AMO/TOM to 19.74.2. This adds support for the latest TOM modelling features, for example the Model.DataSourceVariablesOverrideBehavior and the Model.ValueFilterBehavior properties. This version of AMO/TOM also includes TMDL preview-9.

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):

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

Tabular Editor 2.22.0

• Windows installer: TabularEditor.2.22.0.Installer.msi
  • SHA256: BBA2B06FD95F3CC16AFDF0625D9EF6C1986D825B5AEB7DB946EAF7CCCD373273
• Portable version: TabularEditor.2.22.0.zip
  • SHA256: 00F41216C82FDAE7F9514C1709CDE5EB5C1B6D87C85E7CE097E63C838446B17F

New in 2.22.0

• Updated AMO/TOM to 19.74.2. This adds support for the latest TOM modelling features, for example the Model.DataSourceVariablesOverrideBehavior and the Model.ValueFilterBehavior properties. This version of AMO/TOM also includes TMDL preview-9.

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):

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

Tabular Editor 2.21.1

• Windows installer: TabularEditor.2.21.1.Installer.msi
  • SHA256: 4F4052DA4D60251E0C18B75C03191B0A0B3CCA950811647A69FBF9AC739B97BC
• Portable version: TabularEditor.2.21.1.zip
  • SHA256: 28672953474A634497CA058AAB0B15BDC8DEED1E6FA7486EB98EACE44B68025D

Bugfixes in 2.21.1

• Fixed a regression introduced in 2.21.0, where clipboard "Paste" operations would not always work, see #1154.

Improvements in 2.21.0

• Updated AMO/TOM to 19.69.6.2. This adds support for the latest TOM modelling features. For example:
  • For DirectLake models, we now support the DirectLakeBehavior property, which specifies whether the model should automatically fallback to DirectQuery mode (default), or be restricted to only DirectLake mode, or only DirectQuery mode.
  • Support for Calculation Group Selection Expressions (the model needs to be at Compatibility Level 1605 for these properties to be available).
• Updated TMDL to the latest preview version.
  Note: TMDL is a preview feature. Things are still subject to change.
• When the Timeout property of a Provider (legacy) Data Source has been specified (i.e. a nonzero value), Tabular Editor will now use the value for the CommandTimeout property when performing table imports/schema updates, see #1115 (thanks @rbulka)
• The C# .Tokenize() method (used to retrieve a list of DAX tokens for objects that contain DAX expressions, such as measures, calculation items, etc.), now take an optional bool includeHidden argument. By default, this is true. Set this flag to false if you do not want whitespace and comment tokens in the output. This method should be used in dynamic LINQ expressions, if you want to create BPA rules that check for the presence of certain DAX keywords or syntax. It is more robust than e.g. Regex. See examples here.

Bugfixes in 2.21.0

• When deploying a model, always add a dummy partition to an incremental refresh table, if the metadata does not define any partitions. Otherwise, the generated TMSL deployment script would be invalid.
• Fixed a bug that could cause a NullReferenceException when deleting objects through a C# script, see #1139
• The data source name is now (again) shown under the source info-column for tables that use Provider Data Sources, see #1136
• Fixed an issue that prevented loading a model from a Power BI workspace with special characters in the name, see #1133
• Fixed a bug where the Best Practice Analyzer would report the wrong number of objects having a violation within each rule.

Tabular Editor 2.21.0

Important

Update, Nov. 14th, 2023:
There is a newer version available, which fixes an issue related to using the clipboard in the version below.

---

• Windows installer: TabularEditor.2.21.0.Installer.msi
  • SHA256: 0E79FF597F401E8943583FCE633ABD196BD1A3BFA423B2DB537ED93010458A8E
• Portable version: TabularEditor.2.21.0.zip
  • SHA256: EE018E3FCB82D87F1D8787807713026D903A28A78792489FDF8D5C03EA185650

Improvements in 2.21.0

• Updated AMO/TOM to 19.69.6.2. This adds support for the latest TOM modelling features. For example:

  • For DirectLake models, we now support the DirectLakeBehavior property, which specifies whether the model should automatically fallback to DirectQuery mode (default), or be restricted to only DirectLake mode, or only DirectQuery mode.

  • Support for Calculation Group Selection Expressions (the model needs to be at Compatibility Level 1605 for these properties to be available).

• Updated TMDL to the latest preview version.
  Note: TMDL is a preview feature. Things are still subject to change.
• When the Timeout property of a Provider (legacy) Data Source has been specified (i.e. a nonzero value), Tabular Editor will now use the value for the CommandTimeout property when performing table imports/schema updates, see #1115 (thanks @rbulka)
• The C# .Tokenize() method (used to retrieve a list of DAX tokens for objects that contain DAX expressions, such as measures, calculation items, etc.), now take an optional bool includeHidden argument. By default, this is true. Set this flag to false if you do not want whitespace and comment tokens in the output. This method should be used in dynamic LINQ expressions, if you want to create BPA rules that check for the presence of certain DAX keywords or syntax. It is more robust than e.g. Regex. See examples here.

Bugfixes in 2.21.0

• When deploying a model, always add a dummy partition to an incremental refresh table, if the metadata does not define any partitions. Otherwise, the generated TMSL deployment script would be invalid.
• Fixed a bug that could cause a NullReferenceException when deleting objects through a C# script, see #1139
• The data source name is now (again) shown under the source info-column for tables that use Provider Data Sources, see #1136
• Fixed an issue that prevented loading a model from a Power BI workspace with special characters in the name, see #1133
• Fixed a bug where the Best Practice Analyzer would report the wrong number of objects having a violation within each rule.

Tabular Editor 2.20.2

• Windows installer: TabularEditor.2.20.2.Installer.msi
  • SHA256: 013919C91CAE3CD8A0B32116651CA4D26B7B9B3F50E918076C127BBF3F5B01CA
• Portable version: TabularEditor.2.20.2.zip
  • SHA256: 8D84FD738B9BC52897EBDC426A8BC90ECA5FE88FBD577ED740FA68A9B648C30C

Bugfixes in 2.20.2

• Fixed an issue where Tabular Editor was not able to open a model that had been saved to TMDL format (see #1132).

Bugfixes in 2.20.1

• Fixed an issue where Tabular Editor would generate invalid TMSL deployment script in some cases, when performing a deployment on a model containing tables governed by incremental refresh policy.

Improvements in 2.20.0

• Updated AMO/TOM to 19.67.0, which benefits from the recently announced binary XML format.
• Updated TMDL to Preview-3, which fixes a number of issues when serializing/deserializing to this format, and also changes file extensions from .tmd to .tmdl. Note: TMDL is a preview feature. Things are still subject to change.
• Tabular Editor 2 now has an option to remove partitions governed by incremental refresh, before serializing to disk (as Model.bim or Database.json). This is useful to avoid version control conflicts, when partition policy ranges change over time. You can control this setting under File > Preferences... > Serialization or File > Preferences... > Current Model.

Bugfixes in 2.20.0

• Fixed a bug that prevented opening and deploying a model containing incremental refresh tables with no partitions. This applies both to the UI and the CLI.
• Add support for LF as EOL char in CSX scripts (thanks @albertospelta)

Tabular Editor 2.20.1

• Windows installer: TabularEditor.2.20.1.Installer.msi
  • SHA256: 3BF71EDDAA76B2271AC88A3E821F624DF052084FB17BEB97445F78919B6E624D
• Portable version: TabularEditor.2.20.1.zip
  • SHA256: 8B2B9BAE553E4C448F1D37E1BAB4F2E8E61B882E658E220539C3660F1E74A687

Bugfixes in 2.20.1

• Fixed an issue where Tabular Editor would generate invalid TMSL deployment script in some cases, when performing a deployment on a model containing tables governed by incremental refresh policy.

Improvements in 2.20.0

• Updated AMO/TOM to 19.67.0, which benefits from the recently announced binary XML format.
• Updated TMDL to Preview-3, which fixes a number of issues when serializing/deserializing to this format, and also changes file extensions from .tmd to .tmdl. Note: TMDL is a preview feature. Things are still subject to change.
• Tabular Editor 2 now has an option to remove partitions governed by incremental refresh, before serializing to disk (as Model.bim or Database.json). This is useful to avoid version control conflicts, when partition policy ranges change over time. You can control this setting under File > Preferences... > Serialization or File > Preferences... > Current Model.

Bugfixes in 2.20.0

• Fixed a bug that prevented opening and deploying a model containing incremental refresh tables with no partitions. This applies both to the UI and the CLI.
• Add support for LF as EOL char in CSX scripts (thanks @albertospelta)