I’m reposting the same question as I couldn’t figure out how to use the Quick Sight community effectively before.
I have a question about the relationship between parameters and calculated fields.
When I hover over a parameter without a default value on the calculated field screen, the following warning message appears:
Parameters without a default value aren’t usable in calculated fields.
However, it is actually possible to include and save a parameter without a default value in a calculated field. Is this a new specification change in Quick Sight?
I’d like to understand the behavior when using parameters without a default value in calculated fields.
Hello @ken1 , welcome to the Quick Sight community!
Technically you aren’t supposed to be able to use parameters without default values. To get around this you can use “ALL_VALUES” in the default option.
Out of curiosity, what happens when you use that calculated field? Does it work as expected?
Since using multiple media items results in the following error, I will split the message into multiple parts:
“An error occurred: Sorry, new users can only put one embedded media item in a post.”
Out of curiosity, what happens when you use that calculated field? Does it work as expected?
Sometimes it works as expected, and sometimes it doesn’t.
As a test, I created radar charts. “Radar Chart_No.1” is a chart with Quick Sight filters applied, while “Radar Chart_No.2” is created using a parameter without a default value.
Radar Chart_No.1 uses the following columns from a test dataset directly.
These values were randomly generated, so they are not meaningful in themselves.
The calculated field used in Radar Chart_No.2 is shown below (only evaluation_item_1_calc is provided here, but other calculated fields were created in the same way).
In this case, Radar Chart_No.2 appears visually incorrect—it does not display all categories, even though the control shows “All”. This is the case where it does not work as expected.
However, as you may already know, the “All” selection in the control is treated as NULL.
By adding logic to handle NULL in the calculated field, it becomes possible to display all categories in the radar chart while still showing “All” in the control. This is when it does work as expected.
I’m still unclear about one point:
Why is it possible to use a parameter without a default value in a calculated field, even though the warning message says it shouldn’t be allowed?
Any insights or clarifications would be greatly appreciated. Thank you in advance!
It’s been about a week since my last reply, but I’m still hoping to understand this behavior better.
If anyone else has encountered this or can shed some light on it, I’d truly appreciate your input.
I’m tagging this as an error and archiving it for the Quick Sight team.
I would also recommend creating an AWS support ticket to float this up as an 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.
