Important Notes Concerning Embedded Objects

An embedded link requires careful design to ensure that all embedded virtual fields have the appropriate settings.
You must examine the security permissions for the entities involved in the embedded link. In general, all users who have read/write access to the entity also need read/write access to the embedded entity. Regardless of how you configure the security settings, keep in mind that users need access to the embedded entity to function correctly.
When a user opens a new container entity's form and enters information in all of the required fields, including the required embedded link fields, the system creates a new container record and a new embedded link record when the record is saved.
If the embedded link field is required, then a user will need to specify all required fields in the embedded entity in order to save the container record (that is, the record that includes the embedded link).
- For example, if VehicleID is required, then a user needs to specify a value for all of the required fields in the Vehicles entity.
If the embedded link field is not required, the user can save a container record without specifying a value for any of the embedded fields. However, if the user specifies a value for one or more embedded fields (or changes the default value of one or more embedded fields), then the user must specify a value for all of the embedded entity's required fields in order to save the container record.
- For example, if VehicleID is not required, then a user can save a Passenger Vehicles record without specifying any of the required Vehicles fields. However, if a user enters a value for any of the Vehicles fields, the user must complete all of the required Vehicles fields to save the record.
After configuring a linked field as Embedded and then saving the entity, you cannot later change the linked field to Standard. If you want to change an embedded link to a standard link, you can delete the embedded link and then add a new field for the standard link.
If In Place Editing is enabled for the container entity, a user can edit Virtual Fields from an embedded entity in views of the container entity's records just as if those fields existed as In Table fields within the container entity.
A user should not create new records from directly within the embedded entity. The user will be unable to link these records to records in a container entity.
If an embedded record is already linked to one or more container records, changes made directly to the embedded record are reflected within the container record(s).
For non-shared links, each record in an embedded entity has one "owner" record in a container entity.
- Once an embedded record is linked to its owner, you cannot link an existing embedded entity record to another container entity record.
- When a user opens an existing container record and modifies one or more embedded link fields, the system automatically updates the embedded entity's record.
- If a user deletes a container record, the corresponding embedded record is also deleted.
For shared links, each record in an embedded entity has one "owner" record in a container entity and may have one or more non-owner records.
- When a user deletes a shared embedded object's owner record, the corresponding embedded record is not deleted, since it may still be linked to other records. Instead, Aptify removes the OwnerRecordID (it is reset to -1) and locks the record (sets the Locked bit).
- See Designing and Creating Shared Embedded Objects for more information.

5.5 Product Knowledge

If you have a comment on this topic, contact Aptify Documentation. If you want to return to the Aptify Community Site, please click here.

Important Notes Concerning Embedded Objects