Ability to Expand/Collapse horizontal sections or rows full of field cards (like filters).

In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds:

For UX with large grid data, Users wanted to have filters to narrow down results, issue here was they had more than 15 filters for which we had to use field cards. Now even if these cards are set to their minimum width and heights, half the page was consumed by these filters in 3 sections, one under other considering 4-5 filters in 1 row. This was even if okay on desktop, laptop view of screens was pretty bad and resulted in escalations.

How often is this impacting your users?

This was on almost every page and was the first thing users had to deal with.

Who is this impacting? (ex. model builders, solution architects, partners, admins, integration experts, business/end users, executive-level business users):

Business/end Users, Executive-level Business Users

What would your ideal solution be? How would it add value to your current experience?

Can we have some way on UX to mark that a particular row/rows are part of filters and can collapse them after filter use is done? This way result grid would come up and users can have larger view of data.

Please include any images to help illustrate your experience.

Can't post application images.

Comments

cgillett

I have a similar setup in one my apps (only 6 filters, multiselect). For one particular page, I have given my users three approaches, which they can choose between based on their personal preferences. It means I'm maintaining three (technically, four) pages instead of one, but thankfully the requirements haven't changed since I added the additional options, it's only one page, and my users are happy.

I moved the filters to the bottom of the page. Users have to scroll down to use them, but it's not the first thing they see anymore, and they can focus on the grid.
I moved the filters to another page entirely, with a link to the filter page and a text description of the selected filters on the page with the grid. This provides more space for the filters, since they are multiselect and can have anywhere from 3 to 26 options.
I changed the Board to a Worksheet and moved the filters to the Insights panel.

Options 1 and 2, being Boards, can include KPIs and charts at the top, while Option 3 can include those same KPIs and charts in the Insights panel.

Options 2 and 3 work best on tablets and laptops, as well as when sharing screens for collaborative sessions.

I have a few other pages that also leverage the same filters, but the use cases for those are more limited, and only one option is offered for each, although it varies based on the use case.

I have seen this idea come up before. I hope it eventually makes it onto the roadmap.

Rajnee

Hi @cgillett , Thank you for suggestions. I think 3 option is what we would have tried but this new app was move from legacy to new one on Anaplan. So users wanted exact same features and look and feel, plus we had filters on so many pages that maintaining separate page for filters of each page wasn't feasible option. Moving filters to the bottom, I would say users didn't like it, though on some pages, we did put them in middle of 2 grids but just 1 row, more than that would break link between 2 grids, so that option was not recommended.

May I know what you mean by 'multiselect'? Is it like you can select multiple values from same dropdown? or you are saying combination of multiple dropdown filters? We had user requirements where they wanted to select multiple values from same dropdown. e.g. City dropdown - they wanted to select one or more cities.

Regards.

cgillett

Hi, @Rajneekant Ukalkar , I used the multiselect filters described by @daniel_bad in the How I Built It: Limitless Interdependent Multi-Select Filters (https://community.anaplan.com/discussion/158405/how-i-built-it-limitless-interdependent-multi-select-filters). Each filter is a module based on Users and one list with a Boolean line item. The user selects the item(s) they want to see, and a master filter module consolidates all the selections into a single Boolean line item which filters the final grid. They are not dropdowns, so they take up more space, but it's a very elegant solution to the multiselect use case.

My use case is very simple compared to yours. All of the pages that use my filters, use the same combination of filters, so I only need one page to hold all of the filter modules and apply the same filter to several other pages.

Rajnee

Hi @cgillett , thanks for link. This is similar to what multiselect filters we used. Now if you look at that page in whole, almost 40% of page is covered by multi-select filter grids. We had 2 more rows on top of this with single dropdown filters and had squeezed these multi-select grids, also had some home and other links in filter rows. Result grid here in video has only 4 columns, we had range of 10-15. Now, you can imagine, how cluttery it would look. Filters took almost 50% of screen. Now that was the issue, which could be resolved/helped once you collapse these filter rows.

cc - @daniel_bad

Quick Links

New ideas

New Module Experience - Modules Search Bar
In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds: It is not possible to search for modules in the new modules (Beta) experience. This is something that exists in the current one. How…
Virtual Data Warehouse using Anaplan metadata
We are writing from Centrify Solutions, an Enterprise Data Integration +AI company. We have developed a solution that integrates metadata from Anaplan and external sources like NetSuite into a virtual data warehouse. This creates a dynamic large language model that can be deployed internally to any data source or securely…
How CloudWorks Changed My Day-to-Day Work
Hello Everyone, I’ve been using Anaplan CloudWorks, and honestly, it has completely transformed the way I handle daily integrations. What I love most is how simple it is — you don’t need deep technical knowledge to get started. It’s simple, user-friendly, and has become an essential part of my daily workflow. If you are…