Hi,

I'm building a solution for a client, i have a child table which is defined as per below. It seems like when there is an error in a record in that child table, i go to the errored record. Whether i fix the data or not and resend it, the data in the child records is lost, looking at the JSON sent to Maximo its not there, so then the child record isn't created in Maximo, and disappears from the device as its refreshed.

<attribute describedByProperty="spi_wm:woinspect{spi_wm:insprole}" id="workOrder_roleobserved" name="roleobserved"/>

I spoke with IBM support and was informed this wasn't a supported customization, however its detailed in the development guide how to use records in other tables.  There is no issue getting the data from Maximo, its just the first record creation failure that loses the data you entered in that child table record.  I am wondering if anyone has had similar experience?

Thanks
Nicky

------------------------------
Nicky Rhodes
------------------------------



#AssetandFacilitiesManagement
#MaximoAnywhere
#Maximo

Hi Nicky,

The code you've sent is like a Maximo relationship, it can't create what's not there.

If I read correctly, you are trying to update a field that is not on the work order, but is on a child object.  Essentially it's reference only.  I'd love to know what is your reference as there is not much written on the customisations.

In most cases you have to navigate to a new view that references the other object in order to update it, like with labor or meters.

What is the error BTW?

------------------------------
===============================
Craig Kokay,
Lead Senior Maximo/IoT Consultant
ISW
Sydney, NSW, Australia
Ph: 0411-682-040
=================================
#IBMChampion2021
------------------------------

Hi Craig,

Thanks for the reply.  The use case is that my client is using an extension table for Work Orders.  So they have 100+ attributes on that table, some of which i need for the Work Execution app.  They are able to create a work order on the app, and i need to be able to populate those attributes.  Currently using the method above it works just fine, it doesnt work however if the record errors out on the first try.  

There's no error unfortunately, when you hit the resend button it just doesnt send the sub object the second time around, which is then subsequently lost, and replaced by the response from maximo.  It would seem to be a bug with the framework, where by on resend it doesnt see that the extension table object is modified still.  

Thanks
Nicky

------------------------------
Nicky Rhodes
------------------------------

Original Message:
Sent: Fri November 05, 2021 08:00 AM
From: Craig Kokay
Subject: Using Maximo Extension table - records get lost when erroring on creation

Hi Nicky,

The code you've sent is like a Maximo relationship, it can't create what's not there.

If I read correctly, you are trying to update a field that is not on the work order, but is on a child object.  Essentially it's reference only.  I'd love to know what is your reference as there is not much written on the customisations.

In most cases you have to navigate to a new view that references the other object in order to update it, like with labor or meters.

What is the error BTW?

------------------------------
===============================
Craig Kokay,
Lead Senior Maximo/IoT Consultant
ISW
Sydney, NSW, Australia
Ph: 0411-682-040
=================================
#IBMChampion2021
------------------------------

Just to follow up with this.  I have got this working.  Essentially you have to put in a handler to force the ID record of the sub table to be modified.  That way it sends back the ID with the payload and the standard MIF will deal with it as an update.

------------------------------
Nicky Rhodes
------------------------------

Original Message:
Sent: Fri November 05, 2021 10:10 AM
From: Nicky Rhodes
Subject: Using Maximo Extension table - records get lost when erroring on creation

Hi Craig,

Thanks for the reply.  The use case is that my client is using an extension table for Work Orders.  So they have 100+ attributes on that table, some of which i need for the Work Execution app.  They are able to create a work order on the app, and i need to be able to populate those attributes.  Currently using the method above it works just fine, it doesnt work however if the record errors out on the first try.  

There's no error unfortunately, when you hit the resend button it just doesnt send the sub object the second time around, which is then subsequently lost, and replaced by the response from maximo.  It would seem to be a bug with the framework, where by on resend it doesnt see that the extension table object is modified still.  

Thanks
Nicky

------------------------------
Nicky Rhodes
------------------------------


Original Message:
Sent: Fri November 05, 2021 08:00 AM
From: Craig Kokay
Subject: Using Maximo Extension table - records get lost when erroring on creation

Hi Nicky,

The code you've sent is like a Maximo relationship, it can't create what's not there.

If I read correctly, you are trying to update a field that is not on the work order, but is on a child object.  Essentially it's reference only.  I'd love to know what is your reference as there is not much written on the customisations.

In most cases you have to navigate to a new view that references the other object in order to update it, like with labor or meters.

What is the error BTW?

------------------------------
===============================
Craig Kokay,
Lead Senior Maximo/IoT Consultant
ISW
Sydney, NSW, Australia
Ph: 0411-682-040
=================================
#IBMChampion2021