The developerWorks Connections Platform is now in read-only mode and content is only available for viewing. No new wiki pages, posts, or messages may be added. Please see our FAQ for more information. The developerWorks Connections platform will officially shut down on March 31, 2020 and content will no longer be available. More details available on our FAQ. (Read in Japanese.)
with Tags:
child
X
X
Marking Main Record as Modified while Modifying Related (Child) Records via Automation Scripts (v7.6)
When you modify, i.e. add/update/delete, child records (MBOs) related to a main record, the parent object might not always require saving, in other words it might not always get marked as "Modified". For default applications, the application forces the user to SAVE the main record because this functionality is implemented in the original MBO classes of Maximo. Unfortunately, when you have your custom objects used in your custom applications, you can face such use cases that you modify the child records and the main record is not... [More]
Tags: controldesk+7.5 modified parent maximo modify mainrecord related child update save add maximo+7.6 delete maximo+7.5 controldesk+7.6 controldesk |
Show the assets child record attachments in parent asset record
Some user would like to view all the attachments being added over the Child records to be visible over the Parent records in applications wherever the attachment provision is present. For you to be able to see the children attachments in the parent asset you have to add a where clause to the relationship. Please do the following steps: 1. Go to Database Configuration application 2. Bring up ASSET object 3. Select the Relationships tab and filter by DOCLINKS 4. Add the following to the end of the relationhip: or (ownertable =... [More]
Tags: child ibm-blog attachment parent asset |
A Scripting Solution to Set Child Work Order Values From the Parent
Introduction Crossover domains can be a convenient way to copy values from a parent work order to a new child when adding a child work order. In most cases this works without a problem. However, if the values being copied from parent to child include ASSETNUM, LOCATION, and/or GLACCOUNT, the crossover domain may not work as expected. This is the case if these values do not match, for example, if the ASSETNUM does not reside at the location specified by LOCATION, or if the GLACCOUNT does not match the ASSETNUM/LOCATION combination. This... [More]
Tags: bmxaa4721 domain duration crossover autoscript bmxaa4195e parent child script bmxaa4722 bmxaa4510 workorder automation requires |
