Tabular Editor 2.14.2

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

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)

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.

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.

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.

#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