9,400
edits
App projects: Difference between revisions
Jump to navigation
Jump to search
→Managing fields
| Line 258: | Line 258: | ||
; Requirement Level | ; Requirement Level | ||
:* A field can be either optional ("None") or required ("SystemRequired"). | :*A field can be either optional ("None") or required ("SystemRequired"). | ||
; Options | ; Options | ||
: | : For option/status fields, the available values are listed here. | ||
; Default | ; Default | ||
: | : The default value of the field. | ||
; Constraints | ; Constraints | ||
: | : For numbers, see the minimum and maximum allowed value. For strings, see the maximum size. | ||
; Precision | ; Precision | ||
: | : For floating-point numbers, see the maximum allowed precision. | ||
; Lookup Targets | ; Lookup Targets | ||
: | : For lookup fields, this parameter lists the allowed targets of the lookup. | ||
; Advanced {{Anchor|Mark as Parent Pointer}} | ; 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: | ||
:* 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 | ; Description | ||
: | : Description of the field. | ||
{{Note|If you disable any previously enabled field, please check all existing views and forms and remove any fields or lists marked by the sign “Invalid”, or enable the corresponding field so that the field will no longer be listed as invalid. If there are any invalid fields or lists in the form or view, the application will crash when you try to open an entity list or record details. See [[Metadata changes in live projects]] for more information.|Warning}} | {{Note|If you disable any previously enabled field, please check all existing views and forms and remove any fields or lists marked by the sign “Invalid”, or enable the corresponding field so that the field will no longer be listed as invalid. If there are any invalid fields or lists in the form or view, the application will crash when you try to open an entity list or record details. See [[Metadata changes in live projects]] for more information.|Warning}} | ||