Hi @Team,
SPICE Method ( Datasets from S3 as CSV files ).
after removing 10 to 20 unnecessary calculated columns/measures which are not used in any visual from the dataset, visuals are not loading showing proper error like below.
I don’t see any errors after removing unnecessary calculated columns/measures in the datasets.
Have you checked the field well and the filters pane to see if anything shows as missing?
There is also a possibility that the fields you think are not used may be referenced in some other calculated fields. They will show up with a long key value if the underlying field has been removed.
If you look at one of these visuals you should be able to determine the missing link
Regards,
Giri
Hi @Giridhar.Prabhu , I have checked all the visuals, i didn’t remove or delete the Fields/Measures/ calculations which are used in all visual but showing error.
Hello @Venkat.Metadata
Were you able to find a solution or are you still facing this issue?
Did you remove the calculated fields from the analysis or the data prep layer? It’s easy to run into a situation where you delete something in the data prep layer that doesn’t seem relevant but is used in the analysis within another calculated field.
Hi @duncan , I still face the issue for 2 days then I removed all the visuals then I re-created all visuals.
is that wrong way to delete/remove Un -necessary calculated fields at the Analysis layer?
Suppose, in what layer is better to remove /delete unnecessary
what if i do reverse way? Although i have removed / deleted unnecessary calculated fields / calculated measures, right?
No, I have cross verified 3 times before deleting all as i don’t delete calculated fields which are used in calculated measures ( these finally used in Visuals )
if A used in B
If B used in Visual
i don’t delete A because B is used in Visual
If I don’t use A or B or Both then only I removed/deleted A & B.
Hello @Venkat.Metadata
In my experience, some times the only way to fix that error is to recreate the visuals because, as you experienced, it’s hard to find where the issue is coming from.
The reason it was confusing is because that error usually happens when you do broad changes to a dataset or swap datasets that visuals rely on like changing or removing calculated fields.
