#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

Extend the limit and include the database file name in the "Use view dialog for choices" option

The test results shows that the Dialog List Field option "Use view dialog for choices" displays a maximum of roughly 250 database names. Notably, it also doesn't specify the database file name and only includes the database titles which causes confusion as to what specific database be included.

  • Guest
  • Sep 20 2021
  • Needs review
  • Attach files
  • Guest commented
    20 Sep 06:09pm

    The "Use view dialog for choices" option for dialog list fields is excellent because it displays all the columns in the view to provide a context for the returned value. It makes it much clearer for end users to select the correct value for the field.

    However, the implementation of this feature makes it mostly worthless. Problems:

    1. The list of databases containing the lookup view is limited to only the first 250 databases bookmarked in desktop8.ndk. We need to access ALL available databases, and without any reliance on desktop8.ndk.

    2. If the designer selects a view in their desktop8.ndk but the end user doesn't also have that database bookmarked in their desktop8.ndk, the field chooser just blinks.

    3. Additionally, since only the database title is displayed to the designer, we cannot tell which database we are actually selecting for the lookup.

    These shortcomings would be overcome if the field properties would include a database chooser that permit browsing servers and NSFs. It then could perhaps store the replica ID of the chosen database. The Notes client would then display the view from any replica of the specified database - even if the end user does not already have that database bookmarked.