#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

Storing DQL Query Document Collection Results as a Collection of Document IDs

After a DQL query has been performed, there needs to be the ability to store the results for later use.  Since the results of a DQL query is a Notes Document Collection, the ability to store the results as as collection of document IDs in a document is important.  There is the need to store these collections for later interpretation and analysis. Currently, you need to run the query again.  For auditing purposes the collection would have changed if the data changes and would not reflect the query performed on the original date. This feature needs to be accessible using Java and LotusScript.  The results should include history data about the query.

  • Guest
  • Mar 25 2019
  • Under Consideration
  • Attach files
  • Guest commented
    17 Jan, 2020 03:06pm

    This is in plan, absolutely.  Refreshable results even.

  • Guest commented
    25 Mar, 2019 06:16pm

    The returned array has @UNID for each document. There's nothing to prevent you from storing that array in a variable in the app, to a file, to other storage used by the app, or to write to a Notes document (profile) if that's what you want. I don't understand what additional functionality would provide or why it's necessary.  Maybe I'm missing something.

  • Guest commented
    25 Mar, 2019 02:27pm

    We have tried to use folders to store the document collection, but that is not usable at all since that is an extremely slow process.Competitive databases like MongoDB and CouchBase already have this capability.