#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

DQL: improvements on named variable handling and on documentation

Playing around with DQL, and especially with NamedVariables.

The NotesDominoQuery class at the moment has 2 methods dealing with named variables:

DQL.setNamedVariable("name", "value")


The more I try to use that concept the more I need to know which variable names have been defined so far. That in my opinion calls for a getter method like

Variant names = DQL.getNamedVariables()

Result could also be JSON, text list, or whatever you feel appropriate, then not only containing the names but also the values.

And following up on this this calls out to methods to remove individual names:


In regards to documentation: information on NamedVariables is extremely basic (trying to be polite). Up to now I want these questions answered:

  • is it correct to assume that NamedVariables are stored in the design catalog?

  • is it valid only for a single database?

  • is it replicated?

  • what is the life span of a NamedVariable?

  • are there any known limitations in regards to sizes, data types, number of characters, whatever

More questions are likely to come up as I continue to work with that stuff.

Keep up the good work!

In case direct feedback is needed: lothar.mueller@edcom.de

  • Guest
  • May 10 2022
  • Needs Review
  • Attach files