#dominoforever | Product Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Add view filter option to columns, where user can select documents to be displayed

You might know filter option in LibreOffice or Excel, where user can reduce the shown documents to selected values.

Of course, this can also be done by using a search formula, but most users are not experienced with the syntax of notes search.
Adding this feature will simplify the usage for users and it might also help to reduce the number of required views in a database.

When a filter is active, calculated summary and totals in categorized views should base on current shown documents.

  • Guest
  • Aug 5 2018
  • Assessment
  • Attach files
  • Guest commented
    6 Nov, 2021 08:17pm

    Is there any news on this idea?

    We are struggeling with the lack of client side filtering in views forever.

    There are a lot of workarounds with private views, embedded views with single category, @SetViewInfo and so on but none of them work well.

    We are about to drop Notes just because of this.

  • Guest commented
    7 Jul, 2020 07:28am

    Hi there, such a feature would be great indeed. I think implementing something similar like @SetViewInfo in LS could be done on the client.

    But if you want a more complex filter I asumme that a pure implementation on the client would come with a heavy time penalty, as it would have to read lots of documents first.

    Especially in the home office latency between the docs could add up signifcantly. In this case it would be better to give the filter to the server, which then would search and send only the docs concerned back. That would give a good performance.

    I start to love this idea.


  • Guest commented
    6 Jul, 2020 07:14pm

    Ok, I have the idea. We will ruminate on it a bit and I will pass it along.

  • Guest commented
    6 Jul, 2020 06:32pm

    Hi, John I understand that you say, I'm programmer and I make a complex view . THe proposal is when you've the information and you want to see the same information for a lot of points of views this suggestion are very good.

    I put an example, a sales of company, you want to see by countries, by departments, which customers sells more this quantity, an specific country and department check, and more combinations. The solution is making a lot of views.

    I know the spreadsheets there're functions that is more difficult implement in Lotus for example accumulative in one year.

    The idea is filter documents and hide the documents that there arent in the filter. I believe this idea is good for us.

  • Guest commented
    6 Jul, 2020 06:25pm


    Personally I'm talking of the full Notes client. I'm not experienced on Nomad enough, and on interacting with the finger to have an idea there, but it would make sense as well.

    IMHO, in terms, if I want to restrict what is shown from a categorised view, I'd want to place the cursor bar on the category/subcategory, and having it available on a keyboard combination for example CTRL+ to activate and CTRL-, as we already + and - for single category and SHIFT for all categories expand/condense would be somehow logical.

    The 'classical' Notes programmer if I want to restrict what is shown from a categorised view, I'd want to place the cursor bar on the category/subcategory, and via an action button select it, which means some @Formula and/or LS Property and or Method to programm that.

    This would be like Christmas to me and many other developpers !

  • Guest commented
    6 Jul, 2020 05:59pm

    LIFO - it's what I do :-)

    What is the UI you're suggesting? The Notes Client/Nomad/WebAsm client? Or another web-based technology?

    I can't find the Screenshot-Example, but I think I understand your intent from your comments. Though I am not sure if it's a client enhancement or back-end support (where I mostly work).

    It does sound like we have existing capabilities in core Domino to supply this capability, but I need the UI venue suggested.

  • Guest commented
    6 Jul, 2020 04:16pm

    Hi John,

    the intended idea was really that those filters work like in an spreadsheet application.

    (Have another look at the attached Screenshot-Example, it might be more clear then).

    The big benefit is: There is no learning curve for users to know a search syntax or internal field names,.... the user just selects from the values of a column which documents he wants to see. And it should work just as a temporary filter for this users current view. So it's probably a thing to solve on client side and does not affect built index on server side.

    Of course, for developers it would be great to have functions and classes to takeover those filter functions into their applications ... but that's another challenge.

    Just come back to me if further clarifications needed. Thanks for making Notes/Domino great again!

  • Guest commented
    6 Jul, 2020 02:29pm


    I do see your point and agree : there is no wish to change the views. They are one big advantage Notes has, so this is not something I feel needs to change at all.

    The reference to spreadsheets I read and hear are all coming because users tend to compare what they see and are mostly totally unaware of the technical stuff behind it. So they compare and look for features they don't find. And I've had customers happy to move excel data to a Notes Db because of the views as well... and one of the pain points is this one.

    And yes, what I feel (and I guess others as well) is needed is an easy way to get and present a subset in the same format and having it available in the same UI.

    We did try to simulate that with folders, but how do you move a few thousand documents to a folder without seleting them on the left margin ? You need coding. And it comes with its challenges and overhead

    @Set/GetInfo, is adapted to that global vision you clearly outlined : it works within that logicial frame. However it needs coding and has no equivalent in LS.

    Having databases with tens of thousands of documents and hundreds of categories and sub-categories with documents present in multiples of them, we search for ways to make it easier for users to get to focus on a part of the data sets and then do what they need on their own. At present we need to hard code functions whenever the need arises - and customers have the knack of always wanting something new in terms of reports and extraction...

  • Guest commented
    6 Jul, 2020 02:16pm

    In the views filter i can find a field that equal a <blanc> or equal to error because I can't find. For the user is a bit complicate because they don't know the internal fields. I'd like a easy way to make filters, the idea of spreadsheets of excel is very great and if it could apply in Lotus could be fantastic.

  • Guest commented
    6 Jul, 2020 01:59pm

    No, views as they exist (not as we are envisioning them herein) are NOT like spreadsheets. They are like the database indexes used to POPULATE spreadsheets. They are persistently-refreshed indexes, quickly navigate by use of ordinal positions. That navigation (which goes horizontal as well) is extremely powerful and we intend to keep/leverage it.

    @Set/GetViewInfo works with such persistent structures (view indexes) as well, though it filters by category. And they do NOT change the column formulas. They present persistent index data without changing it according to context.

    Aggregates (average, sum, max, min, count, stdev,, etc.) are persistent as well in views; and that is not helpful when you choose subsets (or reader lists do it for you).

    What I hear is the need for a less persistent data store mechanism to supply subsetting capabilities. All the while maintaining the power of views.

  • Guest commented
    6 Jul, 2020 11:30am

    Hello John,

    I believe it needs to be both, and I am basing my suggestion on categories/sub-categories

    1) user can for example place cursor bar on a category or sub.category and the view is automatically restricted to showing that category/sub-category - stays open the question of documents present in several subcategories. This would be the easiest way of doing it.

    Choose the line, click on a button and you've got your 'selection' vsible without any fuss. Some mechanisms is then needed to go back to full view. Just easy, quick and no fuss.

    2) any totals ought to reflect what is visible in the view once the restricted view is visible, not taking into account the rest, so just the subset of documents.

    This ties in to @SetViewInfo/@GetViewInfo suggestions present on this ideas blog. We Notes developpers, would love so much and need so much a way to do this in LS so as developper we can present subsets easily (by date, by user, by whatever value without having to live with the 15 cm limit (and others) of integrated views. We are taking so much flack because this is not possible in Notes... and it is possible in Excel or LibreOffice : users compare and tend to forget processes ...

    Categories and sub-categories in Notes Views are such a powerful way to present information, and a unique one as well. It is what makes Notes so powerful when handling big datasets.

    So having a similarly easy and powerful way to show a subset is a big miss, need and hope !

    Some users are using the search feature as they are used in gmail...this sometmes gives strange results in terms of what appears on the screen especially in categorised views. But ther as well, you make a search and the totals ought to reflect the found documents.

    In VOLT there is a fliter feature that is nice for basics. Getting this kind of filter available would be a nice add-on as well.

  • Guest commented
    6 Jul, 2020 11:09am

    I understood the view works as like as excel, you can make filters you can sort for different ways and for see all information you don't need a lot of view, with one view you can find the documents that you want easy. Now a lot of people export the views to excel and with excel search the information. This I'd like to avoid, I think this change is very important.

  • Guest commented
    6 Jul, 2020 10:58am

    I need some more clarity on this. Is this is a filter of documents displayed or a filter of what gets displayed at the column level, or both?

  • Guest commented
    26 Jun, 2019 11:32am


  • Guest commented
    15 Oct, 2018 09:27am

    This is a very good idea. We need this function quite urgently in the current project