I have around 10 datasets in my analysis and for a one dataset while replacing, the functionality not working. It does not give any error message, instead quit from the Dataset Replacement Dialog Box. Then the dataset pane is not visible and need refresh.
Could you try open the two datasets one by one ( both predecessor & successor dataset) and try save and publish it . Check if any issues are showing up there and try to replace the dataset in analysis one more time.
If the issue persist , its better to create AWS support case to debug this issue further .
Here are the steps for opening a support ticket - Creating support cases and case management - AWS Support . If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf
Sorry to hear you are having trouble replacing a dataset in your Amazon QuickSight analysis. A few other things to try:
Try replacing the dataset with a simple test dataset with same data type. See if the issue reproduces.
Disable SPICE capacity if enabled. There could be a capacity issue trying to query after replace.
Create a copy of the analysis and attempt the replace there as a test.
Make sure your user permissions allow editing/updating the associated datasets.
Try to do the replace via the API or CLI instead of the console UI.
As a last resort, delete the visualization with the problematic dataset entirely and re-add it.
This seems like an odd UI bug or permission issue that is isolating the single dataset. Systematically testing and eliminating possible causes generally helps troubleshoot.
Please let me know if any of those suggestions help resolve the replace issue! Reach out to AWS Support too if it continues, they may need to investigate further.
Hello @Yasiru_Randika, were you able to resolve this issue in QuickSight? It seems like a bug, but were you able to get more information from AWS Support? I will mark the previous response as the solution for now, but I would be interested to hear about the solution you implemented if you were able to find one. Thank you!
@DylanM As you suggested this may be a bug. I have communicated this issue to AWS Support Team 3 weeks ago and what I heard is still the Technical Team is working on this.
Hello @Yasiru_Randika, I am sorry to hear it hasn’t been resolved yet. Once the support team is able to fix this bug, would you mind confirming on this topic that it is working again for you? I just want to make sure it is being accounted for. Thank you for following up!
I have communicated this issue to the AWS Support and Technical Team confirmed that this is due to a technical issue. By 13th of February deployment, this issue has been fixed from AWS Quicksight.