App projects: Difference between revisions

App projects (view source)

Revision as of 12:37, 12 October 2021

1,147 bytes removed , 12 October 2021

→‎Managing fields: move Mark as parent pointer info to a standalone article

Jzambor

Interface administrators, Administrators

9,400

edits

@@ Line 276: / Line 276: @@
 ; Advanced {{Anchor|Mark as Parent Pointer}}
-: Mark as Parent Pointer – When you enable this flag for a lookup field, you can establish a child-parent relationship between entities. This information is used at various places in the app, usually to ensure that both parent and child records are available (all child records for each parent; no orphaned child records, etc.), for example:
+: Mark as Parent Pointer – When you enable this flag for a lookup field, you can establish a child-parent relationship between entities. See [[Mark as Parent Pointer]] for implications.
-:* In the entity download phase of sync, to include the parent entity's [[Sync_Filter#Mark_as_Parent_Pointer|sync filter]] also for child entity records. I.e., only download child records if their parent records are also downloaded.
-:* When [[Synchronization_steps#Uploading_local_changes|uploading local changes]] during synchronization to establish the order of entities. (Child entities are uploaded before parent entities.)
-:* Also related to sync upload: Status changes for parent records are updated only after all associated child records are uploaded.
-:* When deleting parent entity records (to clean up also child records). Note that cascading deletion only happens if [[Configuration#Delete_Behavior|the related configuration option]] is enabled. If not, orphaned child records are deleted during the next sync in its cleanup phase.
-:* (Salesforce only) Check to download only attachments belonging to records that are available offline. This property can optimize data download.
 ; Description

App projects: Difference between revisions

App projects (view source)

Revision as of 12:37, 12 October 2021

Navigation menu

Search