This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
In Maximo 6.2, I have several clones of Work Order Tracking that serve as forms to fill out to capture relevant data in different circumstances (the type of work done. . .Corrective Maint vs. Event Setup vs. whatever).
In Maximo 7.6, since it now has Conditional Expressions, I want to consolidate it all down to one form that dynamically changes based on workorder.worktype. I've got the basics of it working, but I'm having a problem.
In 6.2, one of the forms has several tabs. Two tabs each have a copy of the Child Work Orders child table (the table you'd find in Work Order Tracking on the Plans tab, and not the Tasks table). So one of those tabs are intended to be instructions for the SETUP of an event, the other is for the TEARDOWN (undo the setup) of the event. So I have an event as the parent work order, and there should be at least one child setup and one child teardown. I want the hierarchy in this way so costs roll up, and the children this way so status and scheduling can be tracked separately. And I want the children to be able to be viewed separately, at least at the time the work order is being entered.
Normally, that relationship is SHOWCHILDREN. In 6.2, I made it work by, in Application Designer, making the tab, copying in the Child Work Orders table, giving the table a Default Value on Insert for the Description, and making a relationship (in DB Configuration) like the existing SHOWCHILDREN, but adding that defaulted Description to the Where Clause. And repeating for the second tab, with a different default, and therefore a different Relationship.
Now in 7.6, I can't get it to work. If I change the Relationship from SHOWCHILDREN, it shows no rows on existing records and it won't insert new rows correctly. If I leave it as SHOWCHILDREN, then it shows all rows; it won't separate them. I have tried also adding a Default Value filter on each table On Query, and I have tried adding a Where Clause in the table control's Advanced Properties, Application Listeners.
The only other difference between the 6.2 version and the 7.6 version that I can think of as relevant is that I've put both tables on the same tab. In the same section container even. And, as a result, when I add a row in the first table, it has its Description set to the Default Value from the 2nd table (and if I add a row to the 2nd table, it gets the Default Value from the 2nd table).
Any helpful hints as to what I'm doing wrong?
Travis Herron
Hi Travis,
Check the relationship's where clause "showchildren" v7.6 & v6.2
Regards,
Pietter Mulyono
On 18 Aug 2017 12:43 am, "therron@pcci.edu [MAXIMO]" <MAXIMO@yahoogroups.com>
wrote:
In Maximo 6.2, I have several clones of Work Order Tracking that serve as
forms to fill out to capture relevant data in different circumstances (the
type of work done. . .Corrective Maint vs. Event Setup vs. whatever).
In Maximo 7.6, since it now has Conditional Expressions, I want to
consolidate it all down to one form that dynamically changes based on
workorder.worktype. I've got the basics of it working, but I'm having a
problem.
In 6.2, one of the forms has several tabs. Two tabs each have a copy of the
Child Work Orders child table (the table you'd find in Work Order Tracking
on the Plans tab, and not the Tasks table). So one of those tabs are
intended to be instructions for the SETUP of an event, the other is for the
TEARDOWN (undo the setup) of the event. So I have an event as the parent
work order, and there should be at least one child setup and one child
teardown. I want the hierarchy in this way so costs roll up, and the
children this way so status and scheduling can be tracked separately. And I
want the children to be able to be viewed separately, at least at the time
the work order is being entered.
Normally, that relationship is SHOWCHILDREN. In 6.2, I made it work by, in
Application Designer, making the tab, copying in the Child Work Orders
table, giving the table a Default Value on Insert for the Description, and
making a relationship (in DB Configuration) like the existing SHOWCHILDREN,
but adding that defaulted Description to the Where Clause. And repeating
for the second tab, with a different default, and therefore a different
Relationship.
Now in 7.6, I can't get it to work. If I change the Relationship from
SHOWCHILDREN, it shows no rows on existing records and it won't insert new
rows correctly. If I leave it as SHOWCHILDREN, then it shows all rows; it
won't separate them. I have tried also adding a Default Value filter on
each table On Query, and I have tried adding a Where Clause in the table
control's Advanced Properties, Application Listeners.
The only other difference between the 6.2 version and the 7.6 version that
I can think of as relevant is that I've put both tables on the same tab. In
the same section container even. And, as a result, when I add a row in the
first table, it has its Description set to the Default Value from the 2nd
table (and if I add a row to the 2nd table, it gets the Default Value from
the 2nd table).
Any helpful hints as to what I'm doing wrong?
Travis Herron
I did, and they are exactly the same. But as an added bonus, I can't begin to imagine how that relationship actually works. It's a join from WORKORDER to WORKORDER as
parent = :parent and siteid = :siteid and istask = no
Shouldn't it be parent = :wonum?
Pretty sure that's a rhetorical question. Which makes me think it is actually handled in the Java code somehow.
I'm going to be trying a radically different approach today, since I can't get this working.
Travis Herron
"Two tabs each have a copy of the
Child Work Orders child table (the table you'd find in Work Order Tracking
on the Plans tab, and not the Tasks table)"
What's that definition, since all of your workorder data is coming from the same table? Your relationship is definitely not correct.
-C