9,281
edits
Configuration: Difference between revisions
Jump to navigation
Jump to search
→Salesforce: Force legacy batch upload API
(→Forms) |
(→Salesforce: Force legacy batch upload API) |
||
| Line 86: | Line 86: | ||
* '''Disable multi-layout support''': Disable automatic selection of forms based on Salesforce Layout Configuration. This also disables support for Picklist Values based on Record Type. | * '''Disable multi-layout support''': Disable automatic selection of forms based on Salesforce Layout Configuration. This also disables support for Picklist Values based on Record Type. | ||
* '''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. | ||
* '''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. | |||
== Dynamics == | == Dynamics == | ||