diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml index e3e0aed0..ee38109e 100644 --- a/.github/workflows/deploy.yml +++ b/.github/workflows/deploy.yml @@ -19,7 +19,7 @@ jobs: with: submodules: true - name: Build Documentation - uses: nikeee/docfx-action@v1.0.0 + uses: nunit/docfx-action@v3.0.0 with: args: docfx.json - name: Build And Deploy diff --git a/common/CSharpScripts/Beginner/script-create-field-parameter.md b/common/CSharpScripts/Beginner/script-create-field-parameter.md new file mode 100644 index 00000000..f3bc4c50 --- /dev/null +++ b/common/CSharpScripts/Beginner/script-create-field-parameter.md @@ -0,0 +1,68 @@ +--- +uid: create-field-parameter +title: Create Field Parameter +author: Daniel Otykier +updated: 2024-01-27 +applies_to: + versions: + - version: 2.x + - version: 3.x +--- +# Create Field Parameters in + +## Script Purpose +If you want to create field parameters in a Power BI model using Tabular Editor or in a Direct Lake model. + +> [!TIP] +> Want to see the script in action, check out this [Guy in a Cube video](https://www.youtube.com/watch?v=Cg6zRhwF-Ro) where Patrick LeBlanc explains how to use it step by step. + + +## Script + +### Select Columns or Measures to create a field parameter table +```csharp +// Before running the script, select the measures or columns that you +// would like to use as field parameters (hold down CTRL to select multiple +// objects). Also, you may change the name of the field parameter table +// below. NOTE: If used against Power BI Desktop, you must enable unsupported +// features under File > Preferences (TE2) or Tools > Preferences (TE3). +var name = "Parameter"; + +if(Selected.Columns.Count == 0 && Selected.Measures.Count == 0) throw new Exception("No columns or measures selected!"); + +// Construct the DAX for the calculated table based on the current selection: +var objects = Selected.Columns.Any() ? Selected.Columns.Cast() : Selected.Measures; +var dax = "{\n " + string.Join(",\n ", objects.Select((c,i) => string.Format("(\"{0}\", NAMEOF('{1}'[{0}]), {2})", c.Name, c.Table.Name, i))) + "\n}"; + +// Add the calculated table to the model: +var table = Model.AddCalculatedTable(name, dax); + +// In TE2 columns are not created automatically from a DAX expression, so +// we will have to add them manually: +var te2 = table.Columns.Count == 0; +var nameColumn = te2 ? table.AddCalculatedTableColumn(name, "[Value1]") : table.Columns["Value1"] as CalculatedTableColumn; +var fieldColumn = te2 ? table.AddCalculatedTableColumn(name + " Fields", "[Value2]") : table.Columns["Value2"] as CalculatedTableColumn; +var orderColumn = te2 ? table.AddCalculatedTableColumn(name + " Order", "[Value3]") : table.Columns["Value3"] as CalculatedTableColumn; + +if(!te2) { + // Rename the columns that were added automatically in TE3: + nameColumn.IsNameInferred = false; + nameColumn.Name = name; + fieldColumn.IsNameInferred = false; + fieldColumn.Name = name + " Fields"; + orderColumn.IsNameInferred = false; + orderColumn.Name = name + " Order"; +} +// Set remaining properties for field parameters to work +// See: https://twitter.com/markbdi/status/1526558841172893696 +nameColumn.SortByColumn = orderColumn; +nameColumn.GroupByColumns.Add(fieldColumn); +fieldColumn.SortByColumn = orderColumn; +fieldColumn.SetExtendedProperty("ParameterMetadata", "{\"version\":3,\"kind\":2}", ExtendedPropertyType.Json); +fieldColumn.IsHidden = true; +orderColumn.IsHidden = true; +``` +### Explanation +Before running the script the user has to select the measures or columns in the TOM Explorer they wish to have in their field parameter table. +The selected objects are then inserted into a calculated table which is then configured as a field parameter table automatically. + diff --git a/common/CSharpScripts/Beginner/script-format-numeric-measures.md b/common/CSharpScripts/Beginner/script-format-numeric-measures.md index 55455974..f87c022a 100644 --- a/common/CSharpScripts/Beginner/script-format-numeric-measures.md +++ b/common/CSharpScripts/Beginner/script-format-numeric-measures.md @@ -5,7 +5,6 @@ author: Morten Lønskov updated: 2023-11-29 applies_to: versions: - - version: 2.x - version: 3.x --- # Format Numeric Measures diff --git a/common/CSharpScripts/csharp-script-library-beginner.md b/common/CSharpScripts/csharp-script-library-beginner.md index b7ad0f2f..55ae95e8 100644 --- a/common/CSharpScripts/csharp-script-library-beginner.md +++ b/common/CSharpScripts/csharp-script-library-beginner.md @@ -19,7 +19,14 @@ These are more basic scripts that are easy to understand or modify. They have a | --- | --- | --- | | [Count Table Rows](Beginner/script-count-rows.md) | Evaluates a COUNTROWS ( 'Table' ) of a selected table. | When you want to check how many rows are in a table, or if it's been loaded. | | [Count Model Objects](Beginner/script-count-things.md) | Counts all the different objects by type in a model. | When you need an overview of the model contents or want to count objects by type. | -| [Create Sum Measures from Columns](Beginner/create-sum-measures-from-columns.md) | Create SUM ( 'Table'[Column] ) measures from any selected column. | When you have many columns in a new table / model and must make many measures at once. | +| [Create Sum Measures from Columns](Beginner/script-create-sum-measures-from-columns.md) | Create SUM ( 'Table'[Column] ) measures from any selected column. | When you have many columns in a new table / model and must make many measures at once. | | [Create M Parameter](Beginner/script-create-m-parameter.md) | Create a new M Parameter in 'Shared Expressions' | When you want to create a parameter to use in other Power Query queries (M Partitions / Shared Expressions). | | [Edit Hidden Partitions](Beginner/script-edit-hidden-partitions.md) | Reveals the properties of hidden partitions in Calc. Groups & Calc. Tables | When you need to see or edit the TOM properties of these hidden partitions. | -| [Find & Replace in Selected Measures](Beginner/script-find-replace-selected-measures.md) | Searches for a substring in the DAX of selected measures, replacing with another substring. | When you need to quickly find/replace values in multiple DAX measures (i.e. `CALCULATE` filter or broken object references). | \ No newline at end of file +| [Find & Replace in Selected Measures](Beginner/script-find-replace-selected-measures.md) | Searches for a substring in the DAX of selected measures, replacing with another substring. | When you need to quickly find/replace values in multiple DAX measures (i.e. `CALCULATE` filter or broken object references). | +| [Create Measure Table](Beginner/script-create-measure-table.md) | Create a measure table | When you want to create an empty table to use as an organizing measure table| +| [Create Table Groups](Beginner/script-create-table-groups.md) | Organize the model into Table Groups | When you want to have an automatic organization of your tables using the table group feature of Tabular Editor 3 | +| [Format Numeric Measures](Beginner/script-format-numeric-measures.md) | Formats the chosen measures | When you want to quickly apply a format string to the currently selected measures | +| [Show Data Source Dependencies](Beginner/script-show-data-source-dependencies.md) | Shows dependencies for data sources | For explicit (legacy) data sources it can be hard to know exactly where they are used. This script shows you which partition reference the chosen data source | +| [Create Field Parameters](Beginner/script-create-field-parameter.md) | Quickly create a field parameter table | Choose the objects that should be in the field parameter and the script will take care of the rest | + + diff --git a/common/Datasets/direct-lake-dataset.md b/common/Datasets/direct-lake-dataset.md index 769fa5c8..111cecbf 100644 --- a/common/Datasets/direct-lake-dataset.md +++ b/common/Datasets/direct-lake-dataset.md @@ -18,10 +18,6 @@ applies_to: # Direct Lake Semantic Models Direct Lake semantic models connect directly to data sources stored in [Fabric One Lake](https://learn.microsoft.com/en-us/fabric/onelake/onelake-overview). -> [!IMPORTANT] -> Changing a Direct Lake dataset through the XMLA endpoint will block your ability to change the Direct Lake dataset inside the Fabric Service. Only XMLA endpoint can then edit the Direct Lake This is one of the current limitations of this preview -feature. - Tabular Editor 3 can create and connect to this type of dataset. For a tutorial on this please refer to our blog article: [Direct Lake semantic models: How to use them with Tabular Editor](https://blog.tabulareditor.com/2023/09/26/fabric-direct-lake-with-tabular-editor-part-2-creation/). Tabular Editor 3 can create direct lake semantic models with both the Lakehouse and Datawarehouse SQL Endpoint. @@ -38,4 +34,4 @@ Tabular Editor 2 can connect to Direct Lake semantic models, but does not have a ## Identifying a Direct Lake model -The TOM Explorer informs what object type your tables are. A Direct Lake model's tables will have the object type 'Table (DirectLake)' to make clear that the open model is a Direct Lake model. +The top title bar of Tabular Editor shows which type of model is open in that instance of Tabular Editor. Additionally, the TOM Explorer displays the type and mode of every table (Import, DirectQuery, Dual or Direct Lake). If a model contains a mix of table modes, the title bar will show "Hybrid". Currenctly, it is not possible for a DirectLake model to contain tables in Import, DirectQuery or Dual mode. diff --git a/common/toc.md b/common/toc.md index bd1145e8..0ecfe8fd 100644 --- a/common/toc.md +++ b/common/toc.md @@ -24,6 +24,7 @@ #### @script-create-measure-table #### @script-format-numeric-measures #### @script-create-table-groups +#### @create-field-parameter ### @script-library-advanced diff --git a/images/features/macros/macro_tutorial_create_infobox.png b/images/features/macros/macro_tutorial_create_infobox.png new file mode 100644 index 00000000..29f3ecf0 Binary files /dev/null and b/images/features/macros/macro_tutorial_create_infobox.png differ diff --git a/images/features/macros/macro_tutorial_edit_infobox.png b/images/features/macros/macro_tutorial_edit_infobox.png new file mode 100644 index 00000000..63a15c06 Binary files /dev/null and b/images/features/macros/macro_tutorial_edit_infobox.png differ diff --git a/images/features/macros/macro_tutorial_menu_shortcut.png b/images/features/macros/macro_tutorial_menu_shortcut.png new file mode 100644 index 00000000..021b0cf1 Binary files /dev/null and b/images/features/macros/macro_tutorial_menu_shortcut.png differ diff --git a/images/features/macros/macro_tutorial_save_window.png b/images/features/macros/macro_tutorial_save_window.png new file mode 100644 index 00000000..f2c99d75 Binary files /dev/null and b/images/features/macros/macro_tutorial_save_window.png differ diff --git a/images/tmdl-options.png b/images/tmdl-options.png new file mode 100644 index 00000000..6281b697 Binary files /dev/null and b/images/tmdl-options.png differ diff --git a/te3/features/dax-query.md b/te3/features/dax-query.md index a54f2af1..c708476c 100644 --- a/te3/features/dax-query.md +++ b/te3/features/dax-query.md @@ -53,7 +53,7 @@ Unlike the [DAX Script feature](xrefid:dax-scripts), only the expression propert The "Apply" option has also been added to the right-click context menu. -![Dax Query New](~/images/features/dax_query_window/dax_query_apply_measure_right_click.png.png) +![Dax Query New](~/images/features/dax_query_window/dax_query_apply_measure_right_click.png) The shortcuts for these commands are: @@ -79,7 +79,7 @@ It is also possible to return the value of a measure but a table constructor {} EVALUATE { [Invoice Lines] } ``` -![Dax Query New](~/images/features/dax_query_window/evaluate_measusre.png) +![Dax Query New](~/images/features/dax_query_window/evaluate_measure.png) ### Multiple EVALUATE statements It is perfectly possible to have multiple EVALUATE statements inside the same DAX query. This type of query is most often encountered with Power BI Performance Analyzer queries. diff --git a/te3/features/pivot-grid.md b/te3/features/pivot-grid.md new file mode 100644 index 00000000..669649db --- /dev/null +++ b/te3/features/pivot-grid.md @@ -0,0 +1,30 @@ +--- +uid: pivot-grid +title: Pivot Grids +author: Morten Lønskov +updated: 2024-01-22 +applies_to: + editions: + - edition: Desktop + - edition: Business + - edition: Enterprise +--- +# Pivot Grids + +After adding or editing DAX measures in a model, it is common for model developers to test these measures. Traditionally, this was done using client tools such as Excel or Power BI. With Tabular Editor 3, you can use **Pivot Grids** which behave much like the famous PivotTables of Excel. The Pivot Grid lets you quickly create summarized views of the data in your model, allowing you to test the behavior of your DAX measures when filtering and slicing by various columns and hierarchies. + +To create a new Pivot Grid, use the **File > New > Pivot Grid** option. From here, you can either drag measures, columns and hierarchies directly from the TOM Explorer into the grid, or you can use the **Pivot Grid > Show fields** menu option to display a popup list of all fields that can be dragged into the Pivot Grid (see screenshot below). + +![Show Fields Pivot](~/images/show-fields-pivot.png) + +As fields are dragged into the Pivot Grid, Tabular Editor generates MDX queries that are sent to Analysis Services, to display the resulting data. In this regard, the behavior is very similar to Pivot Tables in Excel. You can rearrange fields in the Pivot Grid by dragging and dropping, and there are various right-click menu options available for customizing how the data is displayed. + +> [!IMPORTANT] +> Since Pivot Grids relies on the Analysis Services engine for query execution, this feature is not available when working in offline mode (such as when editing a model.bim file in Tabular Editor, without a connection to a workspace database). + +![Customizing Pivot Grids](../images/customizing-pivot-grids.png) + +The Pivot Grid is automatically refreshed when a change is made to the model or a refresh operation finishes. You can toggle this auto-refresh capability within the **Pivot Grid** menu. + +> [!Note] +> The Pivot Grid currently does not work with [hidden fields](https://github.com/TabularEditor/TabularEditor3/issues/345). As a workaround, temporarily unhide the field and save the model, before dragging the field into the Pivot Grid. Moreover, the Pivot Grid only displays values on rows/columns [when at least one measure is present](https://github.com/TabularEditor/TabularEditor3/issues/776). diff --git a/te3/features/supported-files.md b/te3/features/supported-files.md index 416fca4d..8d9c1e79 100644 --- a/te3/features/supported-files.md +++ b/te3/features/supported-files.md @@ -210,5 +210,7 @@ You can download the official Microsoft BPA rules here: [PBA Rules](https://raw. Contains all the servers a user has been connected to. It can be advisable to edit it manually to 'forget' past servers no longer relevant. ### Layouts.json -The Layouts file is automatically generated by Tabular Editor when starting the application. -If the Tabular Editor layout does not behave as expected a good first step is to backup this file somewhere else, delete the original and restart Tabular Editor 3. +The Layouts file is automatically generated by Tabular Editor when starting the application. It contains all information to how Tabular Editor 3's UI layout is configured. + +> [!TIP] +> Deleting this file will reset Tabular Editor's layout. If the Tabular Editor layout does not behave as expected a good first step is to backup this file somewhere else, delete the original and restart Tabular Editor 3. diff --git a/te3/features/tmdl.md b/te3/features/tmdl.md index 870bc123..45e11fad 100644 --- a/te3/features/tmdl.md +++ b/te3/features/tmdl.md @@ -15,7 +15,11 @@ applies_to: **TMDL** is a model metadata file format [announced by Microsoft in April 2023](https://powerbi.microsoft.com/en-ie/blog/announcing-public-preview-of-the-tabular-model-definition-language-tmdl/). It aims to provide a human-readable, text-based alternative to the JSON-based model.bim file format. TMDL is inspired by YAML, and as such, is easy to read and write, with minimal use of string quotes and escape characters. It also serializes a model as several smaller files in a folder structure, and is therefore also better suited for version control integration. > [!IMPORTANT] -> As of May 2023, TMDL is still a preview feature. It is currently only supported by community tools such as Tabular Editor and [pbi-tools](https://pbi.tools/). However, the format is fully documented and available through [Microsoft-provided nuget packages](https://www.nuget.org/packages/Microsoft.AnalysisServices.Tabular.Tmdl.retail.amd64/19.64.0-TmdlPreview). +> As of February 2024, TMDL is still a preview feature. It is currently only supported by community tools such as Tabular Editor and [pbi-tools](https://pbi.tools/). However, the format is fully documented and available through [Microsoft-provided nuget packages](https://www.nuget.org/packages/Microsoft.AnalysisServices.Tabular.Tmdl.retail.amd64/19.64.0-TmdlPreview). + +> [!TIP] +> Since TMDL is a preview feature, breaking changes could be introduced between new releases of Tabular Editor. If you face any issues deserializing a model after upgrading Tabular Editor, rollback to the latest version of Tabular Editor, then temporarily save the model as a regular .bim file, before serializing it to TMDL again using the latest version of Tabular Editor. + ## Enabling TMDL (Preview) in Tabular Editor 3 @@ -35,4 +39,4 @@ When saving a new model for the first time, Tabular Editor (since v. 3.7.0), wil # Next steps - [TMDL overview (Microsoft Learn)](https://learn.microsoft.com/en-us/analysis-services/tmdl/tmdl-overview?view=asallproducts-allversions). -- [Get started with TMDL (Microsoft Learn)](https://learn.microsoft.com/en-us/analysis-services/tmdl/tmdl-how-to?view=asallproducts-allversions) \ No newline at end of file +- [Get started with TMDL (Microsoft Learn)](https://learn.microsoft.com/en-us/analysis-services/tmdl/tmdl-how-to?view=asallproducts-allversions) diff --git a/te3/other/release-notes/3_13_0.md b/te3/other/release-notes/3_13_0.md index 632591a7..357d1c30 100644 --- a/te3/other/release-notes/3_13_0.md +++ b/te3/other/release-notes/3_13_0.md @@ -33,7 +33,7 @@ Tabular Editor 3.3.0 (and newer) uses .NET 6. You may have to install the [.NET ## New in 3.13.0 -Check out our [release blog](https://blog.tabulareditor.com/) to get a brief overview of the most important updates in this release. +Check out our [release blog](https://blog.tabulareditor.com/2023/12/15/tabular-editor-3-december-2023-release/) to get a brief overview of the most important updates in this release. ## Improvements in 3.13.0 diff --git a/te3/powerbi-xmla-pbix-workaround.md b/te3/powerbi-xmla-pbix-workaround.md index 2c1545f9..ca17d4d9 100644 --- a/te3/powerbi-xmla-pbix-workaround.md +++ b/te3/powerbi-xmla-pbix-workaround.md @@ -1,6 +1,6 @@ --- uid: powerbi-xmla-pbix-workaround -title: Creating PBIX File from XMLA Endoint. +title: Creating PBIX File from XMLA Endpoint. author: Morten Lønskov updated: 2023-10-18 applies_to: @@ -11,16 +11,16 @@ applies_to: partial: Tabular Editor 3 Business Edition only allows connecting to the XMLA endpoint of Premium-Per-User (PPU) workspaces. - edition: Enterprise --- -# Editing a Power BI dataset through the XMLA endpoint +# Downloading a Power BI dataset to a .pbix using the XMLA endpoint -Once a change is made to a Power BI semantic model through the XMLA endpoint, it's not possible to download the dataset as a .pbix file from the Power BI service. +Once a change is made to a Power BI semantic model through the XMLA endpoint, it's not possible to download the model as a .pbix file from the Power BI service. However, with the Power BI Project file, it's possible to create a .pbix file from the remote model by following the three-step process, which is described as follows. ![XLMA to PBIX Overview](~/images/power-bi/create-pbix-from-xmla-overview.png) > [!NOTE] -> The described workaround isn't officially supported by Microsoft. There's no guarantee that it works for every model. Specifically, if you've added custom partitions or other objects [not listed here](https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-external-tools#data-modeling-operations), Power BI Desktop may not be able to correctly open the file following this approach. +> The described workaround isn't officially supported by Microsoft. There's no guarantee that it works for every model. Specifically, if you've added custom partitions or other objects [listed here](https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-external-tools#data-modeling-operations), Power BI Desktop may not be able to correctly open the file following this approach. ## Step 1: Create and save an empty Power BI projects (.pbip) file diff --git a/te3/powerbi-xmla.md b/te3/powerbi-xmla.md index 82a36c59..9833fb98 100644 --- a/te3/powerbi-xmla.md +++ b/te3/powerbi-xmla.md @@ -1,6 +1,6 @@ --- uid: powerbi-xmla -title: Power BI XMLA endpoint +title: Editing through XMLA endpoint author: Daniel Otykier updated: 2021-10-01 applies_to: diff --git a/te3/toc.md b/te3/toc.md index 30102904..6ae4bbe6 100644 --- a/te3/toc.md +++ b/te3/toc.md @@ -3,11 +3,13 @@ ## @whats-new ## @editions ## @desktop-limitations-te3 -## @powerbi-xmla +## Power BI XMLA Endpoint +### @powerbi-xmla ### @powerbi-xmla-pbix-workaround # Documentation -## @user-interface +## User interface +### @user-interface ### @tom-explorer-view ### @bpa-view ### @messages-view @@ -24,7 +26,9 @@ ### @metadata-translation-editor ### @dax-debugger ### @dax-query -## @supported-files +### @pivot-grid +## Files formats +### @supported-files ### @tmdl ## @preferences ## @shortcuts diff --git a/te3/tutorials/creating-macros.md b/te3/tutorials/creating-macros.md index 794dd8a4..444c2927 100644 --- a/te3/tutorials/creating-macros.md +++ b/te3/tutorials/creating-macros.md @@ -1,8 +1,8 @@ --- uid: creating-macros title: Creating macros -author: Daniel Otykier -updated: 2021-09-08 +author: Morten Lønskov +updated: 2023-12-07 applies_to: editions: - edition: Desktop @@ -11,4 +11,54 @@ applies_to: --- # (Tutorial) Creating macros -(WIP) +Macros are C# scripts that have been saved in Tabular Editor to be easily reused across semantic models. +Saving a script as a Macro will allow that macro to be used when right clicking on the objects in the TOM Explorer making it simple to apply the script to your model. + +## Creating a Macro + +The first step in creating a Macro is to create and test a C# script. + +> [!TIP] +>One easy way to get started with C# scripting is to use the built in record function that lets you record the actions you take in the TOM Explorer. +>This way you can see how to interact with the different model objects and create reusable scripts. +>Another way is to reuse existing scripts such as those in our [script library](xref:csharp-script-library). +>In this tutorial we use the script [Format Numeric Measures](xref:script-format-numeric-measures) to showcase the Macro functionality. + +Once the script works according requirements the script can be saved using the toolbar button "Save as Macro" which will open the "Save Macro" window. + +![Macro Create infobox](~/images/features/macros/macro_tutorial_create_infobox.png) + +The "Save Macro" window allows three options: +1. Macro Name: Give the Macro a name and use backslash "\" to create folder path for the macro (See bellow) +2. Provide a tooltip for the Macro to remember what it does in detail +3. Select a context where the Macro should be available. + +![Macro Save infobox](~/images/features/macros/macro_tutorial_save_window.png) + +In the above example the Macro will be saved in a folder called Formatting\Beginner and the script is called "Format Numeric Measures". It will be saved in the context of measures. + +### Macro Context +Macros are saved in a "valid context" that determines which objects in the model the script can be applied to. + +This Macro can then be used when Right Clicking on a measure in the TOM Explorer. The context given while saving the Macro determines which objects will show the Macro when right clicking on that object. + +Tabular Editor will suggest a context based on the script that is being saved. + +![Macro Menu Shortcut](~/images/features/macros/macro_tutorial_menu_shortcut.png) + +## Edit a Macro + +A macro can be opened by double clicking it in the Macro pane and after editing the C# script saved using _Ctrl + S_ or the Edit Macro button. + +![Macro Edit Infobox](~/images/features/macros/macro_tutorial_edit_infobox.png) + + +## Macro JSON file + +Macros are stored in the %LocalAppFolder%/TabularEditor3 as a JSON file called MacroActions.json. For more information on file types in Tabular Editor please see [Supported File Types](xref:supported-files#macroactionsjson) + +## Macro file example + +An example of a MacroActions.JSON file can be found here. It contains several of the C# scripts from our script library: [Download example MacroActions File](https://raw.githubusercontent.com/TabularEditor/TabularEditorDocs/main/assets/file-types/MacroActions.json) + + diff --git a/te3/features/user-interface.md b/te3/views/user-interface.md similarity index 94% rename from te3/features/user-interface.md rename to te3/views/user-interface.md index bf1ec0ef..513d0973 100644 --- a/te3/features/user-interface.md +++ b/te3/views/user-interface.md @@ -1,6 +1,6 @@ --- uid: user-interface -title: User interface +title: Basic user interface author: Daniel Otykier updated: 2021-09-08 --- @@ -62,7 +62,7 @@ The **File** menu primarily contains menu items for dealing with loading and sav ![File Menu](~/images/file-menu.png) -- **New**: Opens a submenu that allows you to create a new blank data model (Ctrl+N), or create various [supporting files](supported-files.md#tabular-editor-supporting-files) such as a new DAX Query or DAX Script (text files) or a data model diagram (JSON file). Supporting files (with the exception of C# scripts), can be created only when a model is already loaded in Tabular Editor. +- **New**: Opens a submenu that allows you to create a new blank data model (Ctrl+N), or create various [supporting files](xref:supported-files.#supported-file-types) such as a new DAX Query or DAX Script (text files) or a data model diagram (JSON file). Supporting files (with the exception of C# scripts), can be created only when a model is already loaded in Tabular Editor. ![File Menu New](~/images/file-menu-new.png) @@ -81,7 +81,7 @@ The **File** menu primarily contains menu items for dealing with loading and sav ![Supported File Types](~/images/supported-file-types.png) > [!IMPORTANT] -> In Tabular Editor 3 Desktop Edition the **Open > Model from file...** and **Open > Model from folder...** options are not available and the **Open > File...** dialog only allows opening [supporting files](supported-files.md#tabular-editor-supporting-files), not files containing metadata. +> In Tabular Editor 3 Desktop Edition the **Open > Model from file...** and **Open > Model from folder...** options are not available and the **Open > File...** dialog only allows opening [supporting files](xref:supported-files#supported-file-types), not files containing metadata. - **Revert**: This option lets you reload the model metadata from the source, discarding any changes that are made in Tabular Editor, which have not yet been saved. This option is useful when Tabular Editor 3 is used as an External Tool for Power BI Desktop, and a change is made in Power BI Desktop while Tabular Editor 3 is connected. By choosing **Revert**, Tabular Editor 3 can reload the model metadata from Power BI Desktop without having to reconnect. - **Close**: This closes the active document (for example a DAX Query, a C# script or a data model diagram). If the document has unsaved changes, Tabular Editor will prompt you to save the changes before closing. @@ -94,7 +94,7 @@ The **File** menu primarily contains menu items for dealing with loading and sav - **Recent tabular models**: Displays a list of recently used model metadata files or folders, allowing you to quickly reload model metadata from one of these. > [!IMPORTANT] -> In Tabular Editor 3 Desktop Edition the **Save to folder** and **Recent tabular models** options are disabled. In addition, the **Save as** option is only enabled for [supporting files](supported-files.md#tabular-editor-supporting-files). +> In Tabular Editor 3 Desktop Edition the **Save to folder** and **Recent tabular models** options are disabled. In addition, the **Save as** option is only enabled for [supporting files](xref:supported-files#supported-file-types). - **Exit**: Shuts down the Tabular Editor 3 application. You are prompted to save any unsaved files or model metadata before the application is shut down. @@ -116,8 +116,8 @@ The **Edit** menu contains standard Windows application menu items for editing a > [!NOTE] > Tabular Editor generally only prompts for object deletion when multiple objects are selected, or when there are dependencies to the object(s) being deleted. Object deletion can be undone by using the **Undo** option (CTRL+Z). -- **Select all**: Selects all text in the currently active document, or all objects belonging to the same parent within the TOM Exporer. -- **Code assist**: This option is available when editing DAX code. It provides a shortcut to various code assist features relevant for editing DAX code. See [DAX editor](dax-editor.md#code-assist-features) for more information. +- **Select all**: Selects all text in the currently active document, or all objects belonging to the same parent within the TOM Explorer. +- **Code assist**: This option is available when editing DAX code. It provides a shortcut to various code assist features relevant for editing DAX code. See [DAX editor](xref:dax-editor#code-assist-features) for more information. ## View @@ -125,7 +125,7 @@ The **View** menu lets you navigate between the different views of the Tabular E ![View Menu](~/images/view-menu.png) -- **TOM Explorer**: The TOM Explorer presents a hierarchichal view of the entire [Tabular Object Model (TOM)](https://docs.microsoft.com/en-us/analysis-services/tom/introduction-to-the-tabular-object-model-tom-in-analysis-services-amo?view=asallproducts-allversions) of the currently loaded model metadata. See @tom-explorer-view for more information. +- **TOM Explorer**: The TOM Explorer presents a hierarchical view of the entire [Tabular Object Model (TOM)](https://docs.microsoft.com/en-us/analysis-services/tom/introduction-to-the-tabular-object-model-tom-in-analysis-services-amo?view=asallproducts-allversions) of the currently loaded model metadata. See @tom-explorer-view for more information. - **Best Practice Analyzer**: The Best Practice Analyzer helps improve the quality of your model by letting you specify rules for best practice validation. See @bpa-view for more information. - **Messages**: The Messages view displays errors, warnings and informational messages from various sources, such as the Tabular Editor 3 Semantic Analyzer. See @messages-view for more information. - **Data Refresh**: The Data Refresh view allows you to track data refresh operations that are running in the background. See @data-refresh-view for more information. @@ -168,7 +168,7 @@ The **Window** menu provides shortcuts for managing and navigating between the v ![View Menu](~/images/window-menu.png) -- **New...** this submenu provides a shortcut for creating new [supporting files](supported-files.md#tabular-editor-supporting-files). The options here are identical to those under **File > New**. +- **New...** this submenu provides a shortcut for creating new [supporting files](xref:supported-files#supported-file-types). The options here are identical to those under **File > New**. - **Float** undocks the current view or document into a floating window. - **Pin tab** pins a tab. When a tab is pinned, it is shown at the left-most side of the document tabs, and when right-clicking on the tabs, shortcuts are available for closing only unpinned tabs. diff --git a/templates/lightbox-featherlight/partials/head.tmpl.partial b/templates/lightbox-featherlight/partials/head.tmpl.partial index c330cda3..01736391 100644 --- a/templates/lightbox-featherlight/partials/head.tmpl.partial +++ b/templates/lightbox-featherlight/partials/head.tmpl.partial @@ -9,7 +9,7 @@ {{#_description}}{{/_description}} - + @@ -17,4 +17,4 @@ {{#_enableSearch}}{{/_enableSearch}} {{#_enableNewTab}}{{/_enableNewTab}} - \ No newline at end of file + diff --git a/templates/lightbox-featherlight/partials/scripts.tmpl.partial b/templates/lightbox-featherlight/partials/scripts.tmpl.partial index 16b384b4..aeadd30b 100644 --- a/templates/lightbox-featherlight/partials/scripts.tmpl.partial +++ b/templates/lightbox-featherlight/partials/scripts.tmpl.partial @@ -1,6 +1,6 @@ {{!Copyright (c) Microsoft. All rights reserved. Licensed under the MIT license. See LICENSE file in the project root for full license information.}} - + diff --git a/whats-new/3-13-0.html b/whats-new/3-13-0.html new file mode 100644 index 00000000..d1467cd4 --- /dev/null +++ b/whats-new/3-13-0.html @@ -0,0 +1,10 @@ +

Tabular Editor 3.13.0

+

Latest release: December 2023 (v. 3.13.0, release notes)

+ \ No newline at end of file diff --git a/whats-new/index.html b/whats-new/index.html index 7b9fb199..8d115259 100644 --- a/whats-new/index.html +++ b/whats-new/index.html @@ -109,14 +109,21 @@

Community

Ask questions, suggest enhancements and help other TE fans get their answers at our GitHub community:

Articles

Share your favorite blog or SoMe post with the community

+

Video

+

Other resources