I have a customer that wants to be able to select from a List (multi-select) of the available columns in a Paginated Report Table to customize it before printing.
I believe do this I need a parameter with the selected columns and then have this really complicated calculated column that selects which data to display in the column. But I haven’t found a way to set the Column Header/Label correctly. If I have 5 columns in the list and user select 3 of those columns this would leave 2 of the columns empty and maybe in the middle of the report.
What I need is a way to conditionally hide a column? Are you planning on adding conditional hiding of columns.
Conditional formatting of columns would be very useful to have not just for the ability of users to create their own reports but also for security. We have reports where certain columns should not be visible to all employees. I currently do not have the ability to hide when those users are running the Paginated report. This has been one of the reason we have been shy to adapt paginated reports.
Both conditional hiding of visuals and table columns would also be very useful in the Interactive Dashboards all for the same reasons. Currently we are building multiple variations of the same report or dashboard and restricting access to the report by those users.
Thank You for considering this
Hello @Joel_Isenstadt , welcome to the Quicksight community!
To clarify, do you want the end user of the paginated report to have the ability to use a filter in your paginated report before printing, or for Quicksight authors to be able to filter prior to the Paginated report being emailed out?
For hiding columns, have you tried using column level security?:
I would also suggest checking out managing groups in Quicksight:
I would second this desire for interactive dashboard’s table visual customization with more flexibility in showing/hiding columns. Allowing an end user the option to modify the columns in a table would satisfy our similar requirements.
We have explored paginated, however our embedded use case does not fit paginated, since giving users the ability to customize filters and fields displayed in a table would be more in line with an interactive dashboard scenario. If we gave the user a predefined table, with standard fields, then the user could adapt and modify what fields they desire in the table.
Hello @bkasen !
I think this is a really interesting use case! Since this thread was marked as solved, could you repost this at the top of the community and link back to this thread?
That way I can mark your post as a fresh feature request for the Quicksight team. Feel free to tag me as well.