What is the problem or goal you're trying to solve or accomplish?
The customer has a multi-tab dashboard where a section in one tab has a "Go to data" button meant to take the user to the corresponding section in another tab; the same lightweight, in-page jump you'd expect from an anchor link on a web page, without reloading and while keeping the user's current filters applied.
There is no supported way to do this today, and the gap is not specific to embedding. Within a single tab, an anchor-style jump to a section works. But crossing into another tab requires loading that tab's content, which is a state change rather than a scroll, and no in-place mechanism performs it. The only native affordance that lands on a specific tab and section is the permalink (via the chart Share menu or the anchor icon on a section header), and it has two problems even in the standard, non-embedded dashboard: it triggers a full reload rather than an in-place transition, and it is a point-in-time snapshot that re-applies the filter values captured when it was created; overriding the user's current selections and producing inconsistent data between tabs.
Embedding compounds this: the permalink resolves to a full-application route that cannot be rendered inside an embedded frame, so it fails outright there. In other words, the capability is missing in the standard product and additionally broken in the embedded context.
How are you solving it currently?
They generate a permalink to the target section (using the anchor icon next to the section header) and paste it into a Markdown component styled as a "Go to data" button. In the non-embedded dashboard this loads the target but reloads the page and can reset the applied filters to whatever was live when the permalink was created; in the embedded dashboard it fails entirely. The only reliable fallback is switching tabs manually via the dashboard tab bar, which preserves live filters but does not land on a specific section. Same-tab anchor navigation is available but does not address the cross-tab case they need.
What is your recommended solution?
A supported mechanism for in-dashboard navigation to a specific tab and section that (a) performs the transition in place, without a full reload, (b) preserves the user's current filter state rather than applying a stale snapshot, and (c) works consistently in both the standard and embedded contexts (i.e. without routing through the full application). This could take the form of a native "link to section/tab" component or link type that switches the target tab and scrolls to the target section client-side, carrying the live filter context across the jump.