Well-Positioned Buscomps

A well-positioned Buscomp is a Buscomp that has been positioned correctly, and whose position should not be disturbed. DTU uses the following rule:

• The initiator Buscomp is a well-positioned Buscomp.

• The ascendants of a well-positioned Buscomp are well-positioned.

• For a given data map component, the buscomps involved in all its parent data map components are well positioned.

If the source Buscomp is well-positioned:

• Data transfer is only invoked on the current row of the source BusComp. Otherwise, the operation is carried out on all rows in the source BusComp at the moment of invocation.

• Advanced options such as source search spec, source sort spec should be empty.

If the destination Buscomp is well-positioned:

• You do not need to specify key fields to retrieve the destination record. Even if you do in this case, DTU would ignore them.

• And if the current operation is Insert, it would change to Update by default, unless overridden by Operation Overrides.

Example of Buscomp That is Not Well-Positioned

Calling the DTU Data Transfer method from an applet that is based on buscomp Quote, but which has the data mapped source buscomp Opportunity. In this case:

• The UI context (Quote) does not match the data mapped buscomp (Opportunity), and

• DTU must query all Opportunity buscomp records, unless the RowId parameter is additionally passed, to identify a single opportunity record.