10,730
edits
Important: Deprecating old WebView — Publish failed error
App projects: Difference between revisions
Jump to navigation
Jump to search
→Managing fields: expanded
(→Managing entities: When to use Always Full Sync) |
(→Managing fields: expanded) |
||
| Line 178: | Line 178: | ||
{{Note|Best practice: We recommend not to include too many entities and fields in your mobile project. Backend servers often include a large wealth of entities and fields, and most organizations only use a small subset. An even smaller subset of the data is necessary in the field. [[Sync Filter]] can further restrict which records should be downloaded to the mobile device. Careful planning can improve the performance of the app and satisfaction of the users.|Tip}} | {{Note|Best practice: We recommend not to include too many entities and fields in your mobile project. Backend servers often include a large wealth of entities and fields, and most organizations only use a small subset. An even smaller subset of the data is necessary in the field. [[Sync Filter]] can further restrict which records should be downloaded to the mobile device. Careful planning can improve the performance of the app and satisfaction of the users.|Tip}} | ||
You can also configure some properties for each field. Select a row and modify the '''Properties''' pane on the right. | [[File:Properties pane for entity fields.png|right]] | ||
You can also configure some properties for each field. Select a row and modify the '''Properties''' pane on the right. Some parameters are read-only. | |||
; Permissions: Configure the permissions to Read, Create, or Update values in the field. | ; Permissions: Configure the permissions to Read, Create, or Update values in the field. | ||
| Line 191: | Line 192: | ||
:* HTML – Formats the text field into an HTML type (bodies of email, signatures and etc). | :* HTML – Formats the text field into an HTML type (bodies of email, signatures and etc). | ||
:* DropDown, DropDownList, Multi DropDown, Multi DropDownList – this feature allows you to predefine input for users, so instead of entering a value, they can choose to use options from a drop-down list (or enter what is needed manually). More about this feature is shown in this [https://youtu.be/9vL4QRN_1dk?t=34m3s webinar section]. {{Badge|Webinar}} | :* DropDown, DropDownList, Multi DropDown, Multi DropDownList – this feature allows you to predefine input for users, so instead of entering a value, they can choose to use options from a drop-down list (or enter what is needed manually). More about this feature is shown in this [https://youtu.be/9vL4QRN_1dk?t=34m3s webinar section]. {{Badge|Webinar}} | ||
; Requirement Level | |||
:* A field can be either optional ("None") or required ("SystemRequired"). | |||
; Options | |||
:* For option/status fields, the available values are listed here. | |||
; Default | |||
:* The default value of the field. | |||
; Constraints | |||
:* For numbers, see the minimum and maximum allowed value. For strings, see the maximum size. | |||
; Precision | |||
:* For floating-point numbers, see the maximum allowed precision. | |||
; 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, for example, during synchronization to establish the order of entities when [[Synchronization_steps#Uploading_local_changes|uploading local changes]], when deleting parent entity records (to clean up also child records), in [[Sync Filter]] (to ensure that both parent and child records are available), etc. | :* 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, for example, during synchronization to establish the order of entities when [[Synchronization_steps#Uploading_local_changes|uploading local changes]], when deleting parent entity records (to clean up also child records), in [[Sync Filter]] (to ensure that both parent and child records are available), etc. | ||
:: (Salesforce only) Check to download only attachments belonging to records that are available offline. This property can optimize data download. | :: (Salesforce only) Check to download only attachments belonging to records that are available offline. This property can optimize data download. | ||
; 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}} | ||