Has anybody else experienced this issue? When trying to save a calculated field, I get an error message. But the error message is not helpful because it’s clearly trying to reference some backend variables that are—ironically—not syntactically correct.
I’ve been seeing this in Quicksight for at least a year now and I always thought it would just be fixed one day, but I’m finally tired of it. I need error messages that actually tell me what’s wrong.
Hi @reaganl,
This is definitely interesting that you have been encountering this scenario in various instances for a while. Could you please provide a specific example on a calculated field you recently tried to save (or one that gave you that error in general) just to ensure all of the fields are expected types?
Thank you!
Sure. I got this exact error when trying to save the following calculation:
reg_count is an INT (calculated field added at the dataset level) , session_year is a String, and CycleMonthIndex is an INT (calculated field created in the visual builder).
Hi @reaganl,
Although everything looks to be syntactically correct and theoretically should work, I believe it is raising that general error because of the mixing of calculating fields between dataset and analysis layers. I would recommend recreating ‘reg_count’ in the analysis level (which should make sure everything is an aggregate for sumOver parameters) to see if that lets you save the calculated field.
@WLS-Luis I appreciate you trying to help, but the issue really isn’t about this calculated field. I ended up solving the problem with a different calculated field.
This question is about the Quicksight error message that is shown when there is an error in your calculated field. The error message Quicksight is showing is broken. It should not say {{argumentName}}; it should tell me which of my arguments is incorrect. It should not say {{functionName}}; in this case, it should say sumOver().
This is simply a bug that AWS needs to address, not really a specific question that I have.
@reaganl Glad you were able to find a workaround! And I agree with you as well regarding the general error message. Thank you for tagging this post as an error. I will keep this post up so that the AWS Team may be able to address the issue in the future!
I’ve been experiencing this issue as well ever since I started using quicksight. It makes debugging calculated fields really difficult. I hope this can be solved soon, so I’ll watch this topic. 
Thank you for letting us know. 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!
