Continuing the discussion from Impact of failed spice dataset refresh on Dashboard:
Continuing the discussion from Impact of failed spice dataset refresh on Dashboard:
The dashboards do break and do not show the data from the previous successful refresh…This is a very annoying phenomenon because we do not know if the users will see a proper or broken dashboard in the morning after the nightly ds refresh. Is there any solution to this problem?
Hi @gnc
We have been using Quick Sight for a while and have had issues with dataset refresh failures; but have not had an instance where the dashboard has broken.
Can you provide a more detailed information about your case so we can understand the issue and may be suggest a solution/workaround?
Regards,
Giri
Hi Giri
It happens all the time- When a dataset fails to tefresh the dashboard does not display data from the dataset (that is what I mean by broken( instead of displaying data before the bad refresh.
Result in visual from today:
Message of refresh failure:
I hope there is a solution for this problem, because the management opens a dashboard and sees these messages instead of what they are supposed to see…
Thank you
Gili
What kind of details will help? I can’t share specific details.
`Hi @gnc
Let us say your visual has a filter to show data for the current day; then it will show No data if your dataset refresh failed and did not bring in any data. However, there may be data upto previous day.
So I am trying to rule out that case.
Regards,
Giri
Hi Giri
Thanks for the explanation. I have to wait for an ingestion to fail in order to test your theory. I will be in touch with you when it happens.
Thank you!
Gili
Hi @gnc
It’s been a while since we last heard from you. If you have any further questions, please let us know how we can assist you.
If we don’t hear back within the next 3 business days, we’ll proceed with close/archive this topic.
Thank you!
Hi Giri
I hope you can help me with this problem:
I have a lag function by year in a pivot table that works fine when a filter by year is not applied. When the filter is applied then the lag is not calculated, even when it is removed from the visual. Is there another way to use the lag so that it will be indifferent to the filter? Or another function that computes the lag of a measure that I can use for this purpose?
Thanks in advance
Before filter - Calculated results as expected:
After applying filter on year- fourth row is displayed- Lag not calculated
Hi @Giridhar.Prabhu,
Hope everything is well with you! Just checking in on this thread to see if you saw gnc’s most recent message regarding a lag not calculating.
Would appreciate very much a solution to this issue.
Hi @gnc,
My apologies for the long delay in replying back. I believe the reason why the lag is not calculating is because when you filter by one year, the lag function has no previous year reference to look back on.
I recommend using a window function (such as sumOver but might need to use a different one in your case). This should allow you to specify the Exist check by PRE_FILTER so that the lag function can obtain reference. If you are still facing the issue after, please feel free to send your calculated field to see if we can come up with an alternative solution. Hope this helps!
Hi @gnc
Following up here as it’s been a while since last communication took place on this thread; did you have any additional questions regarding your initial post?
If we do not hear back within the next 3 business days, I’ll close out this topic.
Thank you
Hi @gnc ,
Since I haven’t received any further updates from you, I’ll treat this inquiry as complete at this time. Please feel free to create a new post if you have more questions.
Thank you
