We have designed a panel for registered users which is driven by “used-based rules”. The panel works fine if we access it via the Quicksight login site with the registered users, but we would like to include a link in our external system (CRM) that will launch the pannel in a new window of the browser using the “GenerateEmbedUrlForRegisteredUser” API.
The URL produced by the API launches the pannel ok, but the problem is that takes really a long time (1,5 mins average) loading before any data is shown. Once the panel is loaded you can play with the filters and see the data fine, but the time it takes to load is not acceptable for an user to wait until he sees the information.
As I said, this does not happens if you access the Quick Sight panel using the login site, selecting the panel… information is shown in 1 or 2 seconds.
Are you using SPICE or direct query? Also, for the dataset, are you doing calculations on the analysis layer or on the data prep layer, and how complex are you calculations?
The reason I ask is those are the primary ways that you can speed up loading data into a dashboard.
Sorry, I got QS mail in Spam and this is why I could not answer you before.
We are using a Panel with 4 Sheets, and these sheets uses also two different DataSets
Both DatSet1 & DataSet2 are both Spice DataSest filtered with used-based rules.
We have some Calculated fields in these sheets, but with basic calculations like “(a+b)/c” or counters.
What it is strange is that if I access the panel using the QS site, it works fine, but launching it with this URL generated it is when it takes too long.
Are you still encountering the same issues or were you able to deploy a work around that helped speed up this process?
Take a look at the attached article that explores various ways to help with data flow:
If you continue to encounter these delayed load times that aren’t taking place directly in QS, I would consider filing a support case to get more direct assistance from AWS support team.
If we do not hear back within the next 3 business days, I’ll close out this topic.
Since we have not heard back, I’ll close out this topic. However, if you have any additional questions, feel free to create a new post in the community and link this discussion for relevant information if needed.