#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

Let me add @formula based calculated result columns in DQL query

there is currently the feature to tell the needed columns in a DQL request. It would be absolutely great if we could add some calculated columns to this, just like in calculated view columns. This, combined with order by will make DQL VERY powerful.

  • Guest
  • Sep 19 2019
  • Likely to implement
  • Attach files
  • Guest commented
    17 Jan, 2020 03:04pm

    So our approach for this is to let you reference Formula language entities (view columns, form fields) by NAME as we do not want to put Formula language into DQL (at least now).  They will also be allowed as sort criteria.

  • Guest commented
    21 Sep, 2019 10:33am

    I expected this to happen:
    itemNames {Array<string>}
    An optional array of item names. Use this option to read selected items. The default is to read no document items.

    Now put @formula('@Left(companyname;20)') into a list of items and you're powerful to meet the needs of your UI component without using any kind of domino design element for it.