Resco CRM Connector: Difference between revisions

Jump to navigation Jump to search

Resco CRM Connector (view source)

Revision as of 16:12, 15 April 2021

307 bytes added ,  15 April 2021
no edit summary
No edit summary
Line 1: Line 1:
{{Integration TOC}}
{{Integration TOC}}
[[Resco Cloud]] server can serve as a stand-alone backend, but it can also connect to other CRM or ERP systems, for example Microsoft Dynamics or Salesforce.
Resco CRM connector is a group of web API services that you can use to connect your third-party backend to [[Resco Cloud]] to exchange data between the systems. These are the components involved in Resco CRM Connector.


[[File:Crm integration.png]]
[[File:Resco crm connector.png|600px]]


* 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 your backend and Resco Cloud
* Resco CRM server: Fully customizable backend for Mobile CRM Client application
* [[Resco Cloud]]: Fully customizable backend for Resco mobile apps
* Resco CRM client: End-user CRM application customized for Resco CRM server
* [[Resco mobile apps]]: Any of the end-user applications customized for Resco Cloud, such as [[Resco Mobile CRM]]


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 Cloud and mobile apps are provided by Resco. Resco Cloud allows you to define schema and stores data for mobile apps, which is used to display the data.


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.
You can now build your own Resco CRM Connector to enable the synchronization between your backend system and the Resco Cloud. Resco Cloud acts as a passive module — it does not initiate any synchronization. Mobile apps must initiate the synchronization process to download/upload data. This also applies to Resco CRM Connector. It must determine when/whether to synchronize ERP system data with data stored on the Resco Cloud. 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 Cloud 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 Cloud.


Resco CRM Connector consists of a set of REST web service methods divided into '''metadata service''' and '''data service'''.
== Available APIs ==
 
Resco CRM Connector offers three different APIs:
* REST data service - a set of REST web service methods divided into '''metadata service''' and '''data service'''
* [[OData service]]
* [[Questionnaire OData service]] - read-only [https://www.odata.org/ OData v4] API service for accessing questionnaire results
 
This article describes the REST data service.


== Data types ==
== Data types ==
Retrieved from "https://docs.resco.net/wiki/Special:MobileDiff/4598"

Navigation menu