Skip to content

@otykier otykier released this Mar 1, 2021 · 5 commits to master since this release

New in release 2.14.2:

  • Bumped TOM to version 19.6.3.4. Hoping this fixes issue #749.
  • Improved C# IntelliSense for certain methods regarding CalculationGroups / CalculationItems

Bug fixes in release 2.14.2:

  • Fixed various typos and text errors (see issue #764, #781, #782, #770, #776).
  • Fixed unhandled exception when changes are made in a connected instance of Power BI Desktop (see #767)

New in release 2.14.1:

  • Bumped TOM to version 19.6.3. This should fix issue #749.
  • The CLI schema check can now output warnings as errors, by settings a TabularEditor_SchemaCheckNoWarnings annotation on the model. More info.
  • Saving a Power BI Desktop model as a folder structure now uses the file name as the database name in the serialised files, instead of the guid generated by PBI Desktop. See issue #758.

Bug fixes in release 2.14.1:

  • Fixed issue #754
  • Fixed issue #751
  • Fixed an issue that prevented Tabular Editor from cleaning up traces on local instances of AS.
  • Fixed an issue that could sometimes cause a crash when deploying to a local instance of AS.

New in release 2.14.0:

  • Bumped TOM to version 19.6.0, which has improved support for Composite Models (DQ over AS) and added the EntityPartition type.
  • The Metadata Refresh feature can now append WHERE 1 = 0 to the SQL query of a partition before executing. To do this, add a new annotation at the partition, table or data source level with name TabularEditor_AddFalseWhereClause with value 1. See issue #736 for context.
  • Allow support for role and RLS creations in preparation for future versions of Power BI Desktop.
  • When loading a model from file, the Deployment Wizard will now suggest the file name as the name of the database to be deployed. See #745.

Bug fixes in release 2.14.0:

  • #707 (also fixed an issue with setting the SortByColumn property on multiple objects at once)
  • #716
  • #718 (relationships serialized as annotations now include the relationship name when a model contains variations)
  • #719
  • #722
  • #725
  • #729
  • #732
  • #735
  • #744
Assets 4

@otykier otykier released this Feb 11, 2021 · 17 commits to master since this release

New in release 2.14.1:

  • Bumped TOM to version 19.6.3. This should fix issue #749.
  • The CLI schema check can now output warnings as errors, by settings a TabularEditor_SchemaCheckNoWarnings annotation on the model. More info.
  • Saving a Power BI Desktop model as a folder structure now uses the file name as the database name in the serialised files, instead of the guid generated by PBI Desktop. See issue #758.

Bug fixes in release 2.14.1:

  • Fixed issue #754
  • Fixed issue #751
  • Fixed an issue that prevented Tabular Editor from cleaning up traces on local instances of AS.
  • Fixed an issue that could sometimes cause a crash when deploying to a local instance of AS.

New in release 2.14.0:

  • Bumped TOM to version 19.6.0, which has improved support for Composite Models (DQ over AS) and added the EntityPartition type.
  • The Metadata Refresh feature can now append WHERE 1 = 0 to the SQL query of a partition before executing. To do this, add a new annotation at the partition, table or data source level with name TabularEditor_AddFalseWhereClause with value 1. See issue #736 for context.
  • Allow support for role and RLS creations in preparation for future versions of Power BI Desktop.
  • When loading a model from file, the Deployment Wizard will now suggest the file name as the name of the database to be deployed. See #745.

Bug fixes in release 2.14.0:

  • #707 (also fixed an issue with setting the SortByColumn property on multiple objects at once)
  • #716
  • #718 (relationships serialized as annotations now include the relationship name when a model contains variations)
  • #719
  • #722
  • #725
  • #729
  • #732
  • #735
  • #744
Assets 4

@otykier otykier released this Feb 1, 2021 · 28 commits to master since this release

New in this release:

  • Bumped TOM to version 19.6.0, which has improved support for Composite Models (DQ over AS) and added the EntityPartition type.
  • The Metadata Refresh feature can now append WHERE 1 = 0 to the SQL query of a partition before executing. To do this, add a new annotation at the partition, table or data source level with name TabularEditor_AddFalseWhereClause with value 1. See issue #736 for context.
  • Allow support for role and RLS creations in preparation for future versions of Power BI Desktop.
  • When loading a model from file, the Deployment Wizard will now suggest the file name as the name of the database to be deployed. See #745.

Bug fixes in this release:

  • #707 (also fixed an issue with setting the SortByColumn property on multiple objects at once)
  • #716
  • #718 (relationships serialized as annotations now include the relationship name when a model contains variations)
  • #719
  • #722
  • #725
  • #729
  • #732
  • #735
  • #744
Assets 4

@otykier otykier released this Dec 4, 2020 · 62 commits to master since this release

Updates in 2.13.2:

  • Tabular Editor now uses a DMV to populate the list of databases when connecting to an instance of Analysis Services or the Power BI XMLA endpoint. This causes the list of databases to load much faster and does not cause evicted Power BI datasets to be loaded into memory prematurely. See issue #678.
  • Added basic support for Linguistic Metadata (see issue #257)
  • Fixed an issue where using the CustomAction method in a script through the CLI would cause a crash.
  • Fixed issue #696
  • Fixed issue #691 (thanks @warthurton)
  • Fixed issue #686

BREAKING CHANGE in 2.13.0

  • The FormatDax(string dax) script helper method has been deprecated. Please update your scripts to use the new syntax!. If you're using the method in an existing script, the execution will be throttled with a 5 second delay between calls! This was necessary to avoid overloading the DaxFormatter.com service. Also be aware that previous versions of Tabular Editor uses a different API, which might not work in the future.

Other changes in 2.13.0 and 2.13.1:

  • All documentation has been migrated from the GitHub Wiki to https://docs.tabulareditor.com. Please report any dead links, thanks!
  • Updated TOM/AMO to version 19.12.7.2 which has full support for Power BI Premium Gen2.
  • The -S / -SCRIPT switch for the Command-Line Interface can now execute multiple scripts (files / inline) sequentially.
  • It is now possible to add the -Y / -SKIPPOLICY flag after specifying -P / -PARTITIONS when deploying through CLI, in order to skip tables that use refresh policies when partitions would otherwise be overwritten. See #632 for more information.
  • Added support for Compatibility Level 1560
  • Deploying a new database now uses the TMSL createOrReplace command, since the create command has some issues on Power BI Premium Gen2. If you had issues deploying to Premium Gen2 previously, make sure to grab this update!
  • Fixed issue #683

Bugfixes in 2.13.0:

Assets 4

@otykier otykier released this Nov 25, 2020 · 83 commits to master since this release

Minor updates in 2.13.1:

  • Deploying a new database now uses the TMSL createOrReplace command, since the create command has some issues on Power BI Premium Gen2. If you had issues deploying to Premium Gen2 previously, make sure to grab this update!
  • Fixed issue #683

Major updates in 2.13.0:

All documentation has been migrated from the GitHub Wiki to https://docs.tabulareditor.com. Please report any dead links, thanks!

BREAKING CHANGE

  • The FormatDax(string dax) script helper method has been deprecated. Please update your scripts to use the new syntax!. If you're using the method in an existing script, the execution will be throttled with a 5 second delay between calls! This was necessary to avoid overloading the DaxFormatter.com service. Also be aware that previous versions of Tabular Editor uses a different API, which might not work in the future.

Other changes in 2.13.0:

  • Updated TOM/AMO to version 19.12.7.2 which has full support for Power BI Premium Gen2.
  • The -S / -SCRIPT switch for the Command-Line Interface can now execute multiple scripts (files / inline) sequentially.
  • It is now possible to add the -Y / -SKIPPOLICY flag after specifying -P / -PARTITIONS when deploying through CLI, in order to skip tables that use refresh policies when partitions would otherwise be overwritten. See #632 for more information.
  • Added support for Compatibility Level 1560

Bugfixes in 2.13.0:

Assets 4
  • 2.13.0
  • 9d24fef
  • Compare
    Choose a tag to compare
    Search for a tag
  • 2.13.0
  • 9d24fef
  • Compare
    Choose a tag to compare
    Search for a tag

@otykier otykier released this Nov 16, 2020 · 91 commits to master since this release

All documentation has been migrated from the GitHub Wiki to https://docs.tabulareditor.com. Please report any dead links, thanks!

BREAKING CHANGE

  • The FormatDax(string dax) script helper method has been deprecated. Please update your scripts to use the new syntax!. If you're using the method in an existing script, the execution will be throttled with a 5 second delay between calls! This was necessary to avoid overloading the DaxFormatter.com service. Also be aware that previous versions of Tabular Editor uses a different API, which might not work in the future.

Other changes in this release:

  • Updated TOM/AMO to version 19.12.7.2 which has full support for Power BI Premium Gen2.
  • The -S / -SCRIPT switch for the Command-Line Interface can now execute multiple scripts (files / inline) sequentially.
  • It is now possible to add the -Y / -SKIPPOLICY flag after specifying -P / -PARTITIONS when deploying through CLI, in order to skip tables that use refresh policies when partitions would otherwise be overwritten. See #632 for more information.
  • Added support for Compatibility Level 1560

Bugfixes in this release:

Assets 4

@otykier otykier released this Sep 15, 2020 · 171 commits to master since this release

Updates in Tabular Editor 2.12.4:

  • Updated TOM/AMO to latest version 19.10.0
  • Patch builds can now be skipped when Tabular Editor checks for updates during start-up (issue #608)
  • Fixed issue #585
  • Allow IME input in textboxes, fixing issue #601
  • Allow URL with the CLI -A switch, issue #603

Updates in Tabular Editor 2.12.3:

Updates in Tabular Editor 2.12.2:

  • Fix issue #584
  • Fixed bug with column selector dialog that didn't always enable/disable the OK button. In addition, item names should no longer be truncated.
  • Changed tooltip delay from 5 to 20 seconds when cursor is hovered over the item that triggered the tooltip, issue #586
  • Added option for specifying a custom compiler for scripts (for example, if you have Visual Studio installed, you can use the Roslyn compiler to take advantage of new C# language features when scripting)
  • Added a new set of global helper methods for displaying an object selection dialog to the user SelectColumn(), SelectTable(), SelectMeasure() and SelectObject(). These methods are useful when creating reusable scripts, such as generic scripts for adding Time Intelligence to a model.

Updates in Tabular Editor 2.12.1:

  • The following methods can now be executed globally (i.e. without prefixing them with Model.Database):
    • void ExecuteCommand(string tmsl)
    • IDataReader ExecuteReader(string dax)
    • DataSet ExecuteDax(string dax)
    • object EvaluateDax(string dax)
    • More information
  • Added the "TOP (without NOLOCK)" row reduction clause to the Import Tables Wizard. This is needed on Synapse SQL pools, since they don't allow the NOLOCK table hint. See also issue #582
  • Allowed creation of tables with M partitions even when no data sources have been defined, since M partitions can include data source and credential information inline.
  • Fixed issue with DataTable ExecuteDax(string dax) causing an error when nullable columns were returned.
  • ExecuteDax now returns a DataSet instead of a DataTable to allow for multiple EVALUATE statements in a single query.
  • The Output() script helper method now supports DataTables, to quickly visualise the result of a DAX expression obtained from ExecuteDax or EvaluateDax

Updates in Tabular Editor 2.12.0:

New features

  • Updated AMO/TOM to target latest version (v. 19.9.0.1)
  • Added support for editing table refresh policies
  • Added support for inline scripts in the CLI using the -S switch (simply type out the script as an alternative to specifying a script file name)
  • Added support for saving back to the source instance of AS using the CLI. Simply specify the -D switch without any additional arguments (this allows us to run a script against a Power BI Desktop model as an External Tool, see issue #530).
  • External libraries specified at the top of the script using the #r "library.name.dll" syntax are now resolved by looking in Tabular Editor's installation folder first and then in GAC.
  • Three new methods have been added to the Model.Database object. These make it possible to programmatically interact with the AS instance when model metadata have been loaded from a database. Expect to see some interesting examples of what these can be used for in the near future:
    • void ExecuteCommand(string tmsl)
    • IDataReader ExecuteReader(string dax)
    • DataTable ExecuteDax(string dax)

Bugfixes

  • Exception handling on AS trace clean-up
  • Fixed a bug where adding a level to a hierarchy and then subsequently undoing that operation could cause a crash
  • Fixed issue #565 - you now no longer need to enable unsupported Power BI features to be able to translate object names through the Explorer Tree
  • Fixed issue #557
  • Fixed issue #566 - measures that have the "Variant" data type (which may happen by adding certain calc group logic) now display the same format string options in the property grid, as if they had a numeric data type.
  • Best Practice Rules are now properly stored to the model annotations of a Power BI Desktop model
  • Fixed issue #568
  • Fixed issue #574
  • Fixed issue #575
  • Fixed issue #576
Assets 4

@otykier otykier released this Sep 11, 2020 · 179 commits to master since this release

Updates in Tabular Editor 2.12.3:

Updates in Tabular Editor 2.12.2:

  • Fix issue #584
  • Fixed bug with column selector dialog that didn't always enable/disable the OK button. In addition, item names should no longer be truncated.
  • Changed tooltip delay from 5 to 20 seconds when cursor is hovered over the item that triggered the tooltip, issue #586
  • Added option for specifying a custom compiler for scripts (for example, if you have Visual Studio installed, you can use the Roslyn compiler to take advantage of new C# language features when scripting)
  • Added a new set of global helper methods for displaying an object selection dialog to the user SelectColumn(), SelectTable(), SelectMeasure() and SelectObject(). These methods are useful when creating reusable scripts, such as generic scripts for adding Time Intelligence to a model.

Updates in Tabular Editor 2.12.1:

  • The following methods can now be executed globally (i.e. without prefixing them with Model.Database):
    • void ExecuteCommand(string tmsl)
    • IDataReader ExecuteReader(string dax)
    • DataSet ExecuteDax(string dax)
    • object EvaluateDax(string dax)
    • More information
  • Added the "TOP (without NOLOCK)" row reduction clause to the Import Tables Wizard. This is needed on Synapse SQL pools, since they don't allow the NOLOCK table hint. See also issue #582
  • Allowed creation of tables with M partitions even when no data sources have been defined, since M partitions can include data source and credential information inline.
  • Fixed issue with DataTable ExecuteDax(string dax) causing an error when nullable columns were returned.
  • ExecuteDax now returns a DataSet instead of a DataTable to allow for multiple EVALUATE statements in a single query.
  • The Output() script helper method now supports DataTables, to quickly visualise the result of a DAX expression obtained from ExecuteDax or EvaluateDax

Updates in Tabular Editor 2.12.0:

New features

  • Updated AMO/TOM to target latest version (v. 19.9.0.1)
  • Added support for editing table refresh policies
  • Added support for inline scripts in the CLI using the -S switch (simply type out the script as an alternative to specifying a script file name)
  • Added support for saving back to the source instance of AS using the CLI. Simply specify the -D switch without any additional arguments (this allows us to run a script against a Power BI Desktop model as an External Tool, see issue #530).
  • External libraries specified at the top of the script using the #r "library.name.dll" syntax are now resolved by looking in Tabular Editor's installation folder first and then in GAC.
  • Three new methods have been added to the Model.Database object. These make it possible to programmatically interact with the AS instance when model metadata have been loaded from a database. Expect to see some interesting examples of what these can be used for in the near future:
    • void ExecuteCommand(string tmsl)
    • IDataReader ExecuteReader(string dax)
    • DataTable ExecuteDax(string dax)

Bugfixes

  • Exception handling on AS trace clean-up
  • Fixed a bug where adding a level to a hierarchy and then subsequently undoing that operation could cause a crash
  • Fixed issue #565 - you now no longer need to enable unsupported Power BI features to be able to translate object names through the Explorer Tree
  • Fixed issue #557
  • Fixed issue #566 - measures that have the "Variant" data type (which may happen by adding certain calc group logic) now display the same format string options in the property grid, as if they had a numeric data type.
  • Best Practice Rules are now properly stored to the model annotations of a Power BI Desktop model
  • Fixed issue #568
  • Fixed issue #574
  • Fixed issue #575
  • Fixed issue #576
Assets 4

@otykier otykier released this Sep 8, 2020 · 183 commits to master since this release

Updates in Tabular Editor 2.12.2:

  • Fix issue #584
  • Fixed bug with column selector dialog that didn't always enable/disable the OK button. In addition, item names should no longer be truncated.
  • Changed tooltip delay from 5 to 20 seconds when cursor is hovered over the item that triggered the tooltip, issue #586
  • Added option for specifying a custom compiler for scripts (for example, if you have Visual Studio installed, you can use the Roslyn compiler to take advantage of new C# language features when scripting)
  • Added a new set of global helper methods for displaying an object selection dialog to the user SelectColumn(), SelectTable(), SelectMeasure() and SelectObject(). These methods are useful when creating reusable scripts, such as generic scripts for adding Time Intelligence to a model.

Updates in Tabular Editor 2.12.1:

  • The following methods can now be executed globally (i.e. without prefixing them with Model.Database):
    • void ExecuteCommand(string tmsl)
    • IDataReader ExecuteReader(string dax)
    • DataSet ExecuteDax(string dax)
    • object EvaluateDax(string dax)
    • More information
  • Added the "TOP (without NOLOCK)" row reduction clause to the Import Tables Wizard. This is needed on Synapse SQL pools, since they don't allow the NOLOCK table hint. See also issue #582
  • Allowed creation of tables with M partitions even when no data sources have been defined, since M partitions can include data source and credential information inline.
  • Fixed issue with DataTable ExecuteDax(string dax) causing an error when nullable columns were returned.
  • ExecuteDax now returns a DataSet instead of a DataTable to allow for multiple EVALUATE statements in a single query.
  • The Output() script helper method now supports DataTables, to quickly visualise the result of a DAX expression obtained from ExecuteDax or EvaluateDax

Updates in Tabular Editor 2.12.0:

New features

  • Updated AMO/TOM to target latest version (v. 19.9.0.1)
  • Added support for editing table refresh policies
  • Added support for inline scripts in the CLI using the -S switch (simply type out the script as an alternative to specifying a script file name)
  • Added support for saving back to the source instance of AS using the CLI. Simply specify the -D switch without any additional arguments (this allows us to run a script against a Power BI Desktop model as an External Tool, see issue #530).
  • External libraries specified at the top of the script using the #r "library.name.dll" syntax are now resolved by looking in Tabular Editor's installation folder first and then in GAC.
  • Three new methods have been added to the Model.Database object. These make it possible to programmatically interact with the AS instance when model metadata have been loaded from a database. Expect to see some interesting examples of what these can be used for in the near future:
    • void ExecuteCommand(string tmsl)
    • IDataReader ExecuteReader(string dax)
    • DataTable ExecuteDax(string dax)

Bugfixes

  • Exception handling on AS trace clean-up
  • Fixed a bug where adding a level to a hierarchy and then subsequently undoing that operation could cause a crash
  • Fixed issue #565 - you now no longer need to enable unsupported Power BI features to be able to translate object names through the Explorer Tree
  • Fixed issue #557
  • Fixed issue #566 - measures that have the "Variant" data type (which may happen by adding certain calc group logic) now display the same format string options in the property grid, as if they had a numeric data type.
  • Best Practice Rules are now properly stored to the model annotations of a Power BI Desktop model
  • Fixed issue #568
  • Fixed issue #574
  • Fixed issue #575
  • Fixed issue #576
Assets 4

@otykier otykier released this Aug 29, 2020 · 194 commits to master since this release

Updates in Tabular Editor 2.12.1:

  • The following methods can now be executed globally (i.e. without prefixing them with Model.Database):
    • void ExecuteCommand(string tmsl)
    • IDataReader ExecuteReader(string dax)
    • DataSet ExecuteDax(string dax)
    • object EvaluateDax(string dax)
    • More information
  • Added the "TOP (without NOLOCK)" row reduction clause to the Import Tables Wizard. This is needed on Synapse SQL pools, since they don't allow the NOLOCK table hint. See also issue #582
  • Allowed creation of tables with M partitions even when no data sources have been defined, since M partitions can include data source and credential information inline.
  • Fixed issue with DataTable ExecuteDax(string dax) causing an error when nullable columns were returned.
  • ExecuteDax now returns a DataSet instead of a DataTable to allow for multiple EVALUATE statements in a single query.
  • The Output() script helper method now supports DataTables, to quickly visualise the result of a DAX expression obtained from ExecuteDax or EvaluateDax

Updates in Tabular Editor 2.12.0:

New features

  • Updated AMO/TOM to target latest version (v. 19.9.0.1)
  • Added support for editing table refresh policies
  • Added support for inline scripts in the CLI using the -S switch (simply type out the script as an alternative to specifying a script file name)
  • Added support for saving back to the source instance of AS using the CLI. Simply specify the -D switch without any additional arguments (this allows us to run a script against a Power BI Desktop model as an External Tool, see issue #530).
  • External libraries specified at the top of the script using the #r "library.name.dll" syntax are now resolved by looking in Tabular Editor's installation folder first and then in GAC.
  • Three new methods have been added to the Model.Database object. These make it possible to programmatically interact with the AS instance when model metadata have been loaded from a database. Expect to see some interesting examples of what these can be used for in the near future:
    • void ExecuteCommand(string tmsl)
    • IDataReader ExecuteReader(string dax)
    • DataTable ExecuteDax(string dax)

Bugfixes

  • Exception handling on AS trace clean-up
  • Fixed a bug where adding a level to a hierarchy and then subsequently undoing that operation could cause a crash
  • Fixed issue #565 - you now no longer need to enable unsupported Power BI features to be able to translate object names through the Explorer Tree
  • Fixed issue #557
  • Fixed issue #566 - measures that have the "Variant" data type (which may happen by adding certain calc group logic) now display the same format string options in the property grid, as if they had a numeric data type.
  • Best Practice Rules are now properly stored to the model annotations of a Power BI Desktop model
  • Fixed issue #568
  • Fixed issue #574
  • Fixed issue #575
  • Fixed issue #576
Assets 4