Skip to content

Connectors

"This is where the magic happens" - James Hutchison, Owner

Connectors are one of the key features of IMan. They integrate IMan with an application such as a CRM, an ERP or accounting system, a cloud-based service or an eCommerce platform.

Connectors can work in both directions. They can push data into an application or webservice, or pull data out of it.

Connectors usually do more than connect to the target application. They smooth out inconsistencies in the application's interface (API). For example, a connector can:

  • Hide processing complexity from the mapping interface.
  • Add functionality the API lacks, improve its processing logic or join separate functions together.
  • Provide a simple flat interface for one-to-one (1:1) communication between IMan and the target application. An application may expose some functionality as a child of the primary entity even though the two operate at the same level. In these cases the connector flattens the parent/child relation and exposes the child's functionality in the primary entity.
  • Keep your mapping working across application versions. Only substantial changes to the application's data schema affect it.

Static & Dynamic Type Connectors

A static connector provides a fixed list of import types. A dynamic connector builds its list of import types by querying the application's metadata. Some connectors combine both approaches: a fixed set of import types, with extra metadata obtained by querying the application.

Static Connector

A small accounting system such as Sage 50 has limited functionality and a specific purpose, so its connector provides a fixed set of interface points. Each interface point exposes a fixed list of fields.

Dynamic Connector

Sage CRM and Sage X3 let you extend or customise their data schema, so their connectors are dynamic connectors.

Mixed Type (static connectors with dynamically generated elements)

The Sage 200 and Sage 300 connectors combine both approaches. They provide a fixed list of import types, but each field list combines fixed fields with a small set of fields that the connector adds by querying the application: Analysis Codes in Sage 200 and Optional Fields in Sage 300.

Common connector handling and setup

The following pages describe how to set up and use any connector. For anything specific to one application, see that connector's guide.

Every connector, push or pull, uses the same interface, with drop-downs that show the options available for that application.