#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

The document properties dialog gives constant 'invalid or non-existing document' popups when clicking on a document in DQL view.

All works fine but I just have to make sure this dialog is not open when accessing an DQL view. I understand where this message comes from as the complete document properties won't be available here but there should be a workaround to suppress these messages. Luckily end users normally don't have this dialog open.

  • Guest
  • Mar 21 2022
  • Needs Clarification
  • Attach files
  • Admin
    Thomas Hampel commented
    4 Apr 08:35pm

    For reference, support tickets can be opened here: https://support.hcltechsw.com/csm

  • Guest commented
    4 Apr 07:03am

    Hi John,

    For starters, it's not a big deal for me ;) I fully understand the restriction here and don't need to see these properties there. However when this properties box is open in designer and you switch to the client to test your QRP code it will give you these constant error messages until you close the properties box. End users don't use this window I guess but if it would happen to be open at some point they would get these messages too of course and they won't understand why this happens. Now, again, no big deal, but if there would be a way to avoid the error, I don't need the properties at all there, that would be great. If of course the only way to avoid the error is to show the properties then I understand that that is a complete project again.

    Btw, I didn't see any of the demo's you refer too. That's why I asked. Sorry about that ;)

    I'm running QRP's on up to 10db's with around 100000 docs in each of them at once and it's impressive how good this works! Really happy with this.

  • Admin
    John Curtis commented
    1 Apr 04:45pm
    1. There is no such thing as a DQL view. You mean QRP view (QueryResultsProcessor view).

    2. This restriction has been demoed and explained at every point along the way. To review - since QRP views pull their data from databases other than the one they are created in, we cannot confuse the NoteIDs (which are redundant across databases) and so we manufacture artificial ones. Document properties cannot be displayed using the database housing the views. If you want to see the document, double click and open it.

    3. There is a possibility of either or both a) NOT manufacturing NoteIDs ONLY IF the QRP view's documents are all from the containing database where the view is created and b) supporting document properties across databases.

    a) could be done as a support effort but b) is a project, not a support ticket.

  • Guest commented
    1 Apr 03:25pm

    No problem! Where do I create a support ticket?

  • Admin
    Thomas Hampel commented
    1 Apr 02:55pm

    Can you please open a support ticket for this problem + add the ticket number here?