Mark K - Hello, I'm trying to create a custom d...
Hello, I'm trying to create a custom dataSource selector. (ignore the janky UX, just exploring).
I use the below to change the datasource:
However it appears to re-render the entire embed element (video attached). Is there a better way to approach this?
12 Replies
@Sandeep do you have any advise here?
Search embed asks for datasource during creation of the instance. If you do give a new data source, it probably will re-render the entire embed element. Can you use full app embed?
@shikharTS I can. Would this still be using a hostevent.search trigger with different data source or something else?
no it should be using the same host event it is supported with app embed https://developers.thoughtspot.com/docs/Enumeration_HostEvent#_search
HostEvent
Event types that can be triggered by the host application to the embedded ThoughtSpot app.
@shikharTS that still has the same behaviour as the SearchEmbed then - it reloads the entire component in the UI
Will check this. cc @yuichirio_ha to take a look as well.
I can repro, will check if that is expected behavior.
Thanks!
Hey @Mark K ,
That is the current behavior fix, I think preivously it didn't used to take up empty queries.
Used to throw errors.
For empty queries this happens.
It's expected behavior as per current updates.
Thanks.
@yuichirio_ha is there any method you could suggest that allows us to set the data source from outside the embed element and have it cleanly change the datasource within the embed?
I'm not sure what you mean by "expected behaviour". Are you saying the entire embed element reloading is expected behaviour? That sounds like a bug...
Hey @Mark K , yeah, that day I initiated conversation internally to confirm what's the exepectation here and if anything we have regardingt that.
Will update you as I get the response. Thanks.
Meanwhile if it's blocking for you - then you can raise a support ticket for this too.
Hey @Mark K , as I told, if it's blocking for you - you can add a feature request or add a ticket. for this particular behavior.
That's the conclusion to internal discussion also.
Thanks.
I've created a support ticket, thanks..