Tabular Editor 3: baixar versions anteriors

Bugfixes in 3.27.1.1
- Fixed an issue where Tabular Editor 3 closed unexpectedly when you selected an object with an expression, on machines whose security configuration prevented the code editor component from starting. This issue was a regression since 3.27.0. Administrators can turn the signature check of the code editor libraries back on with the RequireNativeLibrarySignatureVerification policy. See Policies.
- Fixed an issue where the details of an unexpected error, in the error report dialog and in errorreport.txt, listed the same error several times and left out the underlying error. Each error in the chain is now listed once, down to the underlying cause.

Improvements in 3.27.1.0
- The AI Assistant and agents connected through the MCP server now receive the DAX errors in your model and in open documents:
- it now lists the errors, warnings and Analysis Services messages that the Messages view shows
- the errors and warnings of the active document (DAX query, DAX script, C# script or Pivot Grid) are added to the assistant's context
- after a C# script runs, the result lists the errors the script introduced or resolved
Error text returned by Analysis Services can contain model data, and it's shared only when the Model data permission is set to Read.
- DAX Query and Pivot Grid documents now stay open when you open a different model, and they connect to the new model. A DAX query keeps its text and unsaved changes. A Pivot Grid keeps its layout and drops fields the new model doesn't have. Turn this off with Keep DAX Queries open when a different model is opened and Keep Pivot Grids open when a different model is opened under Tools > Preferences > Data Browsing. See DAX queries: switching models and Pivot Grids: switching models.
- Model > Deploy... has a new Deploy Linguistic Metadata (Q&A Synonyms, AI Instructions and AI Data Schema) option, selected by default. Clear it to keep the AI instructions, AI data schema and Q&A synonyms already set up on the destination semantic model. See Deployment options.
- Right-click a server in the Server list of File > Open > Model from DB... or the deployment wizard to Pin, Unpin or Delete it. Pinned servers stay at the top of the list and aren't removed by Clear recent servers. See Recent and pinned servers.
- The window title now starts with the model name. The Model source detail preference under Tools > Preferences > Tabular Editor > User Interface replaces Hide model source details and sets how much of the model's location the title bar, status bar, tab tooltips and recent lists show. The status bar shows the connection as <database>@<server>. See User Interface preferences and Tabular Editor 3 user interface.
- The Messages view has a Caused by column that shows the object causing a cascading error and +N dependent errors on the object that causes errors on other objects. Right-click an error to clear Show Cascading Errors or to choose Go to Root Cause. See Cascading errors and root causes.
Bugfixes in 3.27.1.0
- Fixed an issue where setting a calculation item's Ordinal to move it toward the end of its calculation group placed it one position too early.
- Fixed an issue where File > New > Model... applied the chosen name to the model only and left the database named SemanticModel.
- Fixed an issue where an invalid culture name was accepted for a model's Culture and a translation's Language property. These values are now rejected with an error such as 'en US' is an invalid culture specifier.
- Fixed an issue where comparing two models failed with Object reference not set to an instance of an object when they differed in role members, query groups or other unnamed collection elements.
- Fixed an issue where a non-standard whitespace character in a DAX expression, such as a no-break space, wasn't reported. It's now reported as an error that names the character and tells you to run Format DAX.
- Fixed issues in the Metadata Translation Editor:
- clearing a translation cell had no effect; it now removes the translation
- the Display folder cell of a table, a hierarchy level, a perspective or the model was editable and the value was discarded; these cells are now read-only
- the column header context menu offered Show Auto Filter Row, which didn't work on translation columns
- Fixed an issue where closing the Import Table Wizard while it listed tables could show an error report dialog or leave objects missing from the tree.
- Fixed an issue where cancelling the Load Semantic Model from Database dialog or the data source credentials prompt could close Tabular Editor and lose unsaved work.
- Fixed issues where Debug this value on a Pivot Grid val

Bugfixes in 3.26.3
- Fixed an issue where a failed File > Revert (for example, when the on-disk TMDL contains an unresolvable reference) could permanently disable unsaved-changes tracking for the rest of the session. Previously, subsequent edits would no longer show the dirty asterisk, and Revert or Close could silently discard unsaved changes without warning. Change tracking now remains active after a failed revert.
- On folder-serialized (TMDL) models, File > Revert no longer leaves the model showing as having unsaved changes after a successful revert. Previously the title-bar asterisk and the "Refresh metadata from source?" confirmation would persist on every subsequent revert until the model was saved.
- Fixed DAX auto-complete suggesting user-defined functions (UDFs) that are not valid in the current argument context, and omitting valid ones. UDFs are now filtered by their inferred return type: where a scalar is expected, only UDFs returning a scalar, a single-column table, or an untyped input parameter are shown; where a table is expected, only table-returning (or passthrough) UDFs are shown; and filter arguments (such as those of CALCULATE / CALCULATETABLE) now suggest UDFs, which were previously omitted entirely. UDFs whose definition contains a semantic error (for example, one that requires row context or misuses MATCHBY) are no longer offered as suggestions, as they cannot be validly invoked.
- The DAX formatter no longer replaces the = of a DAX function's default parameter value with a :. Previously, formatting a function such as (p = [m]) => 1 produced the invalid (p: [m]) => 1, because the formatter assumed any tokens after a parameter name were a : type annotation. Type annotations, default values, and the combination of both (p: INT64 = 1) are now formatted correctly.
- Fixed an issue where marking a DAX Optimizer issue as ignored had no effect after uploading a new version of an obfuscated model: the ignored issue would reappear as open. Ignored issues are now retained across versions of obfuscated models.
- Fixed an intermittent crash ("Collection was modified") that could occur in the DAX Optimizer view right after uploading a model or a new version. The view is now refreshed while the progress spinner is still shown, instead of refreshing in the background as the window was being redrawn.

Improvements in 3.26.2
- Added a Move to group right-click submenu for tables in the TOM Explorer. The submenu lists existing Table Groups, a (New...) entry that creates a new group with the selected tables and opens the name editor, and a (None) entry that removes the Table Group assignment.
- Refreshed the model presets in the AI Assistant preferences with the latest releases, so users can pick current models without typing a custom model ID. Added Anthropic's claude-fable-5 and claude-opus-4-8, and OpenAI's gpt-5.5/gpt-5.5-pro along with other current GPT-5 variants. Deprecated entries (such as the older Codex variants) were removed, and the default OpenAI model is now gpt-5.5.
- Semantic Analyzer improvements
- Added support for optional parameters with default expressions in DAX UDFs.
- The Semantic Analyzer now emits suitable warning / error messages, when an UDF is called with a parameter that doesn't match its declared type (e.g. passing a scalar value to a TABLEREF parameter, etc.)
- The semantic analyzer now reports an error when IGNORE is used anywhere other than directly as an expression argument of SUMMARIZECOLUMNS, matching engine behavior.
- The semantic analyzer now supports the new optional component and escaping parameters introduced for the NAMEOF function in Power BI Desktop April 2026. Valid component keywords are TABLE, COLUMN, MEASURE, CALENDAR, FULL, SELF, PARENT; valid escaping keywords are ESCAPED, UNESCAPED, MINIMALLYESCAPED. The return type is unchanged (scalar string). For example, EVALUATE { NAMEOF([MyMeasure], TABLE, MINIMALLYESCAPED) } returns the table name component of a fully qualified measure reference.
- Semantic Bridge improvements
- Importing a Databricks Metric View now carries the view's metadata into the semantic model.
- comment becomes the description on the model, dimensions, and measures.
- display_name becomes the user-facing Name in the TOM model, with a fallback to name if there is no display_name defined.
- Measure and dimension format translate to TOM FormatString, and the resulting column or measure DataType is inferred from the format (currency, percentage, date, etc.). Format specs without a clean TOM equivalent fall back to a sensible default and surface a warning.
- SQL-to-DAX translation is improved: row counts (COUNT(*)), MEASURE(name) references, binary operations, literals (including NULL -> BLANK()), / mapped to the blank-safe DIVIDE, and parenthesis precedence all now translate cleanly.
- Expressions outside the recognized set still fall back to the verbatim SQL with a warning.
- Translated DAX is best-effort — review and validate before deploying.
- Add support for snowflake schemas with nested joins.
- YAML deserialization accepts both fields: and dimensions: at the top level: the Databricks v1.1 spec treats them as aliases. Round-trip preserves whichever keyword the source YAML used. Views created in TE3 (no source YAML) default to dimensions: for v1.1 and earlier: the fields: alias was introduced after the v1.1 spec was published, so we stay compatible with tooling that targets the original 1.1 spec. A deserialization warning surfaces when a v1.1+ view uses dimensions: (the spec marks fields: as preferred at v1.1+), and a symmetric warning surfaces when a pre-v1.1 view uses fields:.
- The C# scripting surface renames Dimension to Field (view.Fields, view.AddField, Dimension -> Field, MakeValidationRuleForDimension -> MakeValidationRuleForField, ctx.DimensionNames -> ctx.FieldNames).
- The legacy names remain as obsolete forwarders that continue to compile and run with deprecation warnings, so existing scripts and stored paths like Model.Dimensions["x"] still work.
- Window measures (including the v1.1 offset: field) round-trip in YAML deserialization and serialization. We don't yet translate features the spec marks as experimental; the YAML round-trip preserves them so they're not lost.
- Joins now support two new properties in the updated v1.1 spec:
- rely: map

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 weren't 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 Assistant's 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

New in 3.26.0
Check out our release blog to get a brief overview of the most important updates in this release.
- Our AI Assistant is now in public preview. Click the link to learn more.
Improvements in 3.26.0
- Databricks support improvements
- We now support the new Databricks ODBC Driver in addition to the legacy Simba Spark ODBC Driver.
- Added OAuth (OIDC) authentication support for Databricks connections, enabling browser-based sign-in for both Azure and multi-cloud Databricks workspaces.
- The Azure AD authentication option is now hidden for multi-cloud (non-Azure) Databricks connections, since it requires the Azure Databricks resource ID.
- Added advanced connection options for Databricks: Query Tags, Implementation, Metric View BI Compatibility Mode, and Enable Automatic Proxy Discovery.
- Semantic Bridge now supports v1.1 Metric Views metadata
- DAX support improvements
- Add support for table references in NAMEOF function.
- Add support for TABLEOF function.
- DATEADD now gives better error messages when its optional parameters are used without a calendar reference.
- Add support for the new optional EndBehavior parameter of DATESINPERIOD function.
- Add auto-complete support for MEASUREREF, COLUMNREF, TABLEREF and CALENDARREF as UDF parameter type hints.
- C# script improvements
- We now have a Run script with preview button, which will display a dialog showing all the changes made to the model by the script, after the script executes successfully. This way, you have a chance to review the changes and optionally revert the script.
- Added complete singular and plural accessor support in C# scripts for all object types. You can now use Selected.Role to get a single role, Selected.KPIs to get all selected KPIs, and similar patterns for calculated table columns, folders, relationships, table permissions, and generic objects, making scripts more intuitive and easier to write. Learn more.
- Improved the Semantic Bridge C# scripting interface to be more aligned with TOMWrapper for programmatic manipulation of Metric Views
- Other improvements
- Added a toolbar toggle button in the TOM Explorer to show or hide table groups, making it easier to control how tables are organized in the tree view without navigating through the preferences dialog.
- Update NuGet packages including Microsoft.AnalysisServices to 19.113.2 and Scintilla.NET to 6.1.2.
- When opening a model with a workspace database, Tabular Editor now detects changes to incremental refresh Source Expression or Polling Expression and prompts before overwriting workspace partitions. This prevents accidental loss of expression changes when collaborating via Git.
- Added new Built in BPA rule to verify that UDFs uses seperators to ensure UDFs won't break if Microsoft creates a new DAX function.
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

New in 3.25.0
Check out our release blog to get a brief overview of the most important updates in this release.
- Tabular Editor is now available in Chinese and Spanish (Preview). All translations have initially been done with AI, with human proofreading. Japanese, German and French are also available as experimental languages, which are not yet reviewed.
- Tabular Editor now includes a set of built-in Best Practice Analyzer (BPA) rules covering key best practices across formatting, metadata, model layout, DAX expressions, and translations.
- Tabular Editor now includes the Semantic Bridge feature, which lets you easily create semantic models from Databricks Metric Views (Tabular Editor 3 Enterprise Edition only).
- Added an option to save semantic models with supporting files for Fabric. When enabled, Tabular Editor can create and update the .platform and definition.pbism files alongside the model metadata to match Fabric repository structure.
- This release also adds a new Calendar Editor, that makes it easy to manage the calendar objects used for Calendar-based time intelligence.
- Last but not least, we've added an Advanced Refresh dialog, through which you can configure advanced refresh options like parallelism and effective date for incremental refresh. You can also specify refresh override profiles (Tabular Editor 3 Business Edition and Enterprise Edition only).
Improvements in 3.25.0
- Added support for setting the CustomData property of the connection string directly from the Impersonation dialog.
- DAX Package Manager View now downloads and shows DaxLib package icons.
- DAX Package Manager now caches package metadata which allows it to show package info without needing internet connection.
- We've updated the AS client library to the latest version 19.108.5. This update lets you control the new UnicodeCharacterBehavior property on the Database object.
- Added Power BI specific Column Data Categories Longitude, Latitude and Place.
- We now show an error message if you attempt to set the Compatibility Level of a model to a value that is not supported by the server. This is to prevent unexpected errors later on when saving changes to the model. If you need to set an unsupported Compatibility Level for migration purposes, save your model metadata to disk (in .bim or TMDL format), then open the metadata with no workspace database attached.
- User Options (.tmuo) files, are now also saved when you open a model directly from a server / XMLA-endpoint. The files are stored in your %LocalAppData%\TabularEditor3\UserOptions folder.
- Added a "Refresh full (ignore policy)" option to the data refresh context menu, so that you can easily refresh data into existing partitions, without triggering partition add/delete/merge operations on the server, when a table is governed by incremental refresh policy.
- Reorganized the options in the data refresh context menu, to bring the most commonly used options to the top.
- Added Start time to refresh pane making it possible to sort the refresh after when they started e.g. seeing the latest refresh first.
- Added a search pane to the Preferences dialog to quickly search for individual preferences.
- Added "User Defined Functions" and "Calendars" to Best Practice Rule editor list.
- Added a UsedInCalendars property to columns, making it easy to check inside a C# script, if a column is used in any calendar objects.
- "File > Close" menu action is renamed to "Close Document" and is now capable of closing any panel or document in the main document area. Ctrl + W is assigned as the default shortcut.
- Added Semantic Analyzer support for the new ENDALIGNED keyword of the DATEADD parameter. More information.
- When saving to a model.bim or TMDL folder structure with the Ignore incremental refresh partitions serialization option enabled, we now add a dummy partition to replace the PolicyRange partitions. This ensures that the model can still be loaded in Power BI Desktop, as no tables are saved with

New in 3.25.0
Check out our release blog to get a brief overview of the most important updates in this release.
- Tabular Editor is now available in Chinese and Spanish (Preview). All translations have initially been done with AI, with human proofreading. Japanese, German and French are also available as experimental languages, which are not yet reviewed.
- Tabular Editor now includes a set of built-in Best Practice Analyzer (BPA) rules covering key best practices across formatting, metadata, model layout, DAX expressions, and translations.
- Tabular Editor now includes the Semantic Bridge feature, which lets you easily create semantic models from Databricks Metric Views (Tabular Editor 3 Enterprise Edition only).
- Added an option to save semantic models with supporting files for Fabric. When enabled, Tabular Editor can create and update the .platform and definition.pbism files alongside the model metadata to match Fabric repository structure.
- This release also adds a new Calendar Editor, that makes it easy to manage the calendar objects used for Calendar-based time intelligence.
- Last but not least, we've added an Advanced Refresh dialog, through which you can configure advanced refresh options like parallelism and effective date for incremental refresh. You can also specify refresh override profiles (Tabular Editor 3 Business Edition and Enterprise Edition only).
Improvements in 3.25.0
- Added support for setting the CustomData property of the connection string directly from the Impersonation dialog.
- DAX Package Manager View now downloads and shows DaxLib package icons.
- DAX Package Manager now caches package metadata which allows it to show package info without needing internet connection.
- We've updated the AS client library to the latest version 19.108.5. This update lets you control the new UnicodeCharacterBehavior property on the Database object.
- Added Power BI specific Column Data Categories Longitude, Latitude and Place.
- We now show an error message if you attempt to set the Compatibility Level of a model to a value that is not supported by the server. This is to prevent unexpected errors later on when saving changes to the model. If you need to set an unsupported Compatibility Level for migration purposes, save your model metadata to disk (in .bim or TMDL format), then open the metadata with no workspace database attached.
- User Options (.tmuo) files, are now also saved when you open a model directly from a server / XMLA-endpoint. The files are stored in your %LocalAppData%\TabularEditor3\UserOptions folder.
- Added a "Refresh full (ignore policy)" option to the data refresh context menu, so that you can easily refresh data into existing partitions, without triggering partition add/delete/merge operations on the server, when a table is governed by incremental refresh policy.
- Reorganized the options in the data refresh context menu, to bring the most commonly used options to the top.
- Added Start time to refresh pane making it possible to sort the refresh after when they started e.g. seeing the latest refresh first.
- Added a search pane to the Preferences dialog to quickly search for individual preferences.
- Added "User Defined Functions" and "Calendars" to Best Practice Rule editor list.
- Added a UsedInCalendars property to columns, making it easy to check inside a C# script, if a column is used in any calendar objects.
- "File > Close" menu action is renamed to "Close Document" and is now capable of closing any panel or document in the main document area. Ctrl + W is assigned as the default shortcut.
- Added Semantic Analyzer support for the new ENDALIGNED keyword of the DATEADD parameter. More information.
- When saving to a model.bim or TMDL folder structure with the Ignore incremental refresh partitions serialization option enabled, we now add a dummy partition to replace the PolicyRange partitions. This ensures that the model can still be loaded in Power BI Desktop, as no tables are saved with

New in 3.25.0
Check out our release blog to get a brief overview of the most important updates in this release.
- Tabular Editor is now available in Chinese and Spanish (Preview). All translations have initially been done with AI, with human proofreading. Japanese, German and French are also available as experimental languages, which are not yet reviewed.
- Tabular Editor now includes a set of built-in Best Practice Analyzer (BPA) rules covering key best practices across formatting, metadata, model layout, DAX expressions, and translations.
- Tabular Editor now includes the Semantic Bridge feature, which lets you easily create semantic models from Databricks Metric Views (Tabular Editor 3 Enterprise Edition only).
- Added an option to save semantic models with supporting files for Fabric. When enabled, Tabular Editor can create and update the .platform and definition.pbism files alongside the model metadata to match Fabric repository structure.
- This release also adds a new Calendar Editor, that makes it easy to manage the calendar objects used for Calendar-based time intelligence.
- Last but not least, we've added an Advanced Refresh dialog, through which you can configure advanced refresh options like parallelism and effective date for incremental refresh. You can also specify refresh override profiles (Tabular Editor 3 Business Edition and Enterprise Edition only).
Improvements in 3.25.0
- Added support for setting the CustomData property of the connection string directly from the Impersonation dialog.
- DAX Package Manager View now downloads and shows DaxLib package icons.
- DAX Package Manager now caches package metadata which allows it to show package info without needing internet connection.
- We've updated the AS client library to the latest version 19.108.5. This update lets you control the new UnicodeCharacterBehavior property on the Database object.
- Added Power BI specific Column Data Categories Longitude, Latitude and Place.
- We now show an error message if you attempt to set the Compatibility Level of a model to a value that is not supported by the server. This is to prevent unexpected errors later on when saving changes to the model. If you need to set an unsupported Compatibility Level for migration purposes, save your model metadata to disk (in .bim or TMDL format), then open the metadata with no workspace database attached.
- User Options (.tmuo) files, are now also saved when you open a model directly from a server / XMLA-endpoint. The files are stored in your %LocalAppData%\TabularEditor3\UserOptions folder.
- Added a "Refresh full (ignore policy)" option to the data refresh context menu, so that you can easily refresh data into existing partitions, without triggering partition add/delete/merge operations on the server, when a table is governed by incremental refresh policy.
- Reorganized the options in the data refresh context menu, to bring the most commonly used options to the top.
- Added Start time to refresh pane making it possible to sort the refresh after when they started e.g. seeing the latest refresh first.
- Added a search pane to the Preferences dialog to quickly search for individual preferences.
- Added "User Defined Functions" and "Calendars" to Best Practice Rule editor list.
- Added a UsedInCalendars property to columns, making it easy to check inside a C# script, if a column is used in any calendar objects.
- "File > Close" menu action is renamed to "Close Document" and is now capable of closing any panel or document in the main document area. Ctrl + W is assigned as the default shortcut.
- Added Semantic Analyzer support for the new ENDALIGNED keyword of the DATEADD parameter. More information.
- When saving to a model.bim or TMDL folder structure with the Ignore incremental refresh partitions serialization option enabled, we now add a dummy partition to replace the PolicyRange partitions. This ensures that the model can still be loaded in Power BI Desktop, as no tables are saved with

New in 3.25.0
Check out our release blog to get a brief overview of the most important updates in this release.
- Tabular Editor is now available in Chinese and Spanish (Preview). All translations have initially been done with AI, with human proofreading. Japanese, German and French are also available as experimental languages, which are not yet reviewed.
- Tabular Editor now includes a set of built-in Best Practice Analyzer (BPA) rules covering key best practices across formatting, metadata, model layout, DAX expressions, and translations.
- Tabular Editor now includes the Semantic Bridge feature, which lets you easily create semantic models from Databricks Metric Views (Tabular Editor 3 Enterprise Edition only).
- Added an option to save semantic models with supporting files for Fabric. When enabled, Tabular Editor can create and update the .platform and definition.pbism files alongside the model metadata to match Fabric repository structure.
- This release also adds a new Calendar Editor, that makes it easy to manage the calendar objects used for Calendar-based time intelligence.
- Last but not least, we've added an Advanced Refresh dialog, through which you can configure advanced refresh options like parallelism and effective date for incremental refresh. You can also specify refresh override profiles (Tabular Editor 3 Business Edition and Enterprise Edition only).

Improvements in 3.25.0
- Added support for setting the CustomData property of the connection string directly from the Impersonation dialog.
- DAX Package Manager View now downloads and shows DaxLib package icons.
- DAX Package Manager now caches package metadata which allows it to show package info without needing internet connection.
- We've updated the AS client library to the latest version 19.108.5. This update lets you control the new UnicodeCharacterBehavior property on the Database object.
- Added Power BI specific Column Data Categories Longitude, Latitude and Place.
- We now show an error message if you attempt to set the Compatibility Level of a model to a value that is not supported by the server. This is to prevent unexpected errors later on when saving changes to the model. If you need to set an unsupported Compatibility Level for migration purposes, save your model metadata to disk (in .bim or TMDL format), then open the metadata with no workspace database attached.
- User Options (.tmuo) files, are now also saved when you open a model directly from a server / XMLA-endpoint. The files are stored in your %LocalAppData%\TabularEditor3\UserOptions folder.
- Added a "Refresh full (ignore policy)" option to the data refresh context menu, so that you can easily refresh data into existing partitions, without triggering partition add/delete/merge operations on the server, when a table is governed by incremental refresh policy.
- Reorganized the options in the data refresh context menu, to bring the most commonly used options to the top.
- Added Start time to refresh pane making it possible to sort the refresh after when they started e.g. seeing the latest refresh first.
- Added a search pane to the Preferences dialog to quickly search for individual preferences.
- Added "User Defined Functions" and "Calendars" to Best Practice Rule editor list.
- Added a UsedInCalendars property to columns, making it easy to check inside a C# script, if a column is used in any calendar objects.
- "File > Close" menu action is renamed to "Close Document" and is now capable of closing any panel or document in the main document area. Ctrl + W is assigned as the default shortcut.
- Added Semantic Analyzer support for the new ENDALIGNED keyword of the DATEADD parameter. More information.
- When saving to a model.bim or TMDL folder structure with the Ignore incremental refresh partitions serialization option enabled, we now add a dummy partition to replace the PolicyRange partitions. This ensures that the model can still be loaded in Power BI Desktop, as no tables are saved wit

New in 3.24
Check out our release blog to get a brief overview of the most important updates in this release.
Also check out the release notes for version 3.24.0 to see all new features and improvements added in the previous major release.
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.1
- Added Semantic Analyzer support for new data type keywords LOGICAL, INT64, DECIMAL, and TEXT (which are all aliases of existing keywords) that can be used as arguments of functions such as CONVERT and DATATABLE.
- Added Semantic Analyzer support for new functions, ISINTEGER, ISCURRENCY, and visual calculation function LOOKUPWITHTOTALS.
- Added "Manage DAX Packages..." menu option when right-clicking on the Model or Functions node in the TOM Explorer.
Bugfixes in 3.24.1
- Fixed a bug that caused an unhandled exception when launching Tabular Editor 3 on a monitor with a low pixel resolution
- Fixed a bug that prevented opening a model from a PBIP folder structure, when using the File > Open > Model from File... menu option, see #1507.
- Fixed DPI scaling issues related to the DAX Package Manager view.
- Fixed Semantic Analyzer bug where visual calculation functions FIRST and LAST were not recognized.
- Fixed Semantic Analyzer bug that would show a false warning when calling an UDF as the first argument of CALCULATE, see #1509.
- DAX Package Manager no longer shows a warning because of differences in line endings in the DAX expression (PBI Desktop may change \n to \r\n when saving a model).
- Fix ordering of UDFs among namespaces in the TOM Explorer

New in 3.24.1
Check out our release blog to get a brief overview of the most important updates in this release.
Also check out the release notes for version 3.24.0 to see all new features and improvements added in the previous major release.
Improvements in 3.24.1
- Added Semantic Analyzer support for new data type keywords LOGICAL, INT64, DECIMAL, and TEXT (which are all aliases of existing keywords) that can be used as arguments of functions such as CONVERT and DATATABLE.
- Added Semantic Analyzer support for new functions, ISINTEGER, ISCURRENCY, and visual calculation function LOOKUPWITHTOTALS.
- Added "Manage DAX Packages..." menu option when right-clicking on the Model or Functions node in the TOM Explorer.
Bugfixes in 3.24.1
- Fixed a bug that caused an unhandled exception when launching Tabular Editor 3 on a monitor with a low pixel resolution
- Fixed a bug that prevented opening a model from a PBIP folder structure, when using the File > Open > Model from File... menu option, see #1507.
- Fixed DPI scaling issues related to the DAX Package Manager view.
- Fixed Semantic Analyzer bug where visual calculation functions FIRST and LAST were not recognized.
- Fixed Semantic Analyzer bug that would show a false warning when calling an UDF as the first argument of CALCULATE, see #1509.
- DAX Package Manager no longer shows a warning because of differences in line endings in the DAX expression (PBI Desktop may change \n to \r\n when saving a model).
- Fix ordering of UDFs among namespaces in the TOM Explorer

New in 3.24.0
Check out our release blog to get a brief overview of the most important updates in this release.
DAX Package Manager
Find and install DAX packages for Power BI with a single click! This new feature integrates with https://daxlib.org, which serves as an open gallery of community-authored reusable packages of DAX code (in the form of DAX User-Defined Functions). Dozens of packages and hundreds of UDFs are already available, with more coming every day. Learn more.
Organize UDFs by namespaces
The concept of "namespace" doesn't exist in DAX, yet the recommendation is to name UDFs in such a way that ambiguities are avoided and that the origin of the UDF is clear. For example DaxLib.Convert.CelsiusToFahrenheit (using '.' as namespace separators). In this update, we show UDFs hierarchically by their namespace in the TOM Explorer, making it easier to manage and navigate multiple such UDFs. There's a toggle button just above the TOM Explorer, if you prefer to see a flat list of UDFs instead.
This feature also adds a "Namespace" property to UDFs, allowing you to customize the namespace of each UDF individually, without changing the name. Think of it as Display Folders for UDFs. This is useful, for example if you want to batch rename (F2) multiple UDFs to get rid of the namespaces in their names, but you still want to keep them nicely organized in the TOM Explorer. Learn more.
Note
This organizational feature in Tabular Editor doesn't affect DAX code - function calls remain the same regardless of namespace organization.
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 insi

New in 3.23.0
Check out our release blog to get a brief overview of the most important updates in this release.
- Tabular Editor 3 now supports DAX User-Defined Functions (UDFs). This is a big, important feature, and we can't do it justice in a few bullet points. Please check out the dedicated documentation section to learn more.
- As if one big feature wasn't enough, we also added support for Calendars in this release, including DAX parser and editor support for 8 new DAX functions related to week-based time intelligence. Again, please see the dedicated documentation section to learn more.
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.

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 can't 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 editor's 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 Explorer's 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 zoomed in.

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 over OneLake and Direct Lake over 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 over 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.
Note
We no longer configure Direct Lake models to use a case sensitive collation. If you plan to use Direct Lake over SQL with a Fabric Warehouse that uses a case sensitive collation, you must manually fill out the Collation property of your semantic model before adding any tables or other objects.
Improvements in 3.22.0
- When saving a model as a single file, the Save file dialog now suggests "model.bim" as the default file name.
- Updated various dependencies to their latest versions, including AMO/TOM to 19.98.0.3. This update fixes longstanding authentication issues with Work or School accounts and repeated sign in promts.
- DAX query editor support for the MPARAMETER keyword, see #1467.
- Our DAX editors now support word based auto complete search terms. In other words, if you type sales ytd in the editor, the auto complete will now suggest measures such as [Sales Margin YTD], [Sales Revenue YTD], etc.
- With the June 2025 update of Power BI Desktop, external tools can now perform any write operation on the semantic model. As such, we no longer restrict the modeling operations available in Tabular Editor, when connecting to a model in this or newer versions of Power BI Desktop.
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.
Bugfixes in 3.22.0
- Added exception handling when encountering IOException's during save-to-folder operations (where we sometimes need to delete folders in the folder structure, which can be blocked by file system locks placed by version control systems).
- Fixed a bug where certain keyboard shortcuts (both default and customized) didn't work when the "What's new" page was focused.
- When assigning a custom keyboard shortcut that is already assigned to another command, we now show a warning message and remove the shortcut from the other command, to avoid ambiguity.
- Fixed a bug where the Semantic Analyzer showed a false error message when using unqualified column references in a DAX window function. See #1460.
- Fixed a bug that could sometimes cause the Data Refresh view to freeze, requiring an app restart to resolve. See #1461.
- Fixed several smaller DAX editor issues related to auto complete, auto formatting, and syntax highlighting of keywords.
- Query Group names (i.e. "display folders" for Shared M expressions and M partitions) can now be modified. Also, if pasting an object with a query group into a model that doesn't contain said query group, it will be created automatically, so as to avoid the error message on subsequent Save / Deployment of the model.
- Fixed a bug where it was sometimes not possible to Undo previ

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.
Note
We no longer configure Direct Lake models to use a case sensitive collation. If you plan to use Direct Lake on SQL with a Fabric Warehouse that uses a case sensitive collation, you must manually fill out the Collation property of your semantic model before adding any tables or other objects.
For more information, view our Direct Lake Guidance article.
Improvements in 3.22.0
- When saving a model as a single file, the Save file dialog now suggests "model.bim" as the default file name.
- Updated various dependencies to their latest versions, including AMO/TOM to 19.98.0.3. This update fixes longstanding authentication issues with Work or School accounts and repeated sign in promts.
- Changed the default Compatibility Level for new Power BI / Fabric semantic models to 1609, which allows you to control how Selection Expressions on your Calculation Groups behave by default, through the Model SelectionExpressionBehavior property.
- DAX query editor support for the MPARAMETER keyword, see #1467.
- Our DAX editors now support word based auto complete search terms. In other words, if you type sales ytd in the editor, the auto complete will now suggest measures such as [Sales Margin YTD], [Sales Revenue YTD], etc.
- With the June 2025 update of Power BI Desktop, external tools can now perform any write operation on the semantic model. As such, we no longer restrict the modeling operations available in Tabular Editor, when connecting to a model in this or newer versions of Power BI Desktop.
Bugfixes in 3.22.0
- Added exception handling when encountering IOException's during save-to-folder operations (where we sometimes need to delete folders in the folder structure, which can be blocked by file system locks placed by version control systems).
- Fixed a bug where certain keyboard shortcuts (both default and customized) didn't work when the "What's new" page was focused.
- When assigning a custom keyboard shortcut that is already assigned to another command, we now show a warning message and remove the shortcut from the other command, to avoid ambiguity.
- Fixed a bug where the Semantic Analyzer showed a false error message when using unqualified column references in a DAX window function. See #1460.
- Fixed a bug that could sometimes cause the Data Refresh view to freeze, requiring an app restart to resolve. See #1461.
- Fixed several smaller DAX editor issues related to auto complete, auto formatting, and syntax highlighting of keywords.
- Query Group names (i.e. "display folders" for Shared M expressions and M partitions) can now be modified. Also, if pasting an object with a query group into a model that doesn't contain said query group, it will be created automatically, s

New in 3.21.0
Check out our release blog to get a brief overview of the most important updates in this release.

Improvements in 3.21.0
- We've 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. You'll 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 DEFINEing 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 didn't 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 3's 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 re