The auto-complete popup now automatically adjusts its width to fit the widest item inside of it.When cloning objects, we now add the suffix "-Copy" instead of " Copy", to reduce the risk of leaving trailing blanks in object names, see #940.We've also published a blog post on DirectLake, if you want to learn more. Tabular Editor utilises the SQL endpoint of your Fabric Lakehouse to obtain the table schemas. Moreover, you can update the schema of existing tables the usual way. Tabular Editor now supports adding tables to DirectLake datasets through the Import Table Wizard.Fixed a bug that caused a crash whenever the user attempted to type a DAX expression in the DAX Debugger's Watch Expression window.Ĭheck out our release blog to get an overview of the most important updates in this release.Starting from 3.3.1, the Tabular Editor 3 installer will download and install these prerequisites, if they are missing. NET 6.0 Runtime for Desktop before you can launch Tabular Editor 3.3.0 (or newer). Download Tabular Editor 3.10.1 (32 bit).Download Tabular Editor 3.10.1 (64 bit) (recommended).*=Only while connected to an instance of Analysis Services or Power BI Record C# scripts and save as macros (formerly known as "Custom Actions").Create DAX scripts that allow you to edit multiple measures or other calculated objects in a single document.Update Table Schemas on both Provider and Structured Data Sources (yes, even for M queries!).*Preview table data with infinite scrolling, create PivotGrids or write DAX queries to browse the model or test calculation logic.*Workspace mode, allowing you to save your changes to disk and synchronise model metadata to Analysis Services simultaneously.New powerful DAX code editor with auto-complete, syntax checking, code folding and much, much more.Fully customizable IDE, with multi-monitor, Hi-DPI support and themes.Tabular Editor 3 major features overview: Also, make sure to check our onboarding guide. Watch this video to get an idea of the new features in Tabular Editor 3. Fixed numerous issues with the DAX debugger.Fixed a bug, where running a DAX query with no whitespace between EVALUATE and the following expression would cause an error.In this case, the deployment wizard UI did not allow the user to skip partition deployment of this table which would cause an invalid TMSL to be generated generated (one with no partitions for the table in question).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |