10,729
edits
Important: Deprecating old WebView — Publish failed error
Synchronization steps: Difference between revisions
Jump to navigation
Jump to search
→Special considerations
| Line 33: | Line 33: | ||
=== Special considerations === | === Special considerations === | ||
* Lookups may present a problem. They may point to a record that does not exist on the server. | * Lookups may present a problem. They may point to a record that does not exist on the server. | ||
* In some cases, the state of record cannot be updated | * In some cases, the state of record cannot be updated. For example, to close a quote, certain prerequisites must be met. Therefore, status change must be performed at the end of synchronization. | ||
** As of [[Releases/Autumn_2020|release 13.2]], this special behavior for the status field only applies to Account entities and all parent entities. Other entities are unaffected. You can disable this behavior using per entity; see '''Upload Status with Data''' below. | ** As of [[Releases/Autumn_2020|release 13.2]], this special behavior for the status field only applies to Account entities and all parent entities. Other entities are unaffected. You can disable this behavior using per entity; see '''Upload Status with Data''' below. | ||
* We may create a new record on the server, but do not get any confirmation. Next time we try to re-create an existing record. Similar problem can happen for record update. | * We may create a new record on the server, but do not get any confirmation. Next time we try to re-create an existing record. Similar problem can happen for record update. | ||