Not present when

KnightWare

Having trouble with condition rule for the Not Present When property of a separator section on a form. The form is parent/child. On a new parent I want the child section within the separator to be "not Present". When the user saves the form (Creates the new parent), then the section should appear to enter child records. So the section is hidden on the create new, but visible once parent exists.

craigd

I was wondering about something similar. On a form, if I don't want a tab to show up if the BO is new, I tried to set the Not Present When value to

<BO> IS NEW

but no dice. I'm trying to find out what about a BO indicates that it doesn't actually exist yet. Maybe ID is UNDEFINED … ?

KnightWare

Figured it out - my crazy way.

On the Parent, named PROPERTY, BO I added a new attribute "CreateDate". I added a business rule to the create/modified rules of the form to populate with CURRENT_DATE when the condition IS NEW. I set the form Initialization property of the rule to "FALSE" so it populates on the Create (save).

On the Child section, Separator (TENANTS), I added to the "Not Present When"
NOT (ThisPROPERTY.CreateDate IS DEFINED)

So now , until I Create (save) the parent, the section remains hidden. Once I saved it the separator section opened and I can add the child (Tenant) records.

PointsWell

KnightWare wrote
On the Child section, Separator (TENANTS), I added to the "Not Present When"
NOT (ThisPROPERTY.CreateDate IS DEFINED)
.

Out of interest does it work with
“Not Present When”
ThisPROPERTY.CreateDate IS UNDEFINED

Only asking because dates and Undefined are curious in Queries ie a FIND x where x.date is UNDEFINED doesn’t give expected results (and also NOT NOTs can become mind bending when you read them 6 month later.)

tford

NOT (ThisPROPERTY.CreateDate IS DEFINED)

You could probably also use: PROPERTY.CreateDate IS UNDEFINED

As a side note, I often find when I have a parent / child situation, I need to periodically know the # of child instances owned by a parent. So I typically add an attribute Parent.NbrChildren & add a rule that maintains the # of children. In your scenario, this counter could potentially be used to control visibility.

KnightWare

Yes - Works both ways. Changed to
ThisProperty.CreateDate IS UNDEFINED

And works perfectly.

tford

The prefix "This" should not be needed.

KnightWare

You are correct. Lot's of left-overs from trial and error development.