Self created default child

[panchristo]

I have a fixed structure of related tables, forming some kind of hierarchy.

Is it possible to have a one-time default-created child together with every first child of every parent?

For example, the two last tables of my structure are SHELVES

However, because sometimes items may be stored directly on shelves and not boxes, I thought I should better solve this by storing a "dumb" box named as 0 or Shelf so it can be distinguished as a virtual box containing items on shelf level. What I need to know is if I can have this item automatically created for every shelf I create.

Or to put it in another way, automatically create a "placed-directly-on-shelf" BOX child inside a portal.

[Vaughan]

Script the record creation process. Custom menus are great for this.

[panchristo]

: Unfortunately, the record creating process is based on portals where selecting a row gets you to another layout with its children in another portal to enter directly the children. Without changing this logic is there any workaround? (by limiting access to the portal and forcing a dialog entry maybe?)

[LaRetta]

What I need to know is if I can have this item automatically created for every shelf I create.

If you script the process of creating your parent record, it can be simple as:

New Record/Request

Set Field [ Boxes::BoxNumber ; 0 ]

Since this parent has no other (multiple) children, the relationship used for your portal can also be used to create records. Now, if you do NOT want 'allow creation' turned on for your portal, just create another table occurrence of boxes called Boxes_Create and turn on Allow Creation there. When a box record is created, it will automatically add the parentID (whatever is used as the equal match between the two).

UPDATE: Even if you don't script parent record creation, your users can create an opening box but script must be done OR ... place your related Boxes::Box number on the layout and require script trigger or user to enter a 0 in it which will create the opening record. Script must test first that the child has no record yet before continuing or you could over-write exist data in the first record in boxes in the field (since Boxes is the many side).

Edited June 18, 2010 by Guest