When we switch to spotter 3 and upgraded Embedded SDK to 1.49.1, Action.PreviewDataSpotter is not being respected. We are using enabledActions and this action is not in the list but still appears in UI. I switched to Spotter 2 and "Preview Data" was not appearing. Same applies to quick search / Deep Analysis. Also how can we hide the quick search / Deep Analysis? https://cdn.discordapp.com/attachments/1143209464875462756/1515946597635194990/Screenshot_2026-06-15_at_3.05.46_PM.png?ex=6a30dac9&is=6a2f8949&hm=3b500f85f98a601ddfa25962aa3e9e1f9108faaaf976a7bc7bf7deb0f0ba9374&

message has been deleted

Solution: What you’re seeing is expected with Spotter 3 in current SDK behavior: some top-bar/chat-mode controls (like Quick Search / Deep Analysis mode switcher, and related chat controls) are not controlled by older action IDs such as

Action.PreviewDataSpotter

the same way Spotter 2 did. For Spotter 3, use the newer Spotter chat action IDs introduced in recent SDK versions (1.48.x+), especially: -

Action.SpotterChatModeSwitcher

→ controls Quick Search / Deep Analysis switcher -

Action.SpotterChatConnectorResources

-

Action.SpotterChatConnectors

Use them in

hiddenActions

(or

disabledActions

depending on UX you want). Example:

javascript
import { init, AuthType, SpotterEmbed, Action } from '@thoughtspot/visual-embed-sdk';

init({
  thoughtSpotHost: 'https://<your-thoughtspot-host>',
  authType: AuthType.None,
});

const spotter = new SpotterEmbed('#ts-spotter', {
  worksheetId: '<your-worksheet-guid>',
  hiddenActions: [
    Action.PreviewDataSpotter,      // still include if you want Preview Data hidden where supported
    Action.SpotterChatModeSwitcher, // hides Quick Search / Deep Analysis
    Action.SpotterChatConnectors,
    Action.SpotterChatConnectorResources,
  ],
  // or use disabledActions if you prefer disabled instead of hidden
});

spotter.render();

If

Preview data

still appears even with

Action.PreviewDataSpotter

, that indicates Spotter 3 UI behavior/version mismatch rather than your config syntax. In that case, validate against the exact cluster + SDK pairing and test with

hiddenActions

explicitly (not only

enabledActions

logic). Suggestions: - Prefer `hiddenActions`/`disabledActions` over relying only on an allowlist pattern when moving from Spotter 2 → 3. - Confirm your ThoughtSpot cluster version supports the Spotter 3 action controls from SDK changelog (these were added in 1.48.x notes).

Hey can you raise a support case for this? might be an issue. Thanks.