diff --git a/content/features/te-cli/te-cli-commands.md b/content/features/te-cli/te-cli-commands.md index b68e66c06..1873911d2 100644 --- a/content/features/te-cli/te-cli-commands.md +++ b/content/features/te-cli/te-cli-commands.md @@ -215,19 +215,19 @@ te open ./model.bim # Open a BIM file in TE3 ### init -Create a new empty semantic model at the given path. Defaults to a TMDL model in `PowerBI` compatibility mode at compatibility level 1702. +Create a new empty semantic model at the given path. Defaults to a TMDL model in `PowerBI` compatibility mode at compatibility level 1705. `te init` accepts: - `` - positional argument: directory to create the model in (omit to use the global `--model` path). - `--compatibility-mode ` - `PowerBI` (default) or `AnalysisServices`. -- `--compatibility-level ` (alias `--compat`) - compatibility level. Defaults to `1702` when the mode is `PowerBI`, `1500` otherwise. See @update-compatibility-level. +- `--compatibility-level ` (alias `--compat`) - compatibility level. Defaults to `1705` when the mode is `PowerBI`, `1500` otherwise. See @update-compatibility-level. - `--name ` - model/database name (default: the directory name). - `--serialization ` - `tmdl` (default), `bim` (alias `tmsl`), `database.json`, `pbip`. - `--force` - replace any existing file or directory at the target path. ```bash -te init ./new-model # TMDL, PowerBI mode, compat 1702 +te init ./new-model # TMDL, PowerBI mode, compat 1705 te init ./new-model --serialization bim # Single-file BIM model te init ./as-model --compatibility-mode AnalysisServices # AS model, compat 1500 te init ./existing-dir --force # Overwrite non-empty directory diff --git a/content/how-tos/update-compatibility-level.md b/content/how-tos/update-compatibility-level.md index 382dca9b2..f0578857d 100644 --- a/content/how-tos/update-compatibility-level.md +++ b/content/how-tos/update-compatibility-level.md @@ -30,7 +30,7 @@ Compatibility Level and Compatibility Mode are separate properties that serve di | Property | Controls | Values | |---|---|---| -| `Database.CompatibilityLevel` | Which TOM features are available (e.g., custom calendars, DAX UDFs) | `1200`, `1500`, `1600`, `1701`, `1702`, etc. | +| `Database.CompatibilityLevel` | Which TOM features are available (e.g., custom calendars, DAX UDFs) | `1200`, `1500`, `1600`, `1701`, `1702`, `1705`, etc. | | `Database.CompatibilityMode` | Which platform the model targets, which TOM objects and properties are available, and which edition restrictions apply | `Unknown`, `AnalysisServices`, `PowerBI`, `Excel` | If you need to change the platform target rather than unlock new TOM features, see [Change compatibility mode](xref:change-compatibility-mode). @@ -40,7 +40,7 @@ If you need to change the platform target rather than unlock new TOM features, s Upgrade when: - A feature exists in Power BI Desktop but the related TOM property is missing in Tabular Editor -- You need newly introduced capabilities like **custom calendars** (1701+) or **DAX user-defined functions** (1702+) +- You need newly introduced capabilities like **custom calendars** (1701+), **DAX user-defined functions** (1702+), or **user-context calculated columns** (calculated columns that use user-context functions, 1705+) - You're standardizing development across environments and want consistent minimum feature sets ## Before you start @@ -86,6 +86,7 @@ Examples: - **Custom calendars:** 1701+ - **DAX UDFs:** 1702+ +- **User-context calculated columns:** 1705+ > [!NOTE] > Minimum required levels for features can change as the platform evolves. Always verify prerequisites in current documentation. Some levels/features are Power BI-only and may not be available on SSAS/AAS. @@ -134,4 +135,4 @@ After updating and saving: - Confirm **Database → Compatibility Level** reflects the new value in Tabular Editor - Verify the expected feature surfaces (e.g., the **Functions** node becomes available at 1702+) -- If targeting SSAS/AAS, validate deployment against the server's supported compatibility levels \ No newline at end of file +- If targeting SSAS/AAS, validate deployment against the server's supported compatibility levels diff --git a/content/kb/bpa-powerbi-latest-compatibility.md b/content/kb/bpa-powerbi-latest-compatibility.md index c4b448d8e..4069120d7 100644 --- a/content/kb/bpa-powerbi-latest-compatibility.md +++ b/content/kb/bpa-powerbi-latest-compatibility.md @@ -70,17 +70,17 @@ Team policy to delay upgrades. ``` Model Compatibility Level: 1500 -Current Maximum Level: 1700 +Current Maximum Level: 1705 ``` ### After Fix ``` -Model Compatibility Level: 1700 (Latest) +Model Compatibility Level: 1705 (Latest) ``` Access to new features like enhanced calculation groups and field parameters. ## Compatibility Level -This rule applies to Power BI models at all compatibility levels. \ No newline at end of file +This rule applies to Power BI models at all compatibility levels. diff --git a/content/tutorials/new-pbi-model.md b/content/tutorials/new-pbi-model.md index 441d983bd..aae2486c8 100644 --- a/content/tutorials/new-pbi-model.md +++ b/content/tutorials/new-pbi-model.md @@ -1,4 +1,4 @@ ---- +--- uid: new-pbi-model title: Create a Power BI Semantic Model author: Daniel Otykier @@ -34,7 +34,7 @@ This page walks you through the process of creating a new Power BI semantic mode ![New model](~/content/assets/images/tutorials/new-pbi-model.png) -- Provide a name for your model or use the default value. Then, set the compatibility level to "1609 (Power BI / Fabric)". +- Provide a name for your model or use the default value. Then, set the compatibility level to "1705 (Power BI / Fabric)" (the latest Power BI / Fabric level). - For the best development experience, check the "Use workspace database" option. This requires that you have a development workspace available in Power BI, with XMLA read/write enabled. When you click OK, you will be prompted to enter the connection string for the Power BI workspace in which you want the workspace database created. > [!NOTE]