HCL Domino 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

Add a new idea Subscribe
Status Under Consideration
Workspace Domino
Categories Integration
Created by Guest
Created on Oct 15, 2021

RELATED IDEAS

Date/Time on JSON Domino Access Services converted to UTC

There are uses on REST API to retrieve data from documents but the problem is the data (date/time) returned as they are always converted to UTC time zone regardless of what is on the field


From checking this is working as designed as JSON specs dictates the dates to be always in UTC.


It would be helpful if we can set parameters/query on REST to indicate timezone for accurate data

  • Attach files
  • Guest
    Reply
    |     Oct 18, 2021

    Here is an example:


    {

    "@href": "/dev/datetime.nsf/api/data/documents/unid/349861C0C3B785958025876E004D7C35",

    "@unid": "349861C0C3B785958025876E004D7C35",

    "@noteid": "90E",

    "@created": "2021-10-14T14:06:20Z",

    "@modified": "2021-10-18T11:49:43Z",

    "@authors": "CN=....",

    "@form": ".Invoice",

    "ComposeDate": "2021-10-14T10:24:00Z"

    }


    From the document properties the actual value for ComposeDate is 14/10/2021 12:24:00 ZE2 meaning that the Document GET is lossful and the actual value of the ComposeDate field cannot be determined.

    This makes using Domino Access Services for accurate date processing impossible.


    Please implement a fix to resolve this problem.


Copyright © 2023 HCL Technologies Limited