Skip to content

docs: document undocumented customer-facing changes from the last week #11652

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
keydunov wants to merge 1 commit into
base: master
Choose a base branch
from
+25 −5
Open

docs: document undocumented customer-facing changes from the last week #11652

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs-mintlify/docs/explore-analyze/analytics-chat.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ The AI agent interprets your questions, generates queries against your semantic
- **Python analysis** – For work SQL can't express — forecasting, cohort analysis, statistical tests — the agent can run [Python](/docs/explore-analyze/workbooks/python-analysis) and render the result inline, then save it to a workbook as a re-runnable report (in preview)
- **Semantic model integration** – All queries run against your semantic model with proper access control and security, honoring the active [security context](/docs/explore-analyze/workbooks/querying-data#applying-a-security-context)—including an override applied by a developer or admin
- **Queued messages** – Send follow-up messages while the agent is still processing
- **Save to Workbook** – Export insights to [Workbooks](/docs/explore-analyze/workbooks) for further analysis
- **Save to Workbook or as an exploration** – Ask the agent to save a result, either into a [workbook](/docs/explore-analyze/workbooks) as a report or, if you don't name a workbook, as a standalone [exploration](/docs/explore-analyze/explore) for further analysis

@claude claude Bot Aug 26, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The behavior is accurate but the trigger is implicit — "if you don't name a workbook" means the destination depends on what the user omits from a prompt, which is hard to discover from a feature bullet. Consider a concrete example prompt pair somewhere in the body of the page (this page already has a "Try prompts like" pattern below), e.g. "Save this to the Revenue workbook" vs. "Save this".

Also worth a follow-up cross-link: explore.mdx documents "Exploring from Analytics Chat" as clicking Explore, and its "Saving explorations" section lists only the manual Save paths — neither mentions that the agent can now produce a saved exploration directly. A reader landing on Explore first won't learn about this.


## Discover available fields

Expand Down
11 changes: 9 additions & 2 deletions docs-mintlify/docs/integrations/google-sheets.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,8 @@ A modal window with an authentication prompt will appear. Choose the deployments
that you want to work with in Google Sheets and click **Authorize**.
Once you see the `Access Granted` message, close the modal window.

If you want to revoke the authentication, open the add-on menu and click
The add-on menu shows the current tenant, Cube account, deployment, and signed-in
user. If you want to revoke the authentication, open the add-on menu and click
**Sign out**.
Comment on lines +64 to 66

@claude claude Bot Aug 26, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: the new sentence about what the menu displays is grafted onto the sign-out paragraph, so two unrelated facts share one block. Splitting reads better and makes the display change findable:

Suggested change
The add-on menu shows the current tenant, Cube account, deployment, and signed-in
user. If you want to revoke the authentication, open the add-on menu and click
**Sign out**.
The add-on menu shows the current tenant, Cube account, deployment, and signed-in
user.
If you want to revoke the authentication, open the add-on menu and click
**Sign out**.

Same applies to microsoft-excel.mdx:72-74.


## Create reports via pivot table
Expand All @@ -80,7 +81,13 @@ Google Cloud for Sheets works only with [views][ref-views], not cubes.
Click on members to add them to **Rows** and **Measures**.
If needed, drag dimensions from **Rows** to **Columns**. Click on
the funnel buttons to add members to **Filters**. Click on **×** to
remove members from a query.
remove members from a query. Drag members within **Measures** to reorder them
in the output.

When a dimension is on **Columns**, the **Measure position** option controls
how measures nest relative to the column values: **After columns** (default)
nests measures under each column value, while **Before columns** makes each
measure span all column values.

<Frame>
<img src="https://ucarecdn.com/acc8e133-f237-4aa7-a725-f32dd4a2ebdb/" />
Expand Down
6 changes: 6 additions & 0 deletions docs-mintlify/docs/integrations/mcp-server.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -244,6 +244,12 @@ work together.
Call `searchDataModel` before `runQuery` to find exact view and member names rather than
guessing them.

`runQuery` also takes an optional `branchName` to query a [dev branch][ref-dev-mode]
instead of the deployed model — use it to verify a data model edit before committing it.
Every response reports the branch it actually ran against (`null` means the deployed
model). Keep `branchName` identical across paginated calls: dropping it on a later page
re-runs the query against the deployed model instead of continuing on the branch.
Comment on lines +247 to +251

@claude claude Bot Aug 26, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A reader hitting this paragraph has no idea where a branchName value comes from — startDataModelEdit (the tool that returns one) isn't introduced until line 290, in a later section that's only registered for model-editing roles. Two small fixes:

  1. Point at the source of the value, e.g. "…use the branchName returned by startDataModelEdit, or the name of an existing dev branch."
  2. The runQuery table row above describes the tool's other inputs/outputs (offset, hasMore, totalRows) but not branchName, so someone skimming only the table misses it entirely. Worth a clause there too.

Fix this →

Comment on lines +250 to +251

@claude claude Bot Aug 26, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"paginated calls" is ambiguous given the tool list above documents two pagination paths: runQuery itself paginates "via offset", while loadQueryResults "paginates through the results of a previous query." Which one does this caveat apply to?

If it's repeated runQuery calls with offset, say so ("when you re-issue runQuery with a higher offset"). If loadQueryResults is the normal path, the more important question is whether it carries the branch context implicitly or needs branchName passed too — as written a reader can't tell, and the failure mode (silently querying the deployed model) is exactly the one this paragraph is warning about.


### Dashboard authoring

These tools build [workbooks][ref-workbooks] and [dashboards][ref-dashboards]
Expand Down
11 changes: 9 additions & 2 deletions docs-mintlify/docs/integrations/microsoft-excel.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,8 @@ A modal window with an authentication prompt will appear. Choose the deployments
that you want to work with in Microsoft Excel and click **Authorize**.
Once you see the `Access Granted` message, close the modal window.

If you want to revoke the authentication, open the add-in menu and click
The add-in menu shows the current tenant, Cube account, deployment, and signed-in
user. If you want to revoke the authentication, open the add-in menu and click
**Sign out**.

## Create reports via pivot table
Expand All @@ -88,7 +89,13 @@ Cube Cloud for Excel works only with [views][ref-views], not cubes.
Click on members to add them to **Rows** and **Measures**.
If needed, drag dimensions from **Rows** to **Columns**. Click on
the funnel buttons to add members to **Filters**. Click on **×** to
remove members from a query.
remove members from a query. Drag members within **Measures** to reorder them
in the output.

When a dimension is on **Columns**, the **Measure position** option controls
how measures nest relative to the column values: **After columns** (default)
nests measures under each column value, while **Before columns** makes each
measure span all column values.

<Frame>
<img src="https://ucarecdn.com/670fda9d-358a-4345-9242-7888d8aaedd8/" />
Comment on lines +92 to 101

@claude claude Bot Aug 26, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Measure position explanation is clear, and mirroring it verbatim in google-sheets.mdx matches how these two pages are already kept in sync — good.

One gap: the <Frame> screenshot immediately below predates both the reorderable Measures pane and the Measure position control, so the prose now describes UI the image doesn't show. Not blocking, but worth queuing a screenshot refresh (both pages).

Expand Down
Loading