Hello team, I was wondering if you can
Hello team, I was wondering if you can help me with a suggestion. Currently we are doing liveboard embedding into our application. And every tenant will their own liveboards embedded. And all these liveboard comes from same template.
lets say their have an improvement to the template liveboard or one chart in the template, how should i update all deployed customers liveboard to reflect new changes?
4 Replies
Please take a look at this and see if this helps : https://developers.thoughtspot.com/docs/development-and-deployment
Development and deployment in ThoughtSpot
Overview of development and deployment following the SDLC practices in ThoughtSpot
@Murali Krishna definitely check out the documentation on deployment. I couldn't tell from your description if you had already deployed or not. If this is the first time, then my recommendation varies based on what options you have:
* If you can use GitHub, I really like using the version control APIs.
* If you don't, then the only real option is to use the metadata export/import APIs
These are both via APIs. If you don't want to write your own code, check out the cstools project (https://thoughtspot.github.io/cs_tools/tools/). There is a tool called
git that wraps the git APIs and one called scriptability that handles the metadata export/import calls (and also has support for mapping built in.)@bill_da_golfer I didn't quite understand your point, if you can elaborate that would be great.
currently what we are doing is when ever a customer is onboarded, we generate a TML for liveboard and respective entities. so their are 3 liveboards we generate for each customer and then use TML import API from ThoughtSpot. once imported we get its ids which will be used for liveboard embedding.
Hi, @Murali Krishna ,
You will be creating different liveboard for each customer, if the data is different.
Can you also confirm on what do you refer by liveboard templating ?
The templating will be provided by you on the outer side for the embed am I correct ?
The one usecase I can confirm here,
If you use one liveboard and based on fliters and params you are showing different data to different customers then, changing the basic liveboard will reflect changes to all the customers of yours. This should do for your usecase.