A child app instance can be submitted even before its parent instance has been submitted. On the Submit button object and the Submit behavior command, there is an advanced property, Submit as child even if parent is not submitted.(1)
If this check box is selected, and the child is submitted, it will be written into the database immediately, even if the parent instance has not yet been submitted for the first time. If the parent instance does not get submitted at all, the child instance will exist normally but its parent relationship is broken, since the parent instance does not exist in the database.
If this option is not selected, and the child is submitted, it will not be written to the database until the parent has been submitted at least once. If the parent has already been submitted before, it is written into the database immediately. This option allows you to prevent orphaned child instances.
You cannot look up another instance if it has not yet been submitted. If you are planning to use app connections to perform lookups between parent and child instances, you need to make sure that the retrieved instance has actually been submitted. If necessary, use the Submit behavior command with the Re-open Same Instance (2) property selected. This will perform an invisible submit of the parent instance before you open the child instance.
See also: Finding and Viewing Related Apps Instances
Return to: Linking Apps and Using Parent-Child Relationships, Designing an App |
|
