#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: datetime column search using @dt()

There is a view that sorts the columns displaying date and time in ascending order.
Searching this view using the following query fails:
'datetime'.DATETIME < @dt('2021-01-01')
 
The following query is fine.
'datetime'.DATETIME < @dt('2021-01-01T00:00:00.0000+09:00')
 This query is verbose.
 
I hope the first query will work.
  • Guest
  • Aug 26 2019
  • Needs review
  • Attach files
  • Guest commented
    21 Sep, 2019 12:24am

    The date and time that the end user gets from the document properties and view columns is the local time.

    Therefore, when using DQL's @Dt (), the conversion to GMT is uncomfortable.

     

    I think there should be an option to convert to local time internally.

     

    What about the idea below

    • @Dt ('2021-01-01', LOCALTIME) adds an option to convert to local time ('2021-01-01T00:00:00.0000+09:00') according to the OS time zone
    • Add a property to handle ISO format to NotesDateTime class of LotusScript.This makes it easy to convert local time to ISO format.

     

  • Guest commented
    17 Sep, 2019 07:19pm

    Spoke to soon.  We will not be in the business of filling in the +09:00 for your timezone.   Because timezone  defaults are not helpful in that operation - speaking from experience.

    - John Curtis

  • Guest commented
    17 Sep, 2019 07:15pm

    That should work in V11 at the latest.