What is the difference between a "datalink connection" and an integration?

ECM
1

I created a datalink connection and some datalinks in my sandbox instance. I’m looking to now move into production and the workload is small enough that I’m considering just creating everything from scratch in prod instead of exporting and importing (I’m also concerned about accidentally overwriting fields etc in prod from an import).

Anyway, in looking at things it appears we don’t have any datalink connections except the E10V2 connection that is greyed out (it turns out it’s an integration). While I can create a new datalink connection it’s all to the same database and server so it’d be nice if I could leverage the integration that already exists. However, I’m not sure how to add datalinks to that integration.

Should I be just creating a new datalink connection? And what ultimately is the difference between the two?

1 Like
2

The Integration is the official channel by which the licenses automation solutions communicate with the connected (integrated) environment. It’s basically reserved for this as it will import all of the default datalinks needed that come with the default workflows for the respective automation license.

The Datalink is the area in which you can create custom datalinks to achieve results that the default datalinks do not necessarily provide in one way or another. These are essentially boundless whereas the Integration method is confined to what comes with the respective license.

3 Likes