Continuing the discussion from
Hello @sudhanss, welcome to the QuickSight community!
Would you be able to create a demo version of the issue you are experiencing in QuickSight Arena? I’ll include some documentation on how to build an Arena dashboard:
This will allow me to see the problem you are having and test out some possible solutions in QuickSight directly. Just make sure that you remove any sensitive data since this is a public forum.
Alternatively, can you post some screenshots of the visual issue, plus explain what the expected outcome is and any calculated fields you may be utilizing. That would allow me to provide a more detailed response to your question. Thank you!
Hello @sudhanss, I wanted to check in since we have not received a response. Please provide some more information on the issue you are facing and I can help guide you towards a solution. If we do not hear back from you in 3 days, I will close out this topic. Thank you!
Hi Dylan, Sorry for the delayed response.
The below link has sample images from the previous use case.
Problem I am trying to solve: Lets say i have 100 tickets, each ticket is in a different stage. Now when I report, I would like to show the value as Sum of that stage plus all the stages after that and repeat the same for successive stages. This would help me end up with a waterfall table, which shows cumulative numbers.
To achieve this, I created 5 calculated fields for each stage using “ifelse” that would give me either the stage value or null. This would mean that the calculated field would have high null values as we move down the stages, considering we will only be showing the last bucket of the staging alone.
Now when i add these 5 calculated fields one after another into the pivot, the group by logic shows blank values as expected. However we cannot filter out null values, since there will be data for the previous stage which needs to be reported.
Temporary Solve I found: I have sorted the values descending, which pushes the blank values to the bottom of the pivot. Once this is done, I change the font & background coloring for cell/header to be the same in order to not allow users to be able to read the value. However those blank cells will continue to show up on pivot and users when they click on the blank cells will be able to read the value.
If there is a way to hide specific cells it would be great 
or if there was a different calculated field model to be used, it would have sorted this issue.
Hello @sudhanss, I did a little bit of testing on this to see if I could bypass the issue in the pivot table. Unfortunately, even with some calculated fields to manage the logic, attempting to hide a row depending on something like a user selection ends up breaking the visual all together.
I think the only way to really manage this how you are wanting would be to swap between different pivot table visuals in the free form layout using condition rules. If you set up some type of user select to change a parameter value, that could decide which waterfall pivot table you would want to show. That is likely the best work-around solution to the issue you are facing.
I’ll link some documentation below: