Skip to Main Content
HCL Domino 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

Status Under Consideration
Workspace Domino Designer
Created by Guest
Created on Jan 10, 2020

View: Ability to open a defined # of category levels.

It should be possible to create a button on a view that would open documents in the view a defined # of category levels. For example, open the top two levels of categories in the view.

I think that HCL should spend a lot of time improving the functionality of views. One of the advantages that views have over spread sheets is the ability to categorize multiple levels of documents. Categories are very useful but could be even more so.

The idea would be useful in helping users analyze data. In some cases the user wants to display the top category and one (or two) levels of categories beneath it. Users have asked me for this several times but I can't do it for them.

  • Attach files
  • Guest
    Reply
    |
    Jan 10, 2020

    You could use the @Command([ViewShowOnlyCategories]) in a view action button function to show only catagories, with column totals enabled to produce summary totals for a given sub catagory

  • Guest
    Reply
    |
    Jan 10, 2020

    Notes can be programmed to do the necessary calculations. The issue is how to give the user a suitable interface for selecting parameters and viewing the results.

    This is a tricky area - you need to have the type of selection and filter capabilities found in Excel (Excel 2007 would suffice). Also you would need a grid type component that does not need a document as its data source.

    Hidden views can be used to display data in embedded views - the issue is how to transition from one view/document to another. Each method requires various hoops to jump through