Maximo

I'm not entirely sure how you're displaying the data but if you are trying to display all child WOs and all tasks of the WO on the same page, you would likely have a data-list of showchildrenwo and an additional data-list for the tasks. If that's the case, you can set the datasource to something like this:

Hello Steven,

Thanks for the Response.

I am trying to display all the child work orders in one page(similar to Schedule Page) and their respective tasks in a different page.

I have found a different way to load the woactivity array into a datasource of tasks page using js code but I gave a try of getChildDatasource method also but somehow getting error as getChildDatasource is not a function of showchildrenwo datasource.

Also I have observed that I am not able to access all the attributes of woactivity like description_longdescription  even though woactivity is defined to fetch all the attributes as name="rel.woactivity{*}" .

Could you please help here.

Thanks again !

I'm not entirely sure how you're displaying the data but if you are trying to display all child WOs and all tasks of the WO on the same page, you would likely have a data-list of showchildrenwo and an additional data-list for the tasks. If that's the case, you can set the datasource to something like this:

You never want to retrieve all attributes but certainly not on an object like WOACTIVITY where there are going to be literally hundreds of attributes. There's overhead in building that data (all the attribute initialize events will fire), downloading that data (a much larger dataset than the application needs), and memory utilization on the device to load that data into a datasource. 

The REST API using the asterisks on a relationship does not seem it will retrieve non-persistent attributes on a persistent object. You have to define the specific attributes you want. Most non-persistent attributes on a persistent object are used for specific operations (such as supporting asset move/modify) so it would make sense to not fetch them. If you specifically call out description_longdescription, it will return in the select (provided that it is not null since we drop nulls by default to reduce the size of the payload). 

Hello Steven,

Thanks for the Response.

I am trying to display all the child work orders in one page(similar to Schedule Page) and their respective tasks in a different page.

I have found a different way to load the woactivity array into a datasource of tasks page using js code but I gave a try of getChildDatasource method also but somehow getting error as getChildDatasource is not a function of showchildrenwo datasource.

Also I have observed that I am not able to access all the attributes of woactivity like description_longdescription  even though woactivity is defined to fetch all the attributes as name="rel.woactivity{*}" .

Could you please help here.

Thanks again !

I'm not entirely sure how you're displaying the data but if you are trying to display all child WOs and all tasks of the WO on the same page, you would likely have a data-list of showchildrenwo and an additional data-list for the tasks. If that's the case, you can set the datasource to something like this:

Yes, it worked if I specifically call out only required fields. Thanks Again!

Could you please clarify one more doubt here.

With respect to my child datasource of showchildrenwo , I had to define relationship as "showchildren.mxapiwodetail"  instead of "showchildren".

With the latter approach, rel.woactivity on showchildrenwo was undefined ,but the other 1:1 relationships were working fine.

Is it for Multi line relationships like woactivity , are we supposed to use <relationshioname.Objectstructurename>  or is there any other criteria?

Thanks

You never want to retrieve all attributes but certainly not on an object like WOACTIVITY where there are going to be literally hundreds of attributes. There's overhead in building that data (all the attribute initialize events will fire), downloading that data (a much larger dataset than the application needs), and memory utilization on the device to load that data into a datasource. 

The REST API using the asterisks on a relationship does not seem it will retrieve non-persistent attributes on a persistent object. You have to define the specific attributes you want. Most non-persistent attributes on a persistent object are used for specific operations (such as supporting asset move/modify) so it would make sense to not fetch them. If you specifically call out description_longdescription, it will return in the select (provided that it is not null since we drop nulls by default to reduce the size of the payload). 

Hello Steven,

Thanks for the Response.

I am trying to display all the child work orders in one page(similar to Schedule Page) and their respective tasks in a different page.

I have found a different way to load the woactivity array into a datasource of tasks page using js code but I gave a try of getChildDatasource method also but somehow getting error as getChildDatasource is not a function of showchildrenwo datasource.

Also I have observed that I am not able to access all the attributes of woactivity like description_longdescription  even though woactivity is defined to fetch all the attributes as name="rel.woactivity{*}" .

Could you please help here.

Thanks again !

I'm not entirely sure how you're displaying the data but if you are trying to display all child WOs and all tasks of the WO on the same page, you would likely have a data-list of showchildrenwo and an additional data-list for the tasks. If that's the case, you can set the datasource to something like this:

Without testing it I can't explain why but defining an object structure in the relationship shouldn't be required in this case. The use case of returning data using a specific object structure is to handle processing rules that may be set on the object structure.

For clarity though, it is possible woactivity is null on either approach because we drop nulls in the REST API and it is not a requirement that a task has to exist on a WO. The getChildDatasource works whether it exists in the data or not. 

Yes, it worked if I specifically call out only required fields. Thanks Again!

Could you please clarify one more doubt here.

With respect to my child datasource of showchildrenwo , I had to define relationship as "showchildren.mxapiwodetail"  instead of "showchildren".

With the latter approach, rel.woactivity on showchildrenwo was undefined ,but the other 1:1 relationships were working fine.

Is it for Multi line relationships like woactivity , are we supposed to use <relationshioname.Objectstructurename>  or is there any other criteria?

Thanks

You never want to retrieve all attributes but certainly not on an object like WOACTIVITY where there are going to be literally hundreds of attributes. There's overhead in building that data (all the attribute initialize events will fire), downloading that data (a much larger dataset than the application needs), and memory utilization on the device to load that data into a datasource. 

The REST API using the asterisks on a relationship does not seem it will retrieve non-persistent attributes on a persistent object. You have to define the specific attributes you want. Most non-persistent attributes on a persistent object are used for specific operations (such as supporting asset move/modify) so it would make sense to not fetch them. If you specifically call out description_longdescription, it will return in the select (provided that it is not null since we drop nulls by default to reduce the size of the payload). 

Hello Steven,

Thanks for the Response.

I am trying to display all the child work orders in one page(similar to Schedule Page) and their respective tasks in a different page.

I have found a different way to load the woactivity array into a datasource of tasks page using js code but I gave a try of getChildDatasource method also but somehow getting error as getChildDatasource is not a functio