Hi all,

Hi all, I'm using the Visual Embed SDK to embed a Liveboard, and using Trusted Authentication to grab a token for a particular user to use in the embed. The Liveboard is launching ok, but it displays no data in each of the panels. Attached are sample screenshots of an empty Liveboard and a populated one, which I can see if I run the embed from a browser where my admin account is logged in. This makes me think it's a data permissions issue, but I've shared the Liveboard and its worksheets with the group that the user belongs to for whom we're requesting a token in step 1. Would love some pointers to the best ways to debug this issue, thank you!
No description
No description
4 Replies
shikharTS
shikharTS•7mo ago
This can be due to one of the 2 reasons : 1. RLS : Is there any Row level security that you have implemented for any user? That can potentially result in no data in certain scenarios 2. Have you added any runtime filters while you are embedding the liveboard? Or any other type of filter that might not be visible in the ThoughtSpot UI?
About row-level security (RLS) | ThoughtSpot Cloud
Using row-level security (RLS), you can restrict data that appears in search results and Liveboards by group or user.
LiveboardViewConfig
The configuration for the embedded Liveboard or visualization page view.
Chris Winters
Chris WintersOP•7mo ago
Thanks for following up! 1. I've verified that RLS is not enabled on any of the tables the Liveboard's worksheet is referencing. 2. The liveboard embedding code is just about the simplest thing it can be, no filters added: const liveboardEmbed = new LiveboardEmbed( liveboardElementSelector, { frameParams: {width: '100%', height: '100%'}, liveboardId: liveboardId } ); liveboardEmbed.render(); 3. I've also verified that the JWT that we're using has an empty object associated with 'user_parameters', so no filtering is going on there, either.
shikharTS
shikharTS•7mo ago
Can you raise a TS ticket for this? Looks like the user has some filtering going on that someone from TS might be able to identify
Chris Winters
Chris WintersOP•7mo ago
FWIW, it turned out to be an issue with the name of the user and group! They both had a leading number, and changing it to a letter got everything to work 🤯

Did you find this page helpful?