Geovane - Hello ThoughtSpot team!I would like...
Hello ThoughtSpot team!
I would like to explore a better usage of our liveboards.... Right now I am creating a new Liveboard (reading from the same datasouce) for every single client... however, it is getting very hard to manage.
What are the options you suggest to have a better workflow?
- Parameters?
- Views?
- Something else?
If you could also teach me a little bit on "how to", would be great- the documentation for paramenters and views are not great.
6 Replies
Hi @Geovane ,
Thanks for reaching out!
Could you share how each Liveboard differs per client? For example—are you changing just filters like Client ID, or are the visualizations/data logic different?
If the structure is mostly the same, you don’t need separate Liveboards. Here are better options:
• Runtime Parameters: Build one Liveboard and pass client-specific filters dynamically.
• Row-Level Security: Restrict data per user so each client sees only their data.
• Saved Answers or Views: Create reusable filtered answers instead of duplicating boards.
• Dynamic Embedding: If embedding, you can pass filters programmatically.
Happy to guide you further once we understand your use case better!
There are also personalized views, which the users can create on the same liveboard..
@shikharTS but is there a way where I can have these personalized views for an entire group? (instead of individual users?)
I don't think so @Geovane personalized views will not be for an entire group. But yo ucan use the filters/RLS rules mentioned by @sandeep above to filter the liveboard for a particular group..
Thanks. @shikharTS and @sandeep .
I am already using runtime filters, RLS and even some answers.
However, our business need here is:
- We have 60% of the clients that use a liveboard (just changing the data by using runtime filters/rls)
- However, for the other 40% we would need almost the same liveboard but with some minor structural changes, such as adding a new block or even changing a little bit one block of the liveboard...
- - We have been solving it by creating entirely new liveboards for this 40% and making a lot of manual code changes to dynamically load these custom liveboards
- - As you can imagine, this is not scalable and is causing a bottleneck on both sides, code and liveboard creation (multiple almost equal liveboards).
Knowing that, do you have any suggestions on how we can expand our liveboard utilization?
Understood. Unfortunately, I do not have a solution for this other than creating a new liveboard for different groups. I would suggest to talk on the in-app chat support or a solution analyst if they have a better solution (which I am sure they would have).