Cannot access data for this visual

Q&A
, , , ,
1

Good morning, everyone,
I have been running duplicate Analyses and Datasets. The new Analyses was linked to the new Dataset. I also get the blue message of successful data import, but in the Visuals I have the message “Cannot access data for this visual”. Also if I try to open the Filters I get “Unable to fetch data: Cannot fetch dataset.”

2

Hello @joNic, when you create your dataset, are you importing it into SPICE or are you using direct query. If it is direct query, I wonder if it is taking too long to run. I would recommend to edit and publish it again in SPICE if that is the case.

3

PICE. The dataset runs a custom query. It does the import in a few minutes, though. So I’m waiting for it to complete the import before verifying

4

Hello @joNic, if you tried applying it to visuals before the first import completed, you would see the error above! Let me know if things are working as expected when that refresh completes. If not we can dig into it further.

5

If I create a new Analyses, the data shows up without any problems. If I do a dataset replacement instead, I get that error on the visuals

6

Hello @joNic, there have been a few occasions where I have replaced a dataset like that on a dashboard and it did not maintain my calculated fields. Is it possible that calculated fields required for the visuals are not showing and that is why the visuals are displaying an error? If not, are you ignoring any of the fields from the original dataset when you map the new dataset as a replacement?

Those are the only issues I can think of for this if the dataset is working as expected in a new analysis. I suppose the other possibility is that fields are not mapping correctly when you replace the dataset. Let me know if any of those issues I mentioned are occurring and we might be able to figure out a solution.

7

Hello @DylanM.
I am happy to report that it is now working. I am not sure what the problem was. I performed a switch to the old look. Here I did the dataset replace, which was successful, and then I went back to the new look.

1 Like
8

Hello @joNic, thank you for following up. That sounds like it could possibly be a bug from the New Look, so I will tag this as a feature-request and archive the topic for our support team to take a look at just in case. I’m glad you were able to get it working!