Refer - https://docs.tabulareditor.com/te3/other/release-notes/3_22_1.html?tabs=downloads$$$$$$Bugfixes in 3.22.1$$$Fixed a bug where the Data Refresh view would turn blank and not show additional refresh operations until the app was restarted. See #1461.

New in 3.22.0$$$Check out our release blog to get a brief overview of the most important updates in this release.$$$$$$(Enterprise Edition only) Tabular Editor 3 now fully supports Direct Lake on OneLake and Direct Lake on SQL. This means:$$$$$$The Table Import Wizard has new import options for Fabric Warehouses and Lakehouses. You no longer need to know the SQL analytics endpoint of the Warehouse/Lakehouse you wish to connect to. Instead; we show you a list of all the Warehouses/Lakehouses in your workspace; allowing you to choose the one you wish to use.$$$On the last page of the Table Import Wizard; you can choose whether to use Direct Lake in OneLake or SQL mode; or whether to configure the table for plain old import mode.$$$When the model contains tables in Direct Lake on OneLake mode; you can now also add tables in Import mode; in order to create mixed mode/hybrid models.$$$When previewing data in Direct Lake tables; we no longer restrict the number of rows returned (so you can freely scroll through all the data in the table; just like in Import mode). Be aware that all columns are swapped into the Semantic Model in the Fabric capacity when you perform a data preview. Consider using a DAX Query if you are concerned about memory consumption on your Fabric capacity.

New in 3.22.0$$$Check out our release blog to get a brief overview of the most important updates in this release.$$$$$$(Enterprise Edition only) Tabular Editor 3 now fully supports Direct Lake on OneLake and Direct Lake on SQL. This means:$$$$$$The Table Import Wizard has new import options for Fabric Warehouses and Lakehouses. You no longer need to know the SQL analytics endpoint of the Warehouse/Lakehouse you wish to connect to. Instead; we show you a list of all the Warehouses/Lakehouses in your workspace; allowing you to choose the one you wish to use.$$$On the last page of the Table Import Wizard; you can choose whether to use Direct Lake in OneLake or SQL mode; or whether to configure the table for plain old import mode.$$$When the model contains tables in Direct Lake on OneLake mode; you can now also add tables in Import mode; in order to create mixed mode/hybrid models.$$$When previewing data in Direct Lake tables; we no longer restrict the number of rows returned (so you can freely scroll through all the data in the table; just like in Import mode). Be aware that all columns are swapped into the Semantic Model in the Fabric capacity when you perform a data preview. Consider using a DAX Query if you are concerned about memory consumption on your Fabric capacity.

Improvements in 3.21.0$$$Weve made even more visual tweaks and improvements to our Diagram view in this release:$$$Icons visually indicate column data types.$$$Double-arrows when a relationship uses bi-directional cross filtering$$$A chevron button in the top-right corner of the table allows you to quickly toggle between various ways of displaying the columns in the table: All columns; key columns only; or no columns at all.$$$Various font size adjustments and other minor tweaks$$$Updated AMO/TOM to the latest version 19.94.1.1.$$$We have added a new property on the Model object; MetadataSource; which includes information about where the model metadata was loaded from. This is useful for C# scripts; for example if a script needs to iterate files in the same folder structure that the model metadata was loaded from. See the API docs for more information.$$$DAX Optimizer users can now also view the results for RLS and Calculation Item expressions through our DAX Optimizer Integration.$$$You can now script individual objects as TMDL (Tabular Model Definition Language) through the TOM Explorer. This is useful when you want to copy TMDL scripts from Tabular Editor to Power BI Desktop. Right-click an object and choose Export script > TMDL. Youll have the option of exporting the script to a file or directly to the clipboard.$$$Bugfixes in 3.21.0$$$Sorting by Progress or Duration in the Data Refresh view should now work correctly. Moreover; the Duration is no longer reset at the end of the refresh operation; for certain objects.$$$Various bugfixes related to the view of progress events in the Data Refresh view. For example; progress events should now arrive even if a previous session has expired (for example when Tabular Editor was idle for 60 minutes or more).$$$When partition deployment is disabled; or enabled but with incremental refresh partitions skipped; we now also leave the refresh policy settings on the table untouched (i.e. Source Expression; Polling Expression; etc.)$$$The Semantic Analyzer should no longer report an error when tables are connected by only inactive relationships; and a relationship is activated using the $$$USERELATIONSHIP$$$ function.$$$Fixed a bug where the Semantic Analyzer determined the wrong resulting data type when using the $$$GENERATESERIES$$$ function.$$$Fixed a bug with the Semantic Analyzer reporting false not found errors when $$$DEFINE$$$ing and referencing tables and columns inside a DAX script/query.$$$It is no longer possible to assign an empty name to an object through the TOM Explorer.$$$Certain words that were previously treated as reserved keywords; will no longer produce a semantic error; when used as unquoted table / variable references.$$$Fixed a bug where the DAX debugger didnt correctly gray out the inactive branch when using IF.EAGER or IF with only 2 parameters.$$$When opening a model with a workspace connection (i.e. Tabular Editor 3s Workspace Mode feature); we now correctly show the Microsoft Entra MFA prompt; if this was the authentication method used when the connection to the workspace database was originally established.$$$Our code editors now fully supports wide characters / unicode emojis (note; this is not an endorsement of emojis in DAX; but it is now possible to use them without breaking the editor :)).$$$If the .tmuo file contains invalid JSON; Tabular Editor will now show an error message and continue loading the model without the options specified in the file; instead of causing an unhandled exception.$$$Fixed a bug where the Refresh Policy options would not appear in the Properties grid on a table in a model loaded from disk; if the table did not have any partitions specified in the loaded metadata.$$$The Ctrl+U (Uncomment Code) and Ctrl+/ (Toggle comments) shortcuts were not working properly because of conflicts with other editor keyboard shortcuts. We have removed the default shortcuts from the conflicting commands. If you need keyboard bindings for the Editor.Lowercase a

Improvements in 3.21.0$$$Weve made even more visual tweaks and improvements to our Diagram view in this release:$$$Icons visually indicate column data types.$$$Double-arrows when a relationship uses bi-directional cross filtering$$$A chevron button in the top-right corner of the table allows you to quickly toggle between various ways of displaying the columns in the table: All columns; key columns only; or no columns at all.$$$Various font size adjustments and other minor tweaks$$$Updated AMO/TOM to the latest version 19.94.1.1.$$$We have added a new property on the Model object; MetadataSource; which includes information about where the model metadata was loaded from. This is useful for C# scripts; for example if a script needs to iterate files in the same folder structure that the model metadata was loaded from. See the API docs for more information.$$$DAX Optimizer users can now also view the results for RLS and Calculation Item expressions through our DAX Optimizer Integration.$$$You can now script individual objects as TMDL (Tabular Model Definition Language) through the TOM Explorer. This is useful when you want to copy TMDL scripts from Tabular Editor to Power BI Desktop. Right-click an object and choose Export script > TMDL. Youll have the option of exporting the script to a file or directly to the clipboard.$$$Bugfixes in 3.21.0$$$Sorting by Progress or Duration in the Data Refresh view should now work correctly. Moreover; the Duration is no longer reset at the end of the refresh operation; for certain objects.$$$Various bugfixes related to the view of progress events in the Data Refresh view. For example; progress events should now arrive even if a previous session has expired (for example when Tabular Editor was idle for 60 minutes or more).$$$When partition deployment is disabled; or enabled but with incremental refresh partitions skipped; we now also leave the refresh policy settings on the table untouched (i.e. Source Expression; Polling Expression; etc.)$$$The Semantic Analyzer should no longer report an error when tables are connected by only inactive relationships; and a relationship is activated using the $$$USERELATIONSHIP$$$ function.$$$Fixed a bug where the Semantic Analyzer determined the wrong resulting data type when using the $$$GENERATESERIES$$$ function.$$$Fixed a bug with the Semantic Analyzer reporting false not found errors when $$$DEFINE$$$ing and referencing tables and columns inside a DAX script/query.$$$It is no longer possible to assign an empty name to an object through the TOM Explorer.$$$Certain words that were previously treated as reserved keywords; will no longer produce a semantic error; when used as unquoted table / variable references.$$$Fixed a bug where the DAX debugger didnt correctly gray out the inactive branch when using IF.EAGER or IF with only 2 parameters.$$$When opening a model with a workspace connection (i.e. Tabular Editor 3s Workspace Mode feature); we now correctly show the Microsoft Entra MFA prompt; if this was the authentication method used when the connection to the workspace database was originally established.$$$Our code editors now fully supports wide characters / unicode emojis (note; this is not an endorsement of emojis in DAX; but it is now possible to use them without breaking the editor :)).$$$If the .tmuo file contains invalid JSON; Tabular Editor will now show an error message and continue loading the model without the options specified in the file; instead of causing an unhandled exception.$$$Fixed a bug where the Refresh Policy options would not appear in the Properties grid on a table in a model loaded from disk; if the table did not have any partitions specified in the loaded metadata.$$$The Ctrl+U (Uncomment Code) and Ctrl+/ (Toggle comments) shortcuts were not working properly because of conflicts with other editor keyboard shortcuts. We have removed the default shortcuts from the conflicting commands. If you need keyboard bindings for the Editor.Lowercase a