Skip to content

Integration effort depends on the data path you need

Two tools with APIs can require different preparation. The deciding factors are the required data, operations and permissions.

Tobias Krüger2 min read
Blue-rimmed data socket with a cable plug positioned in front of it.

Compare the required workflow

For an effort estimate, “there is an API” is too broad an answer. What matters is whether the specific connection can read the required data, detect changes and write the intended result. Microsoft's Dataverse documentation lists reading, creating and updating as different operations. The permissions actually granted matter too: Personio, for example, documents separate read and write permissions.

A fictional software company compares two tools for transferring approved project time to an ERP billing draft. These invented products are assumed to have the following capabilities:

Required step

Tool A

Tool B

Obtain approved time

API provides projects; time arrives as CSV

API provides {"approvedHours":1.5} among other fields

Detect a correction

New full export without an explicit change signal

Change retrieval with a stable identifier and version

Add to the ERP draft

Project mapping and ERP write permission needed

Project mapping and ERP write permission needed

These capabilities are our own comparison assumptions, not product claims about Microsoft, Personio or other vendors.

Make the remaining part of the connection visible

Tool B provides the required time through its API. The connection must still understand the unit: for a target using minutes, the conversion is 1.5 × 60 = 90. The source project also needs an unambiguous ERP mapping. Write permission in the source does not authorise an entry in the target. The integration must be able to confirm the target result or handle an uncertain response there.

Change retrieval would also need clarification of how completely the required corrections can be recovered. The table proves neither a finished workflow nor a time advantage. Sound planning would require checking documented operations and permissions with suitable examples in an appropriate test environment. The gaps revealed provide a better basis than the number of advertised interfaces.

When a file route can still suit the first delivery

If the team only needs a daily draft, has few records to handle and already has a controlled file handover, that route may be enough for the first delivery. A more extensive API connection need not be built first. Frequent corrections or a need for current values change that decision.

Sources

Written by

  • Tobias KrügerEditor for Systems IntegrationTobias Krüger covers how different software systems work together at ASES. In his articles he explains how ERP, CRM and online shops are connected and how to deal with errors in data exchange.

Follow ASES

Read more

All articles

APIs & Integration with ASES

ERP, CRM and shop cleanly connected