Improvements in 3.26.1$$$AI Assistant$$$Reduced AI assistant token consumption with a better progressive-disclosure approach for model metadata discovery; which should help avoid hitting input token rate limits.$$$Enabled use of caching for Anthropic models (which werent cached previously)$$$Better; more targetted tools that help LLMs produce better results; including a model metadata search tool.$$$The OpenAI and Anthropic AI providers now support an optional base URL override; enabling use with OpenAI regional endpoints and models deployed in Microsoft Foundry.$$$For Open AI and Anthropic; the model name field is now pre-populated with known models; while still allowing custom model names.$$$Hovering over the AI chat token counter displays a tooltip with a breakdown of full-price input tokens; cached input tokens; cache writes; and output tokens. The slider bar continues to show context window pressure.$$$Table Import Wizard$$$The Table Import Wizard now filters the catalog and schema lists for Databricks connections based on the settings already specified on the data source. When a catalog is already configured; the wizard skips the catalog query. Tables and views are filtered by schema when one is specified; reducing clutter in large catalogs.$$$New Databricks connections now default to Implementation 2.0 in the connection dialog. Existing connections that do not explicitly specify an Implementation version are left unchanged.$$$Added support for Databricks service principal authentication using OAuth Machine-to-Machine (M2M) flow. A new OAuth (M2M) option in the Databricks connection dialog lets you authenticate with a Client ID and Client Secret. The ODBC driver handles token acquisition and refresh automatically. This works across all Databricks clouds (Azure; AWS; GCP).$$$Bugfixes in 3.26.1$$$Fixed a bug where always-inject custom instructions (e.g. core.md) were included in both the base system prompt and the per-turn injection; causing ~1;200 tokens of duplicated content on every API call.$$$Fixed an issue where Ctrl+Z (undo) and Ctrl+Y (redo) keyboard shortcuts were not working in the AI Assistant chat input field.$$$Fixed an issue where the AI Assistant would fail with an HTTP 400 error when using models that do not support custom temperature values (e.g. OpenAI o-series reasoning models). The assistant now automatically retries without the temperature parameter when this error is detected.$$$Fixed low-contrast rendering of inline code (e.g.; `Tokenize()`) inside user chat messages on the light theme.$$$Fixed an issue where clicking Allow (not Allow for session) on a consent prompt would silently grant consent to a second tool call in the same turn without prompting. Each tool call now requires its own consent when using one-time approval.$$$Fixed an issue where the AI Assistants knowledge base search would fail when the query contained special characters such as # (e.g. searching for C# language support).$$$Fixed the AI provider endpoint tooltip not updating when switching between providers in the preferences dialog.$$$Fixed an issue where the AI Assistant errored when chatting with models hosted on Databricks via a custom OpenAI-compatible provider.$$$Fixed an issue where AI Assistant tool calling silently failed when using custom OpenAI-compatible providers such as OpenRouter. The assistant would receive tool call requests from the model but never execute them; causing it to appear stuck or respond with text only.$$$Fixed the Updating document content inline marker showing the document ID instead of the new content in its tooltip and Copy button.$$$Fixed the OpenAI Project ID preference being incorrectly bound to Organization ID.$$$Fixed an issue where the Table Import Wizard would reconstruct Databricks M expression options from scratch instead of preserving the original data source options; potentially losing non-default settings.$$$Fixed a bug that would cause the TOM Explorer / Properties view to lock up a

Bugfixes in 3.26.0$$$Multiple Calendar Editor bugfixes and stability improvements$$$Macro tooltips are shown correctly in TOM Explorer; toolbar buttons and header menu items$$$Fixed a bug where BPA rule tooltips appeared on violating object rows in the Best Practice Analyzer; interfering with right-click context menus. Tooltips now only appear on rule rows.$$$Fixed an issue in our M Analyzer; ensuring that M functions such as Table.ColumnNames; Table.ExpandTableColumn; Table.ReplaceValues; and many of the Text.* functions; are now supported for offline schema detection (i.e. when performing an Update Table Schema while Use Analysis Services for change detection is disabled).$$$Fixed a bug that would cause an unhandled exception when attempting to resize the items in the Property Grid; while editing a property.$$$Fixed an issue in the M Editor where -- was incorrectly highlighted as a comment. In Power Query M; only // denotes a single-line comment.$$$Fixed an issue in the C# script editor where typing certain characters — such as a period; bracket; or digit — immediately after an auto-complete suggestion could cause the committed text to be duplicated or the wrong range of text to be replaced; due to an async race condition in the completion handler.$$$Fixed an unhandled NullReferenceException crash in the DAX Debugger Call Tree when expanding or clicking on nodes for iterator functions such as SUMX; MAXX; or MINX. After dismissing the error; the Call Tree would become unresponsive until Tabular Editor was restarted.$$$Fixed a bug in offline schema updates where unsupported M functions in nested shared expressions were silently ignored; leading to silent failures to update table schemas for partitions referencing these shared expressions. Now such functions are reported to the user

Bugfixes in 3.25.5$$$Fixed a bug that would prevent Calculation Items from being serialized as individual files using Tabular Editors JSON based save-to-folder.$$$Fixed a bug with the Replace IFERROR with DIVIDE code action; which would sometimes trigger on unrelated functions.$$$Fixed an issue where the model name in Power BI Desktop files was wrongly tuncated when using hypens. See this issue$$$Fixed a minor bug with the grab handle on the C# auto-complete popup being obscured by the toggle buttons on some DPI scaling settings.$$$Fixed an issue in SQL Legacy partitions where the comment shortcut and toolbar button inserted DAX-style comments (//) instead of SQL comments (--)$$$Find & Replace dialog error exception fixed. The replace tab will now only be shown when there are open documents to replace something in. See this issue$$$Fixed the apperance of the right-click context menu on the C#; M; and SQL code editors.$$$Fixed a race condition in the Model Processing Service that could cause intermittent crashes during data refresh operations; particularly when refreshing large models or models that generate warnings.$$$Fixed an error when switching cultures/translations in models containing user-defined functions.$$$Fixed an issue where hidden objects were not available in the Calendar Editor. Hidden columns and tables now correctly appear in the table and column dropdowns and in the Associated Columns and Time-Related Columns panels.$$$Fix NullReferenceException when updating schema on ODBC/OleDb data sources$$$Fixed an issue where Replace All with scope set to Selection would incorrectly replace text throughout the entire document instead of only within the selected text range. This affected DAX queries; DAX scripts; and C# script editors.$$$Fixed an issue where the TOM Explorer would become unstable after using the Revert option from the File menu.$$$Fixed a transent issue with the TOM Explorer not showing error/warning indicators.$$$Fixed an issue with measure names displaying incorrectly in the Messages view.$$$Fixed an issue where the Calendar Editor would remain disabled after pasting a Date table with calendars into a newly created model. The view now correctly updates and enables itself when calendars are added via paste operations.$$$Fixed a bug in the Calendar Editor where checking a column in the Associated Columns panel while a search filter was active would record the wrong column.$$$Fixed a bug in the Calendar Editor where deleting a calendar would clear the Time-Related Columns captions for all remaining calendars until changes were accepted.$$$Fixed an issue where a calendar created via TOM Explorer would not appear in the Calendar Editor until the calendar was subsequently renamed.$$$Fixed an unhandled NullReferenceException crash when undoing the removal of a Time-Related Column Group in the Calendar Editors Collection Editor.$$$Fixed an issue in our M Analyzer; ensuring that M functions such as Table.ColumnNames; Table.ExpandTableColumn; Table.ReplaceValues; and many of the Text.* functions; are now supported for offline schema detection (i.e. when performing an Update Table Schema while Use Analysis Services for change detection is disabled).

Bugfixes in 3.25.5$$$Fixed a bug that would prevent Calculation Items from being serialized as individual files using Tabular Editors JSON based save-to-folder.$$$Fixed a bug with the Replace IFERROR with DIVIDE code action; which would sometimes trigger on unrelated functions.$$$Fixed an issue where the model name in Power BI Desktop files was wrongly tuncated when using hypens. See this issue$$$Fixed a minor bug with the grab handle on the C# auto-complete popup being obscured by the toggle buttons on some DPI scaling settings.$$$Fixed an issue in SQL Legacy partitions where the comment shortcut and toolbar button inserted DAX-style comments (//) instead of SQL comments (--)$$$Find & Replace dialog error exception fixed. The replace tab will now only be shown when there are open documents to replace something in. See this issue$$$Fixed the apperance of the right-click context menu on the C#; M; and SQL code editors.$$$Fixed a race condition in the Model Processing Service that could cause intermittent crashes during data refresh operations; particularly when refreshing large models or models that generate warnings.$$$Fixed an error when switching cultures/translations in models containing user-defined functions.$$$Fixed an issue where hidden objects were not available in the Calendar Editor. Hidden columns and tables now correctly appear in the table and column dropdowns and in the Associated Columns and Time-Related Columns panels.$$$Fix NullReferenceException when updating schema on ODBC/OleDb data sources$$$Fixed an issue where Replace All with scope set to Selection would incorrectly replace text throughout the entire document instead of only within the selected text range. This affected DAX queries; DAX scripts; and C# script editors.$$$Fixed an issue where the TOM Explorer would become unstable after using the Revert option from the File menu.$$$Fixed a transent issue with the TOM Explorer not showing error/warning indicators.$$$Fixed an issue with measure names displaying incorrectly in the Messages view.$$$Fixed an issue where the Calendar Editor would remain disabled after pasting a Date table with calendars into a newly created model. The view now correctly updates and enables itself when calendars are added via paste operations.$$$Fixed a bug in the Calendar Editor where checking a column in the Associated Columns panel while a search filter was active would record the wrong column.$$$Fixed a bug in the Calendar Editor where deleting a calendar would clear the Time-Related Columns captions for all remaining calendars until changes were accepted.$$$Fixed an issue where a calendar created via TOM Explorer would not appear in the Calendar Editor until the calendar was subsequently renamed.$$$Fixed an unhandled NullReferenceException crash when undoing the removal of a Time-Related Column Group in the Calendar Editors Collection Editor.$$$Fixed an issue in our M Analyzer; ensuring that M functions such as Table.ColumnNames; Table.ExpandTableColumn; Table.ReplaceValues; and many of the Text.* functions; are now supported for offline schema detection (i.e. when performing an Update Table Schema while Use Analysis Services for change detection is disabled).

Bugfixes in 3.25.1$$$Fixed some strings that incorrectly indicated that built-in BPA rules were only available for Enterprise Edition.

Bugfixes in 3.25.1$$$Fixed some strings that incorrectly indicated that built-in BPA rules were only available for Enterprise Edition.

Bugfixes in 3.24.2$$$Fixed a bug that caused an unhandled exception when multiple errors/warnings were reported from the connected AS instance during a refresh operation.

Bugfixes in 3.24.2$$$Fixed a bug that caused an unhandled exception when multiple errors/warnings were reported from the connected AS instance during a refresh operation.

Improvements in 3.24.0$$$Updated the Microsoft.AnalysisServices client library to v. 19.106.1; which includes fixes to TMDL serialization issues; among other improvements.$$$Updated the Dax.Vpax library to v. 1.11.0; which adds support for calendars and UDFs; among other improvements.$$$UDFs now have the Batch Rename option (F2) in the context menu. This is useful if you want to rename multiple UDFs at once; e.g. to add or remove a common prefix or suffix; or to change the namespace of multiple UDFs at once.$$$UDFs and Calendar objects can now be dragged in to C# scripts and DAX code editors just like other objects (measures; columns; etc.).$$$Substantial improvements have been made to our DAX editors support for Visual Calculations. This is relevant when editing UDFs or DAX Queries. For example; we no longer show false error messages when using a Visual Calculation function in a UDF; as long as no model objects are referenced in that UDF or any UDF it calls. The auto-complete will now also suggest Visual Calculation functions and visual column references when appropriate. Axis keywords (ROWS; COLUMNS) are now also properly supported in Visual Calculations.$$$We added a Show/hide calendars toggle button next to the Show/hide partitions button above the TOM Explorer. The button is only shown when working on a model at Compatibility Level 1701 or higher.$$$We now show a warning in the tooltip of any week-based DAX time intelligence functions; if the current model does not contain a calendar with weekly granularity (without which these functions will not work).$$$The Pivot Grid Field List can now be toggled on or off using the dedicated button in the Pivot Grid toolbar.$$$Saved Pivot Grids now retain the settings for Show empty values on columns and Show empty values on rows.$$$Our C# editor now has auto-complete support for UDFs and Calendars on the Selected object. For example; you can now type Selected.Calendars to get a list of the currently selected calendars in the TOM Explorer.$$$You can now export TMDL scripts for multiple objects at once; by multi-selecting objects in the TOM Explorer; right-click and choosing and choosing Export script > TMDL > To clipboard / To file from the context menu.$$$Tabular Editor now lets you open .pbism files; which are commonly found in Power BI Project folders.$$$Added a Fix Expression Editor to the BPA Rules Editor; which allows you to write BPA fix rules directly inside the Editor.$$$Bugfixes in 3.24.0$$$Fixed bugs related to dragging/dropping objects in the TOM Explorer; and also show a warning message when a drag/drop operation fails.$$$When connecting to models in PBI Desktop (September 2025 or newer); you should now (again) be able to perform refresh operations from within TE3.$$$Fixed a bug where Calendars would appear next to measures/columns of a table; instead of inside the Calendars collection in the TOM Explorer.$$$Our Semantic Analyzer will no longer show a false error when using certain UDF parameter type hints in combinations that are valid; for example: (a: TABLE EXPR) => .... For more details; see #1492.$$$UDFs no longer show false error messages when column references cannot be immediately resolved. For example; an UDF defined as (t) => SUMX(t; [SomeColumn]) will no longer show an error on [SomeColumn]; as the expression may be valid when the UDF is called with a table that contains a column named SomeColumn.$$$Using UDF expression parameters in calls to $$$LOOKUPVALUE$$$ or $$$GROUPBY$$$ no longer results in false errors from the Semantic Analyzer.$$$The Semantic Analyzer now correctly deals with DAX variables that shadow outer variables (or UDF parameters) with identical names (e.g. (a) => VAR a = <expression> ...)$$$When creating a Calendar Column Association; we no longer show the Unknown time unit in the dropdown; as this is not a valid option anyway.$$$Fixed a bug where processing-related buttons (Clear completed; Clear All; Cancel; Pause) remained active when swit

Improvements in 3.24.0$$$Updated the Microsoft.AnalysisServices client library to v. 19.106.1; which includes fixes to TMDL serialization issues; among other improvements.$$$Updated the Dax.Vpax library to v. 1.11.0; which adds support for calendars and UDFs; among other improvements.$$$UDFs now have the Batch Rename option (F2) in the context menu. This is useful if you want to rename multiple UDFs at once; e.g. to add or remove a common prefix or suffix; or to change the namespace of multiple UDFs at once.$$$UDFs and Calendar objects can now be dragged in to C# scripts and DAX code editors just like other objects (measures; columns; etc.).$$$Substantial improvements have been made to our DAX editors support for Visual Calculations. This is relevant when editing UDFs or DAX Queries. For example; we no longer show false error messages when using a Visual Calculation function in a UDF; as long as no model objects are referenced in that UDF or any UDF it calls. The auto-complete will now also suggest Visual Calculation functions and visual column references when appropriate. Axis keywords (ROWS; COLUMNS) are now also properly supported in Visual Calculations.$$$We added a Show/hide calendars toggle button next to the Show/hide partitions button above the TOM Explorer. The button is only shown when working on a model at Compatibility Level 1701 or higher.$$$We now show a warning in the tooltip of any week-based DAX time intelligence functions; if the current model does not contain a calendar with weekly granularity (without which these functions will not work).$$$The Pivot Grid Field List can now be toggled on or off using the dedicated button in the Pivot Grid toolbar.$$$Saved Pivot Grids now retain the settings for Show empty values on columns and Show empty values on rows.$$$Our C# editor now has auto-complete support for UDFs and Calendars on the Selected object. For example; you can now type Selected.Calendars to get a list of the currently selected calendars in the TOM Explorer.$$$You can now export TMDL scripts for multiple objects at once; by multi-selecting objects in the TOM Explorer; right-click and choosing and choosing Export script > TMDL > To clipboard / To file from the context menu.$$$Tabular Editor now lets you open .pbism files; which are commonly found in Power BI Project folders.$$$Added a Fix Expression Editor to the BPA Rules Editor; which allows you to write BPA fix rules directly inside the Editor.$$$Bugfixes in 3.24.0$$$Fixed bugs related to dragging/dropping objects in the TOM Explorer; and also show a warning message when a drag/drop operation fails.$$$When connecting to models in PBI Desktop (September 2025 or newer); you should now (again) be able to perform refresh operations from within TE3.$$$Fixed a bug where Calendars would appear next to measures/columns of a table; instead of inside the Calendars collection in the TOM Explorer.$$$Our Semantic Analyzer will no longer show a false error when using certain UDF parameter type hints in combinations that are valid; for example: (a: TABLE EXPR) => .... For more details; see #1492.$$$UDFs no longer show false error messages when column references cannot be immediately resolved. For example; an UDF defined as (t) => SUMX(t; [SomeColumn]) will no longer show an error on [SomeColumn]; as the expression may be valid when the UDF is called with a table that contains a column named SomeColumn.$$$Using UDF expression parameters in calls to $$$LOOKUPVALUE$$$ or $$$GROUPBY$$$ no longer results in false errors from the Semantic Analyzer.$$$The Semantic Analyzer now correctly deals with DAX variables that shadow outer variables (or UDF parameters) with identical names (e.g. (a) => VAR a = <expression> ...)$$$When creating a Calendar Column Association; we no longer show the Unknown time unit in the dropdown; as this is not a valid option anyway.$$$Fixed a bug where processing-related buttons (Clear completed; Clear All; Cancel; Pause) remained active when swit

Improvements in 3.23.1$$$We added Compatibility Level 1700 (SQL Server 2025) to the dropdown in the New Model dialog. Moreover; the default Compatibility Level for Power BI models has been updated to 1702 (which is needed for UDFs and Calendars).$$$Bugfixes in 3.23.1$$$This update fixes several bugs related to UDFs and Calendars compared to 3.23.0. Mostly related to our built-in DAX parser; but also several tweaks and stability improvements for things like autocomplete; formatting; etc.$$$We have downgraded the version of MSAL (Microsoft.Identity.Client) library to 4.72.1; as the newer versions of this library (used in the previous release of Tabular Editor 3); do not work well with the AS client library; causing the application to hang when using the Microsoft Entra ID authentication option.$$$Removed the Duplicate and Cut/Copy/Paste/Delete actions for Calculated Table Columns; as these objects cannot be manually added/removed from tables; and doing so would cause issues upon saving the changes to Analysis Services / Power BI. You should modify the DAX of the calculated table instead.$$$Mirrored Azure Databricks catalogs are now also shown in the Table Import Wizard UI; when choosing the Fabric Mirrored Database option.$$$Fixed an issue where opening a model created with older versions of Power BI Desktop would cause a The given key Extended Properties was not present in the dictionary error.$$$Fixed a bug that prevented forward references in DAX script object properties. I.e. you no longer get an error if the FormatString property of a measure references a measure defined later in the script.

Improvements in 3.23.1$$$We added Compatibility Level 1700 (SQL Server 2025) to the dropdown in the New Model dialog. Moreover; the default Compatibility Level for Power BI models has been updated to 1702 (which is needed for UDFs and Calendars).$$$Bugfixes in 3.23.1$$$This update fixes several bugs related to UDFs and Calendars compared to 3.23.0. Mostly related to our built-in DAX parser; but also several tweaks and stability improvements for things like autocomplete; formatting; etc.$$$We have downgraded the version of MSAL (Microsoft.Identity.Client) library to 4.72.1; as the newer versions of this library (used in the previous release of Tabular Editor 3); do not work well with the AS client library; causing the application to hang when using the Microsoft Entra ID authentication option.$$$Removed the Duplicate and Cut/Copy/Paste/Delete actions for Calculated Table Columns; as these objects cannot be manually added/removed from tables; and doing so would cause issues upon saving the changes to Analysis Services / Power BI. You should modify the DAX of the calculated table instead.$$$Mirrored Azure Databricks catalogs are now also shown in the Table Import Wizard UI; when choosing the Fabric Mirrored Database option.$$$Fixed an issue where opening a model created with older versions of Power BI Desktop would cause a The given key Extended Properties was not present in the dictionary error.$$$Fixed a bug that prevented forward references in DAX script object properties. I.e. you no longer get an error if the FormatString property of a measure references a measure defined later in the script.

Refer - https://tabulareditor.com/https://docs.tabulareditor.com/te3/other/release-notes/3_23_0.html?tabs=downloads$$$$$$New in 3.23.0$$$Check out our release blog to get a brief overview of the most important updates in this release.$$$$$$The Table Import Wizard now supports Fabric SQL Databases and Fabric Mirrored Databases as data sources; both for Import and Direct Lake mode models; in line with the announcement in the Power BI Desktop July 2025 update.$$$Native ARM64 support.$$$Preparations for upcoming Power BI features (which we cant disclose just yet).$$$Improvements in 3.23.0$$$Main window now remembers its position & size. Can be disabled in Preferences > Tabular Editor > User Interface > Layout.$$$Messages view now copies the selected cell rather than the whole row by default; Ctrl+Shift+C can be used to copy the whole row as before. There is a new right click context menu with these (Copy Cell; Copy Row) options as well.$$$Updated 3rd party dependencies including AMO/TOM to v. 19.103.2.$$$A new word wrap option is now exposed in toolbar; menu (Edit > Word Wrap) and preferences window (Text Editors > General). Line wrap indicators can also be enabled in the preferences.$$$The C# script editors auto complete now provides more flexible search (i.e. search for partial matches and search by capital letters).$$$You can now use the Apply or Apply selection action on DAX queries containing $$$DEFINE COLUMN$$$ or $$$DEFINE TABLE$$$ statements; in addition to DEFINE MEASURE statements. This will create the corresponding calculated columns or calculated tables in the model; or update their DAX expressions if they already exist.$$$Peek definition window now lets user scroll the main DAX editor instead of swallowing mouse scroll inputs while the mouse is on it.$$$Peek definition window height is now adjusted more tightly.$$$Semantic Analyzer no longer shows Multiple column cannot be converted to a scalar value errors; when there are other; more indicative error messages.$$$Bugfixes in 3.23.0$$$Fixed a bug where you would have to enable Allow unsupported modelling operations in order to make any changes to a model in Power BI Desktop; even though modelling operations were supported.$$$Fixed a bug where main window exceeds screen dimensions depending on resolution and DPI scaling.$$$Fixed toolbar customization settings such as Large icons; Show ScreenTips on toolbars etc. not persisting after restarting TE3.$$$Fixed a visual glitch where TOM Explorers Perspective and Language drop-down controls have duplicate buttons.$$$Fixed a bunch of issues with Peek definiton feature:$$$Peek definition is closed on undo/redo operations$$$Peek definition is invisible when used on the last line of DAX editor$$$Peek definition turns invisible when the line ending of the peeked reference is deleted$$$Peek definition is also closed when trying to instead close auto-complete popup with ESC$$$Peek definition is also closed when trying to instead clear rectangular-selection with ESC$$$When a new line is added to the left of peeked reference; peek definition turns invisible and empty padding space incorrectly appears above the peeked reference$$$Fix empty padding space appearing under the wrong line if the caret is on a different line than the peeked reference when the peek definition is triggered$$$Calltips in the C# code editor are now sized correctly; ensuring that all of the calltip text is visible.$$$Fixed a bug where Fabric Warehouses were not correctly listed in the Fabric connection dialog (instead they were shown as type Unknown).$$$DAX autocomplete should no longer suggest DAY for the <Interval> parameter of the $$$PARALLELPERIOD$$$ function; as this is not a valid value for that parameter.$$$Calltips will now update correctly when swapping between different syntax alternatives using the up/down arrows.$$$Fixed a bug where code actions did not update correctly when switching between objects.$$$Fix line numbers in code editors getting cut off when zoom

Refer - https://tabulareditor.com/https://docs.tabulareditor.com/te3/other/release-notes/3_23_0.html?tabs=downloads$$$$$$New in 3.23.0$$$Check out our release blog to get a brief overview of the most important updates in this release.$$$$$$The Table Import Wizard now supports Fabric SQL Databases and Fabric Mirrored Databases as data sources; both for Import and Direct Lake mode models; in line with the announcement in the Power BI Desktop July 2025 update.$$$Native ARM64 support.$$$Preparations for upcoming Power BI features (which we cant disclose just yet).$$$Improvements in 3.23.0$$$Main window now remembers its position & size. Can be disabled in Preferences > Tabular Editor > User Interface > Layout.$$$Messages view now copies the selected cell rather than the whole row by default; Ctrl+Shift+C can be used to copy the whole row as before. There is a new right click context menu with these (Copy Cell; Copy Row) options as well.$$$Updated 3rd party dependencies including AMO/TOM to v. 19.103.2.$$$A new word wrap option is now exposed in toolbar; menu (Edit > Word Wrap) and preferences window (Text Editors > General). Line wrap indicators can also be enabled in the preferences.$$$The C# script editors auto complete now provides more flexible search (i.e. search for partial matches and search by capital letters).$$$You can now use the Apply or Apply selection action on DAX queries containing $$$DEFINE COLUMN$$$ or $$$DEFINE TABLE$$$ statements; in addition to DEFINE MEASURE statements. This will create the corresponding calculated columns or calculated tables in the model; or update their DAX expressions if they already exist.$$$Peek definition window now lets user scroll the main DAX editor instead of swallowing mouse scroll inputs while the mouse is on it.$$$Peek definition window height is now adjusted more tightly.$$$Semantic Analyzer no longer shows Multiple column cannot be converted to a scalar value errors; when there are other; more indicative error messages.$$$Bugfixes in 3.23.0$$$Fixed a bug where you would have to enable Allow unsupported modelling operations in order to make any changes to a model in Power BI Desktop; even though modelling operations were supported.$$$Fixed a bug where main window exceeds screen dimensions depending on resolution and DPI scaling.$$$Fixed toolbar customization settings such as Large icons; Show ScreenTips on toolbars etc. not persisting after restarting TE3.$$$Fixed a visual glitch where TOM Explorers Perspective and Language drop-down controls have duplicate buttons.$$$Fixed a bunch of issues with Peek definiton feature:$$$Peek definition is closed on undo/redo operations$$$Peek definition is invisible when used on the last line of DAX editor$$$Peek definition turns invisible when the line ending of the peeked reference is deleted$$$Peek definition is also closed when trying to instead close auto-complete popup with ESC$$$Peek definition is also closed when trying to instead clear rectangular-selection with ESC$$$When a new line is added to the left of peeked reference; peek definition turns invisible and empty padding space incorrectly appears above the peeked reference$$$Fix empty padding space appearing under the wrong line if the caret is on a different line than the peeked reference when the peek definition is triggered$$$Calltips in the C# code editor are now sized correctly; ensuring that all of the calltip text is visible.$$$Fixed a bug where Fabric Warehouses were not correctly listed in the Fabric connection dialog (instead they were shown as type Unknown).$$$DAX autocomplete should no longer suggest DAY for the <Interval> parameter of the $$$PARALLELPERIOD$$$ function; as this is not a valid value for that parameter.$$$Calltips will now update correctly when swapping between different syntax alternatives using the up/down arrows.$$$Fixed a bug where code actions did not update correctly when switching between objects.$$$Fix line numbers in code editors getting cut off when zoom

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.

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