Rules and Guidelines for the Unsaved Sibling Lookup Reference
Rules and Guidelines for the Unsaved Sibling Lookup Reference
Consider the following rules and guidelines for the unsaved sibling lookup reference:
Deletion Handling
If you delete an unsaved child and have not submitted the deletion yet, the sibling lookup pop-up might not display the deleted child.
Parent-Unsaved Child Association
Ensure that the parent record is in active state to create or associate an unsaved child. However, in sibling relationships, you can associate both siblings even if they are unsaved using the sibling lookup.
Validation Errors
Deleting a saved or active child associated with an active root or parent
An error might occur if you delete a saved child associated with a saved root through the sibling lookup and without submitting the changes. Errors may arise from unhandled internal references or constraints. For example, failure to update the state in the parent or sibling entities appropriately can lead to data inconsistencies or constraint violations in the database.
Deleting an unsaved child with an active parent
An error might occur if you delete an unsaved child associated with a saved root without submitting the changes. This action might cause errors as the system expects changes involving saved entities to be finalized with commits or rollbacks. Omitting these steps can disrupt the integrity and consistency of the data model, as the deletion operation affects the in-memory state without confirmation in the database.