|Integration with third-party systems|
Resco CRM Connector (web APIs):
The Integrations function of Woodford allows you to connect your Resco Cloud organization to various systems using connectors (Resco Cloud, Dynamics, OData). Match entities and fields between the two servers and exchange data. Configured connections can be used in Resco Cloud jobs and workflows to automate sync process.
|Note||Integrations are available since release 14.1 as a preview. Contact us if you want to help us shape this function to better match your needs.|
The following connectors are available:
- OData: Connect to any server that supports the Open Data Protocol (OData v4).
- Resco Cloud: Connect to another organization residing on one of the various cloud servers of Resco (including Resco Inspections, Resco Routes, etc.).
You can manage your connections to other servers from the Administration menu of Woodford: Start Woodford and select Integrations (Preview) from the menu.
- Click New.
- Name your integration and select which connector to use.
- Depending on the selected connector, enter the necessary connection details.
- Click Save.
As the next step, you need to map external entities to local entities and external fields to local fields.
- Double-click a connection (created in the previous section).
- Select an entity from the External Entities pane and click Enable.
- In the Entity Mapping pane, select the matching Local Entity and optionally the Primary Key.
- In the table below, select the fields that you want to import or export (enable the checkbox in the first column) and then select the matching Local Field.
- Save all changes.
You can repeat these steps for additional external entities as needed.
Clean up metadata
Administrators of the backend servers can occasionally modify the metadata, either on the local or on the external server. New entities or fields are not a problem. What can affect the integration is when a certain entity or field used in integration is removed.
When you open a connection, Woodford checks whether the configured mapping is still valid. If this validation finds some missing entities or fields, a warning message is displayed with the recommended actions.
- If an external entity or field goes missing, click Clean Up to remove it from the mapping.
- If a local entity or field goes missing, select a new local entity/field.
- If the Primary Key field goes missing, consider setting up a new primary key.
Once the mapping is done, you can start using the integration for migrating data.
- Click Import Data or Export Data.
- Optionally, click Preview to verify that you are migrating the right data. Previews do not make any changes on either server.
- Click Import or Export to conclude the migration.
- Wait for the migration result.
|Note||Preview does not respect the selected primary key.|
Sample migration result:
RESULTS: ALL (15) : IMPORTED (13); UPDATED (2); FAILED (0). In this case, 13 records were imported (created), 2 records were updated, no records failed.
- Export / Import
- If you have multiple similar organizations where you want to reuse an integration, you can export the entire mapping configuration to a file and then import it to a different organization.
- Export Entity / Import Entity
- Alternatively, you can export/import mapping for a single entity.
Use case: connect to Business Central
You can use Integrations to connect to Microsoft Dynamics 365 Business Central.
Register Resco application in Business Central
Before you can start migrating data between Resco Cloud and Business Central, you must register the Resco application (clientId) in Business Central and grant Resco consent with accessing Business Central data.
- Log in to your Business Central organization and go to the Azure Active Directory Applications.
- Click New and fill out the registration form.
- As Client ID, use
- Add User Permission Sets.
- Grant the necesary consent.
- Start Woodford and select Integrations from the Administrator menu.
- Click New and enter the following details:
- Name - enter a name of your integration
- Connector - select OData
- URL - enter the URL of Business Central OData endpoint (e.g., https://api.businesscentral.dynamics.com/v2.0/b8cc0002-2542-46ed-8584-d4868701fbc4/Production/ODataV4/)
- Username - BC account's email address
- Password - BC account's password
- CustomQueryParamaters - custom query, which should be added to the every request (e.g.,
&company=CRONUS%20USA%2C%20Inc.). It is important to include the correct
- Click Save.
Double-click this integration to map external entities/fields to local entities/fields. Then you can start migrating data.