Skip to content

@otykier otykier released this Sep 15, 2020 · 1 commit 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 · 9 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 · 13 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 · 24 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

@otykier otykier released this Aug 24, 2020 · 32 commits to master since this release

Tabular Editor 2.12.0 is here! Many minor updates in this release:

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 Jul 31, 2020 · 53 commits to master since this release

Minor improvements since last version:

  • Now targeting TOM/AMO 19.6.0.
  • #554 - StructuredDataSources now also expose an Options object in the property grid, which lets you add/remove strings to the TOM DataSourceOptions dictionary (connection timeout, etc.)
  • StructuredDataSources now also expose an Address object in the property grid, which lets you add/remove strings to the TOM ConnectionAddress dictionary.
  • Added a new convenient script method, MoveTo(table) on measures, which makes it easy to delete a measure from a table and create a deep clone of the measure on another table (effectively moving the measure from one table to another).
  • Minor IntelliSense improvements to C# script editor.

Bug fixes since last version:

  • Issue #533 "Duplicate object" now respects the "Include translations" setting under File > Preferences. Default value of this setting for new installations is "False" - previously was "True". In addition, new objects that are added to the model will no longer have a default name translation applied.
  • Issue #534
  • Issue #541
  • Issue #547
  • Issue #555
  • Issue #556
  • Clean up trace started on local instances of Analysis Services when connecting to another database
Assets 4

@otykier otykier released this Jul 13, 2020 · 71 commits to master since this release

Update 2.11.6 fixes issues #228, #519, #520, #524 and #525.

Major improvements since 2.10.0:

  • Ability to delete custom actions from within the UI (thanks @albertospelta)
  • Major improvements to ExportProperties / ImportProperties (thanks @albertospelta). How would you like to edit object translations, perspective membership, etc. in an Excel sheet?
  • Preparations for the upcoming Power BI Desktop "External Tools" integration. For example, there's a new setting under File > Preferences, which will cause Tabular Editor to automatically detect changes made to a Power BI Desktop model from inside Desktop, refreshing the TOM tree in Tabular Editor. The setting is enabled by default, but since this feature is using Analysis Services Tracing, you can disable it if it's causing any kind of issues.
  • Database Compatibility Level can now be modified from inside the UI, making it possible to upgrade models from 1200->1400, 1400->1500 and 1500->1520. Please note that you cannot upgrade a model using the Deployment Wizard. Instead, open the model from an existing database, change the compatibility level, and hit save.

Minor improvements since 2.10.0:

  • Table and Column objects now display a dropdown on their DataCategory property (see #498). The dropdown is populated with values according to the MS-SSAS-T specification.
  • Now targeting AMO 19.4.0.2
  • Added support for the AlternateOf column property (used when setting up aggregations on a Power BI model). More information.
  • #407 - you can now copy BPA results to the clipboard
  • #426 - dependency view now defaults to relationships when opening it on a table
  • #524 - StructuredDataSources now expose a Credential object in the property grid, which lets you add/remove strings to the TOM Credential dictionary (blob storage keys, etc.)

Bug fixes since 2.10.0:

  • #485 Calculated tables should no longer cause issues on DirectQuery models.
  • #486 Fixed issue with PBI warning message showing up incorrectly
  • #488 Calculation Items are now included when using the filter box
  • #491 An error message is now shown if a LINQ-style filter is malformed
  • #500 Calling ExportProperties with one or more properties of type Tabular Object, such as "Parent", now no longer gives an error.
  • Fixed path of Tabular Editor executable in the .pbitool.json file, in case Tabular Editor is installed in a non-default location.
  • Issue #504
  • Fixed an unhandled exception when invoking the BPA rule manager through the Tools menu.
  • When connected to a model on a local AS instance with trace enabled, external changes to other models on the same instance will no longer trigger an update.
  • Issue #507
  • Issue #509
  • An external model refresh now triggers an update in Tabular Editor similar to external model changes (local AS instance only)
  • Issue #228 (thanks @N0Ge)
  • Issue #519
  • Issue #520
  • Issue #525 (changed wording on Connect Page to indicate that "Integrated Security" also encompasses Azure AD logins)
Assets 4

@otykier otykier released this Jun 30, 2020 · 82 commits to master since this release

This update fixes issue #407, #426, #509 and improves the way Tabular Editor detects remote changes to the model.

Major improvements since 2.10.0:

  • Ability to delete custom actions from within the UI (thanks @albertospelta)
  • Major improvements to ExportProperties / ImportProperties (thanks @albertospelta). How would you like to edit object translations, perspective membership, etc. in an Excel sheet?
  • Preparations for the upcoming Power BI Desktop "External Tools" integration. For example, there's a new setting under File > Preferences, which will cause Tabular Editor to automatically detect changes made to a Power BI Desktop model from inside Desktop, refreshing the TOM tree in Tabular Editor. The setting is enabled by default, but since this feature is using Analysis Services Tracing, you can disable it if it's causing any kind of issues.
  • Database Compatibility Level can now be modified from inside the UI, making it possible to upgrade models from 1200->1400, 1400->1500 and 1500->1520. Please note that you cannot upgrade a model using the Deployment Wizard. Instead, open the model from an existing database, change the compatibility level, and hit save.

Minor improvements since 2.10.0:

  • Table and Column objects now display a dropdown on their DataCategory property (see #498). The dropdown is populated with values according to the MS-SSAS-T specification.
  • Now targeting AMO 19.4.0.2
  • Added support for the AlternateOf column property (used when setting up aggregations on a Power BI model). More information.
  • #407 - you can now copy BPA results to the clipboard
  • #426 - dependency view now defaults to relationships when opening it on a table

Bug fixes since 2.10.0:

  • #485 Calculated tables should no longer cause issues on DirectQuery models.
  • #486 Fixed issue with PBI warning message showing up incorrectly
  • #488 Calculation Items are now included when using the filter box
  • #491 An error message is now shown if a LINQ-style filter is malformed
  • #500 Calling ExportProperties with one or more properties of type Tabular Object, such as "Parent", now no longer gives an error.
  • Fixed path of Tabular Editor executable in the .pbitool.json file, in case Tabular Editor is installed in a non-default location.
  • Issue #504
  • Fixed an unhandled exception when invoking the BPA rule manager through the Tools menu.
  • When connected to a model on a local AS instance with trace enabled, external changes to other models on the same instance will no longer trigger an update.
  • Issue #507
  • Issue #509
  • An external model refresh now triggers an update in Tabular Editor similar to external model changes (local AS instance only)
Assets 4

@otykier otykier released this Jun 26, 2020 · 92 commits to master since this release

This update fixes issue #507.

Major improvements since 2.10.0:

  • Ability to delete custom actions from within the UI (thanks @albertospelta)
  • Major improvements to ExportProperties / ImportProperties (thanks @albertospelta). How would you like to edit object translations, perspective membership, etc. in an Excel sheet?
  • Preparations for the upcoming Power BI Desktop "External Tools" integration. For example, there's a new setting under File > Preferences, which will cause Tabular Editor to automatically detect changes made to a Power BI Desktop model from inside Desktop, refreshing the TOM tree in Tabular Editor. The setting is enabled by default, but since this feature is using Analysis Services Tracing, you can disable it if it's causing any kind of issues.
  • Database Compatibility Level can now be modified from inside the UI, making it possible to upgrade models from 1200->1400, 1400->1500 and 1500->1520. Please note that you cannot upgrade a model using the Deployment Wizard. Instead, open the model from an existing database, change the compatibility level, and hit save.

Minor improvements since 2.10.0:

  • Table and Column objects now display a dropdown on their DataCategory property (see #498). The dropdown is populated with values according to the MS-SSAS-T specification.
  • Now targeting AMO 19.4.0.2
  • Added support for the AlternateOf column property (used when setting up aggregations on a Power BI model). More information.

Bug fixes since 2.10.0:

  • #485 Calculated tables should no longer cause issues on DirectQuery models.
  • #486 Fixed issue with PBI warning message showing up incorrectly
  • #488 Calculation Items are now included when using the filter box
  • #491 An error message is now shown if a LINQ-style filter is malformed
  • #500 Calling ExportProperties with one or more properties of type Tabular Object, such as "Parent", now no longer gives an error.
  • Fixed path of Tabular Editor executable in the .pbitool.json file, in case Tabular Editor is installed in a non-default location.
  • Issue #504
  • Fixed an unhandled exception when invoking the BPA rule manager through the Tools menu.
  • When connected to a model on a local AS instance with trace enabled, external changes to other models on the same instance will no longer trigger an update.
  • Issue #507
Assets 4

@otykier otykier released this Jun 26, 2020 · 94 commits to master since this release

Bugfixes in this release:

  • When connected to a model on a local AS instance with trace enabled, external changes to other models on the same instance will no longer trigger an update.

Minor improvements in this release:

  • Added support for the AlternateOf column property (used when setting up aggregations on a Power BI model). More information.
Assets 4
You can’t perform that action at this time.