Hi QuickSight team,
We are migrating an existing dashboard and encountered a limitation.
Our calculated fields are created at the Analysis level. However, when creating a dropdown control (parameter/filter), those calculated fields do not appear as selectable fields.
Creating the calculated fields at the Dataset level is not our preferred option because of performance concerns and dataset refresh/maintenance requirements.
My questions are:
Is it expected behavior that Analysis-level calculated fields cannot be used in dropdown controls?
Is there any supported workaround?
What is the recommended best practice for this scenario?
Thanks!
Hi @ymarined,
Welcome to the Quick Community! Yes this is current intended behavior for calculated fields, as analysis level ones are computed at analysis query time unlike at the dataset level.
However, if possible, could you provide a little bit more context in regard to your use case? Depending on that, I feel that it is possible you could utilize parameters within your calculated fields to define conditionals that define visual behavior.
Thank you!
Hi @ymarined,
Just checking back in to see if you were able to view my most recent reply in regard to your questions and/or if you were able to find a solution in the meantime. Please help the community by following up in general within the next 3 business days!
Thanks!
Hi @ymarined,
Since I haven’t received any further updates from you, I’ll treat this inquiry as complete for now. If you have any additional questions, feel free to create a new post in the community and link this discussion for context.
Thank you!