Tabular Editor 3 3.27.1.1

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... …

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. …