Added documentation for new Tabular Editor CLI in Limited Public Prev…#313
Added documentation for new Tabular Editor CLI in Limited Public Prev…#313gronnerup wants to merge 8 commits into
Conversation
…iew. This includes new Tabular Editor CLI item and 8 new doc pages covering installation, commands, ci/cd etc.
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://delightful-mud-081affe03-313.westeurope.azurestaticapps.net |
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://delightful-mud-081affe03-313.westeurope.azurestaticapps.net |
| none: true | ||
| - product: Tabular Editor 3 | ||
| none: true | ||
| - product: Tabular Editor CLI |
There was a problem hiding this comment.
I think it is correct to introduce a new applies_to category, but I just wonder if we need to update all our other documentation with the CLI apply_to? For example Script How to would also apply to CLI.
There was a problem hiding this comment.
Hmm... good question. Some of the scripting doc pages include screenshots of the desktop application - for those I would for sure not add the CLI apply_to. For the Scripting Patterns maybe.
To keep it clean I would recommend that we create a dedicated scripting page for the CLI where we could reference other relevant scripting articles - also covering scripting limitations etc. in the CLI.
| > [!IMPORTANT] | ||
| > The Tabular Editor CLI is in **Limited Public Preview**. It is offered for evaluation with a Tabular Editor account; no license is required during preview. Commands, flags, and outputs may change before general availability. **The preview build stops functioning after 2026-09-30.** We recommend against using the CLI in production CI/CD pipelines during preview. | ||
|
|
||
| The Tabular Editor CLI authenticates to Power BI Service, Microsoft Fabric, and Azure Analysis Services using the same Power BI Desktop client ID that Tabular Editor 3 uses. Tokens are cached locally so you authenticate once and re-run commands silently until the refresh token expires (typically 90 days). |
There was a problem hiding this comment.
Do we need to update security-privacy.md with information around CLI? At least an apply_to is needed.
| Pass an XMLA endpoint, workspace name, or `powerbi://` URL as `--server`: | ||
|
|
||
| ```bash | ||
| te connect "powerbi://api.powerbi.com/v1.0/myorg/Finance" "Revenue Model" |
There was a problem hiding this comment.
Add example of different organsisation "powerbi://api.powerbi.com/v1.0/SpaceParts/Finance" "Revenue Model"
| `te config paths` resolves where the CLI will actually look for TE3 data files — useful when debugging missing macros or BPA rules. | ||
|
|
||
| ## Setting values | ||
|
|
There was a problem hiding this comment.
Needs a line here about what these commands do
| ``` | ||
|
|
||
| > [!TIP] | ||
| > When stdout is piped, `auto` already emits JSON. Explicit `--output json` is only necessary when you want JSON on a TTY, or when a consumer expects it regardless of how the command is invoked. |
There was a problem hiding this comment.
What does the word consumer mean here - it is not a term we generally have used in our documentation elsewhere
| ``` | ||
|
|
||
| ## Python | ||
|
|
There was a problem hiding this comment.
Lacks explanation of what this subsection is about
| ``` | ||
|
|
||
| ## PowerShell | ||
|
|
There was a problem hiding this comment.
lacks explanation of section
| The Tabular Editor CLI is designed for unattended execution in continuous integration and delivery pipelines. A single binary, structured output, non-interactive mode, native CI annotations for GitHub Actions and Azure DevOps, and VSTEST-compatible test results make it a natural replacement for ad-hoc TE2 invocations. | ||
|
|
||
| > [!WARNING] | ||
| > During preview, we recommend against using the CLI in **production** pipelines. Commands, flags, and outputs may change before GA. Build and evaluate in non-production pipelines first; share feedback so the GA shape matches your needs. |
There was a problem hiding this comment.
Add link to GitHub repository to share feedback in
| ``` | ||
| te [MyModel]> | ||
| ``` | ||
|
|
There was a problem hiding this comment.
Picture of starting a session?
| | `-L` / `-LOGIN <user> <pass>` (after `-D`) | *Not yet implemented.* | Use `te auth login` with service principal or env-based credentials instead — see @te-cli-auth. | | ||
|
|
||
| ## Migration playbook | ||
|
|
There was a problem hiding this comment.
Readd warning about production pipelines`?
…TabularEditor/TabularEditorDocs into user-pg/te-cli-limitedPuPr-docs
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://delightful-mud-081affe03-313.westeurope.azurestaticapps.net |
|
|
||
| The Tabular Editor CLI (`te`) is a cross-platform command-line interface for Power BI and Analysis Services semantic models. It runs on Windows, macOS, and Linux as a single self-contained executable and wraps the same model engine (TOMWrapper) that powers Tabular Editor 3 Desktop. | ||
|
|
||
| Use it to inspect, edit, validate, deploy, refresh, and test semantic models from a terminal — against local TMDL or BIM files, Power BI Desktop, or semantic models in Fabric and Power BI Service workspaces. |
There was a problem hiding this comment.
Doesn't feel this is a complete sentence, and what does 'it' refer to?. Instead of "Use it to inspect" - maybe consider: "You can use the Tabular Editor CLI".
There was a problem hiding this comment.
I am also missing a "why this matters". Why should one use this compared to what we had previously with the CLI and the tool itself? what new scenarios does this unlock and when should I use this vs the others?
There was a problem hiding this comment.
Yes, this should be rewritten as a compact Why use the Tabular Editor CLI section
| - **AI agents** — token-lean structured output, predictable exit codes, machine-parseable errors. | ||
| - **CI/CD pipelines** — non-interactive mode, GitHub Actions and Azure DevOps annotations, VSTEST-compatible test results. | ||
|
|
||
| The same design choices — structured JSON output, a `--non-interactive` global flag, clear errors — serve all three. |
There was a problem hiding this comment.
These design choices were not introduced earlier in the doc - it's confusing they are mentioned just here. Shouldn't we have a section about these choices at the top?
| | Connect to local SSAS instance (TCP transport) | Yes | No | | ||
| | Connect to Power BI Desktop (named-pipe transport) | Yes | No | | ||
|
|
||
| Local SSAS and Power BI Desktop connections rely on Windows-only transport protocols. All cloud-based workflows (Power BI Service, Fabric, Azure Analysis Services) work on every platform. |
There was a problem hiding this comment.
shouldn't this be a banner like ![IMPORTANT]?
|
|
||
| # Command Line and Integration | ||
| ## @command-line-options | ||
| ## [Tabular Editor CLI (Limited PuPr)](xref:te-cli) |
There was a problem hiding this comment.
The order here seems kind of random? Why would I want to know about commands before config?
There was a problem hiding this comment.
Config is about custom configurations which most users will probably not attempt, if anything it should perhaps be lower.
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://delightful-mud-081affe03-313.westeurope.azurestaticapps.net |
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://delightful-mud-081affe03-313.westeurope.azurestaticapps.net |
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://delightful-mud-081affe03-313.westeurope.azurestaticapps.net |
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://delightful-mud-081affe03-313.westeurope.azurestaticapps.net |
…iew. This includes new Tabular Editor CLI item and 8 new doc pages covering installation, commands, ci/cd etc.