A dataset is corrupted after deleting another dataset that was included, no way to get past this

Hi

I have a dataset that aggregates several other datasets. One of these embedded datasets was deleted because it was a duplicate of another one. A calculated field was defined by using one field from the deleted dataset, and now whenever I try to save I get a generic error " Can’t perform this action - Something went wrong" (without further details) and when I click on Refresh Now I get “A calculated field contains invalid syntax. Correct the syntax and try again.” even though I’ve removed all calculated fields - it looks like there is still the old calculated field that is broken and it is making the whole dataset broken too.

This is unfortunate because this dataset takes forever to build with the user interface (I wish there was something similar to LookML for this) and I don’t want to start from scratch for such a trivial issue.

@matteo-upsellguru ,

Do you have backups of your dataset ? If yes maybe you can try recreating a new one to check if it works.
As I was looking at another post ( Dataset Replacement failing - #10 by blakecar ) , wondering if your analysis has any controls associated with the deleted dataset.

Otherwise I would recommend filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the steps to open a support case. 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. Hope this helps!

Kind regards,
Koushik

1 Like

Hi Kousik

Thanks - at the end I was able to remove the offending fields by using awscli to do that. But I felt it quite annoying not being able to do that via UI and having to rely on parsing a huge JSON file to figure out what could be the issue.

@matteo-upsellguru
happy to hear it was resolved . To clarify : the missing fields were not visible in the UI , but using the awscli when you ran describe-dataset , you were able to find those fields in the output JSON file ?

1 Like

hi @Koushik_Muthanna - that’s correct. By using aws quicksight describe-dataset and aws quicksight update-data-set I was able to solve it. But parsing the JSON file myself was no joke.

On another note, I’ve recently had to create several datasets as I mentioned, and as I mentioned I had to do that via UI and I could spot several UI annoyances - what’s the best way to provide some feedback to the team?

1 Like