SearchViewConfig
Hi there. I am working in a
SearchEmbed and would like to use multiple datasources. However, the documentation says that it is no longer supported and we should use the datasource (singular string ID) instead.
When I used the array of strings on datasources it worked well, but of course, my goal is to follow the documentation whenever possible.
My question is: Why multiple datasources is an issue on the SearchEmbed at this moment even having it working? Any Advice on how can I achieve this? Or should I keep always one single datasource?
Reference: https://developers.thoughtspot.com/docs/Interface_SearchViewConfig#_datasourcesSearchViewConfig
The configuration attributes for the embedded search view.
6 Replies
I also want to report an error in the documentation here:
https://developers.thoughtspot.com/docs/Interface_SearchViewConfig#_datasource
It says:
datasource
The array of data source GUIDs to set on load.But in fact, it is a singular string. š
SearchViewConfig
The configuration attributes for the embedded search view.
Typically, ThoughtSpot users will Search on a Worksheet, which is like a semantically grouped set of tables. It's unusual to give direct access to the underlying tables. You also are unable to create a single visualization across Worksheets as it does not make sense to join these objects together.
I'm curious what you're trying to do here. š
In my case, I have two data sources (can have more in the future) and want to give the ability to the users to build their reports based on the given datasources. They would use the TS SearchEmbed/ Answers for that.
You could have the source selector in your own app, and then render the Search embed for that source.
While we do currently support multiple sources it might be unsupported in the future.
I assume there is also a way of fetching all available sources for that user through the API too, right? - Maybe this API Meta Data?
- https://developers.thoughtspot.com/docs/rest-apiv2-reference#_metadata
REST API v2.0 Reference
REST API Reference
Yes, you can try it out in the playground. Pass the metadata type as "Logical_Table"