Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only
Back to discussions
Expand all | Collapse all

MAXIMO DATETIMESTAMP IN THE JSON PAYLOAD FOR MAXIMO OSLC JSON REST API

  • 1.  MAXIMO DATETIMESTAMP IN THE JSON PAYLOAD FOR MAXIMO OSLC JSON REST API

    Posted 11/08/21 07:32 PM
    Hello,

    We do the integration with MAXIMO and other business applications using OSLC JSON Rest API.

    For updating rows in MAXIMO, we set the value of the MBO's columns with datetime stamp with the following format: 

    '%Y-%m-%dT%H:%M:%S-07:00  (i.e. 7 hours behind UTC). 

    However from yesterday (until the day light saving begin), it is 8 hours behind UTC.

    Does this mean that we need to keep maintaining the code that produces the JSON Payload for -7:00 or -8:00.

    Is there any other format or way which will work irrespective of day light saving start/ends?

    Pankaj Bhide


    ------------------------------
    Pankaj Bhide
    Associate/Analyst
    Berkeley National Laboratory
    Berkeley CA
    (510) 486-4681
    ------------------------------



    #AssetandFacilitiesManagement
    #MaximoIntegrationandScripting
    #Maximo


  • 2.  RE: MAXIMO DATETIMESTAMP IN THE JSON PAYLOAD FOR MAXIMO OSLC JSON REST API

    Posted 11/09/21 07:31 AM
    You aren't required to provide the offset (IE -07:00). If you don't provide the offset it would use the user's time zone (or system time zone if the user doesn't have one configured). For the REST API this would be the user you're authenticating as/created an API key for but for a standard integration this would typically be MXINTADM. As long as you don't need to support multiple time zones, I would just avoid sending the offset.

    ------------------------------
    Steven Shull
    ------------------------------



Related Content