I created a calculated field in quicksight Q topic, but it shows "Oops. Something went wrong. (VISUAL_CALC_REFERENCE_MISSING, INVALID_DATAPREP_SYNTAX, GENERIC_DATA_SOURCE_EXCEPTION)"

I am getting an error as,
Oops. Something went wrong. (VISUAL_CALC_REFERENCE_MISSING, INVALID_DATAPREP_SYNTAX, GENERIC_DATA_SOURCE_EXCEPTION)

This is my calculated field
image

please anyone give a solution and reason for this.

Thanks in advance!

Hi @priyanka1,
A common cause for receiving this error would be if a field that’s being referenced was removed; are all fields being utilized in this calculated field still located within your dataset?

Additionally, I wonder if it has something to do with the ‘sum’ calculation being nested within the ‘runningSum’. Is this calculated field causing the same error when tested out in an analysis? What if you tried removing the additional ‘sum’, do you still receive the same error?

Hi @Brett , Thanks for your reply!
I can’t write this RunningSum function without doing nesting sum

I can see data in other visuals(line chart and table), but I am not able to see data in particular visuals(example: KPI).
Can you please give a reason for this error?Why RunningSum is not applicable for some visuals?

1 Like

Hi @priyanka1,
Sorry for the delayed response on this topic!
After looking in to this a bit more, this may just be a limitation where Q is not recognizing the appropriate aggregations needed for your calculated field.

Have you tried building the calculated field on the dataset level and then bringing in to the Q topic instead of building within?

1 Like

Hi @Brett ! Yes, I have created a calculated field in dataset level, in there also few visuals are not applicable for RunningSum function.

Hi @priyanka1,
To my understanding, the RunningSum function may not work with certain visuals that are ‘single value visuals’, like a KPI for instance, may lack the continuous flow of data needed to create a running total.
This is why it may work for some visuals that can show over time but not work for single value visuals. I believe this is just a limitation within QuickSight.

Let me know if you have any additional questions!

1 Like

Hi @Brett , thanks for giving the clarity on this.