I am creating a dashboard, and adding a filter. For certain fields, I get an error saying “Something went wrong”, but I cannot determine the cause. Some fields work while others get the error. My dataset is a .XLSX file with multiple tables loaded into Spice and I’ve done this successfully dozens of other times. This field is a simple text field.
Thank you
Hello @Jdimarcantonio , welcome to the Quicksight community!
To troubleshoot this, is the error happening across fields of the same data type like strings or is it mixed between data types?
Also, have you already attempted refreshing the analysis in your browser?
Thank you @duncan . I have continued to investigate what may have happened and it looks liek one of my data uploads to refresh the data added some additional columns of data. This caused a ripple effect and is (I believe) the root cause of the issue. I am trying to sort this out…
Thank you,
Joe
Hello @Jdimarcantonio !
Got it, I will mark that as the solution for now but please feel free to post again if the problem persists!
I am getting back to this issue after a couple of weeks of working on other projects. As of now it is still not resolved.
I ran a simple test where I loaded data from a .xlsx file (a single table) into Spice then created a simple doughnut chart. No problem. I add a filter using the previously references “Active / Inactive” field, which is a text field that has one of 2 values, A or I. I want to filter the data to indicate that only rows with a value or “A” should be displayed.
When I specify a Filter Type of “Filter List”, expecting it display a list of values to select from, it shows “Not Found”. I tried to filter other fields as well, same result.
The table has 2,845 rows. Have I encountered a limit of some kind in QuickSight? I tried this same thing with other tables of data that have fewer rows (less than 1,000 rows) and it works fine. Could this be a defect? I would appreciate your thoughts…
Thanks,
Joe
Hello @Jdimarcantonio !
I would recommend creating an AWS support ticket for this issue.
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.
