10,850
edits
No edit summary |
mNo edit summary |
||
Line 6: | Line 6: | ||
* Your system: any CRM/ERP system | * Your system: any CRM/ERP system | ||
* Resco CRM connector: Synchronization module between ERP System and Resco CRM Server | * Resco CRM connector: Synchronization module between ERP System and Resco CRM Server | ||
* Resco CRM server: Fully customizable | * Resco CRM server: Fully customizable backend for Mobile CRM Client application | ||
* Resco CRM client: End-user CRM application customized for Resco CRM server | * Resco CRM client: End-user CRM application customized for Resco CRM server | ||
Resco CRM server and client are provided by Resco. Resco CRM server allows you to define schema and stores data for Mobile CRM Client, which is used to display the data. | Resco CRM server and client are provided by Resco. Resco CRM server allows you to define schema and stores data for Mobile CRM Client, which is used to display the data. | ||
You can now build your own Resco CRM Connector to enable the synchronization between your | You can now build your own Resco CRM Connector to enable the synchronization between your backend system and the Resco CRM Server. Resco CRM Server acts like a passive module — it does not initiate any synchronization. Mobile CRM Client must initiate the synchronization process to download/upload data. This also applies for Resco CRM Connector. It must determine when/whether to synchronize ERP System data with data stored on the Resco CRM Server. For example, every hour, every day, etc., depends on how current the data must be on the clients. To check whether there are new/updated data on the Resco CRM Server use “GetMaxRowVersion” web service method to get the current row version. If the current row version changed from the last stored row version, there are new changes available on the Resco CRM Server. | ||
Resco CRM Connector consists of a set of REST web service methods divided into '''metadata service''' and '''data service'''. | Resco CRM Connector consists of a set of REST web service methods divided into '''metadata service''' and '''data service'''. | ||
Line 445: | Line 445: | ||
=== Post ExecuteMultiple === | === Post ExecuteMultiple === | ||
Allow to execute specified | Allow to execute specified operations on multiple entities, such as Create, Update, Upsert and Delete. | ||
* ContinueOnError – Determine whether to continue executing operation on error. | * ContinueOnError – Determine whether to continue executing operation on error. | ||
* TransactionType – Determine transaction operation: | * TransactionType – Determine transaction operation: |