Skip to content

Tabular Editor 2.13.2

Compare
Choose a tag to compare
@otykier otykier released this 04 Dec 12:20
· 383 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: