9,281
edits
Configuration: Difference between revisions
Jump to navigation
Jump to search
→Salesforce
| Line 99: | Line 99: | ||
* '''Refresh layouts and Record Type mapping on first sync''': When enabled, layouts and Record Type mappings are downloaded to the mobile app on every first sync after the application start. When disabled, these are only downloaded when a new app project version is available ([[Releases/Autumn_2022#Syncing_layouts_with_Salesforce|feature introduction]] / [[Salesforce_FAQ#permissions|FAQ entry]]). | * '''Refresh layouts and Record Type mapping on first sync''': When enabled, layouts and Record Type mappings are downloaded to the mobile app on every first sync after the application start. When disabled, these are only downloaded when a new app project version is available ([[Releases/Autumn_2022#Syncing_layouts_with_Salesforce|feature introduction]] / [[Salesforce_FAQ#permissions|FAQ entry]]). | ||
* '''Prefer Salesforce Files over Attachments''': Use Files as default object for generated content such as mobile reports and scanned business cards (CamCard). The Attachment object is used by default. | * '''Prefer Salesforce Files over Attachments''': Use Files as default object for generated content such as mobile reports and scanned business cards (CamCard). The Attachment object is used by default. | ||
* '''Download only files linked to records (if enabled for entity)''': When syncing, skip files owned and shared by the current user. Download only files linked with entities where '''Sync linked entities''' is set to "All". | |||
* '''Force legacy batch upload API''': Use the less efficient [https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_composite_batch.htm Batch API] for uploading records during synchronization (instead of the default [https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_composite_sobjects_collections.htm Collections API]). Consider the legacy API only if you experience issues with APEX triggers or when recommended by Resco support. | * '''Force legacy batch upload API''': Use the less efficient [https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_composite_batch.htm Batch API] for uploading records during synchronization (instead of the default [https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_composite_sobjects_collections.htm Collections API]). Consider the legacy API only if you experience issues with APEX triggers or when recommended by Resco support. | ||