Hi,
We are facing an issue on our QuickSight Dashboard: Refresh Failure After Dataset Modification. The dashboard has failed to refresh our SPICE dataset. When attempting to refresh, we receive an error message stating “a general SQL error occurred.”
We need support in identifying the root cause of this SQL error and guidance on how to successfully incorporate the additional mapping without disrupting the dashboard’s functionality.
Issue Description:
After adding additional mapping to our existing dashboard through the following steps:
Hello @elstubbs, welcome to the QuickSight community!
While we do not have the ability to access your account directly, I can help you debug the issue you are facing. My initial thought is that there is some kind of date formatting that is happening in the SQL statement that is not compatible with Excel datasets. I wouldn’t be surprised if it throws the error because of the join even though the field is coming from your database. Are there any date fields that you are formatting in the SQL statement?
Also, when you initially created the dataset join, did it fail the first dataset refresh or did it work and then fail when it refreshed on schedule?
Lastly, what database are you using to query the original dataset before joining it with the Excel file?
With a little more information on the issue, I can help provide further guidance. Thank you!
Hello @elstubbs, I wanted to check in since we have not heard back from you with any further information. Did my previous response help you resolve this issue or were you able to figure out a solution? If so, let me know what you did to fix it. Otherwise, please respond to my questions from the previous response and I can help guide you further.
If we do not hear back from you in 3 days, I will archive this topic. Thank you!
I had a look at the data, and since we cross checked our raw data and the dashboard data (vlooked up the mapping onto exported dashboard csv file), there should be no formatting issues, although I am not sure how to check the SQL statement for compatibility.
Once the extra mapping imports, it kind of works, but it only shows 8 or so random weeks out of all of the 52+ weeks that should be there.
Here is a SS of the dataset we are using, i am not sure where i can find the information regarding the database I am using to query the original dataset before joining it with the Excel file.
Hello @elstubbs, I can’t really get much information from the Summary tab screenshot other than the size of the dataset. It is very likely that you are exceeding the dataset size limit for the dataset you are using in the join.
If the secondary dataset is over 20GB, then that might be the reason for the missing data. You can find more information about each dataset that is involved in the join if you click the edit dataset button at the top right corner of the screen. That should allow you to view the SQL that is utilized for the main dataset and find information about the dataset that is being joined.
Hello @elstubbs, did my last response help resolve the issue you are facing? If not, please follow-up with some more information and I can try to guide you further.
If we do not hear back from you in 3 days, I will archive the topic. Thank you!
Hello @elstubbs, since we have not heard back from you, I will archive this topic. If you still need assistance, please post a new question in the community. That will ensure you are at the top of the priority list for a response from one of our QuickSight experts. Thank you!
