Hello everyone,

I have a problem when adding a record in the labtrans object using a webservice.

Usually when you put a date in the future Maximo wont accept it:


When trying to do the same thing with a webservice, the validation is not working:


So the actual labor record is added in Maximo when it shouldnt:



Does anyone know why the date is not validated when using webservice?

Thanks in advance.

(English is not my main language, apologies for the grammar).

Regards,
Arturo Carmona

------------------------------
Arturo Carmona
------------------------------

#AssetandFacilitiesManagement
#Maximo

Can you try and utilize the STARTDATE & STARTTIME fields instead of STARTDATEENTERED? You may need to include them on the object structure since they're non-persistent attributes.

Historically, this was always managed as the STARTDATE & STARTTIME fields. The problem was that when a date and time were provided in a system used across time zones the dates wouldn't be adjusted for that user's time zone. This made it difficult to know when the work was actually performed (was it 10 AM Eastern, Central, Pacific, etc.). So in the 7.6 release we made some changes to be able to adjust it for the user's time zone (see this technote that walks through it https://www.ibm.com/support/pages/labtransstartdate-non-persistent-maximo-76 ). On the screens we still displayed STARTDATE & STARTTIME and collect it as two separate values. This gets stored in a couple of persistent attributes: STARTDATEENTERED, STARTTIMEENTERED, and most importantly, STARTDATETIME which is a complete date/time that we can adjust for the user's time zone.

But a user should not be setting these new persistent attributes directly. They should be utilizing the STARTDATE & STARTTIME non-persistent attributes. These attributes are what we review during the save for compliance with the labor tolerance. My guess is these non-persistent attributes are not set so we don't try to validate the tolerance.

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

Hello Steven,

Sorry for the late answer but we already tried ur solution and it worked great!

Thanks for the help.

Regards,
Arturo Carmona

------------------------------
Arturo Carmona
------------------------------

Original Message:
Sent: Thu May 26, 2022 02:10 PM
From: Steven Shull
Subject: Actual labor dates not validating when using webservice

Can you try and utilize the STARTDATE & STARTTIME fields instead of STARTDATEENTERED? You may need to include them on the object structure since they're non-persistent attributes.

Historically, this was always managed as the STARTDATE & STARTTIME fields. The problem was that when a date and time were provided in a system used across time zones the dates wouldn't be adjusted for that user's time zone. This made it difficult to know when the work was actually performed (was it 10 AM Eastern, Central, Pacific, etc.). So in the 7.6 release we made some changes to be able to adjust it for the user's time zone (see this technote that walks through it https://www.ibm.com/support/pages/labtransstartdate-non-persistent-maximo-76 ). On the screens we still displayed STARTDATE & STARTTIME and collect it as two separate values. This gets stored in a couple of persistent attributes: STARTDATEENTERED, STARTTIMEENTERED, and most importantly, STARTDATETIME which is a complete date/time that we can adjust for the user's time zone.

But a user should not be setting these new persistent attributes directly. They should be utilizing the STARTDATE & STARTTIME non-persistent attributes. These attributes are what we review during the save for compliance with the labor tolerance. My guess is these non-persistent attributes are not set so we don't try to validate the tolerance.

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