Disabling Child Objects

PointsWell

I have a very complex process for the creation of Contacts which I achieve by creating a Header record which has a series of os child relationships depending on the type of the Contact.

Once I have determined what the type of the Contact is I then set all of the unneeded os child objects to be READ PROTECT.

For example:

If ContactHeader.Type=x THEN 
READ PROTECT ContactHeader.osY FROM ALL
READ PROTECT ContactHeader.osZ FROM ALL
If ContactHeader.Type=y THEN 
READ PROTECT ContactHeader.osX FROM ALL
READ PROTECT ContactHeader.osZ FROM ALL
... etc

What I am finding is that even though a child os record is never created AIM is running all of the rules as if it were.

Any suggestions as to how to prevent this unnecessary processing as it has an overhead on the create process.

tford

Confused.

One one hand you say that the child records are in fact created, but just hidden via READ PROTECT:

Once I have determined what the type of the Contact is I then set all of the unneeded os child objects to be READ PROTECT.

Then you stating that child records are never created:

What I am finding is that even though a child os record is never created AIM is running all of the rules as if it were.

PointsWell

Confused? You and me both.

So the process is:

Create Header, then based on values of Header create ONE of X, Y or Z as Header.osX or Header.osY or Header.osZ.

So there are only ever two records (in this simplified example).

AIM however seems to think that there are 4 BOs Header, X, Y and Z as it is running all of the business rules related to all of the BOs.

At no time however does it appear that the BOs are created in the database. So I am kinda perplexed as to what is going on here. Hence in an attempt to prevent this happening I have created READ PROTECTs against the attributes of the unwanted Child records

e.g. If Header has Header.osX I have then attempted to hinder the visibility of the records oxY and osZ.

There is a secondary need to hide the unwanted child record as I have an HTML form demonstrating progress through the creation path (this simulating a wide record which is in reality broken up into a number of related sub records, though the elements in the record will change depending on the type of Contact that I am creating. So for example Companies have subsidiaries and employees, Clients people do not).

tford

Not sure what to tell you, but I think you'll find if you get under the hood that the "extra" records are in facts being created or the rules wouldn't be executing. READ PROTECT isn't going to solve that.