Type bindings

A binding is used to map properties in a type to a data source (such as database fields) in a connector.

For example, an 'Account' type could use a 'Salesforce Account' binding in order to save Account objects into the Salesforce 'Account' database table.

• The mapping does not need to be directly to database tables in the connector, however, the binding should provide unique identifier information necessary for the element to insert the provided values back into the correct storage locations.

• Bindings are typically pre-configured as part of the type installation process.

Multiple bindings

It is possible to have multiple bindings for the same connector, but with subsets of the properties mapped to different fields.

For example, you might have an 'account' type from the Hub connector, which has a 'quarantine entry' binding with the 'company name', 'created at', and 'quarantined at' properties bound, and another 'golden record' binding with the 'company name', 'created at' and 'source ID' properties bound. The whole type itself would have 'company name', 'created at', 'quarantined at' and 'source ID' properties, but you would only be able to view the appropriate ones for the selected binding at any time.

Another example of multiple binding is if a 'person' type is created that could (in theory) have two bindings - one for the SQL connector, and one for the Salesforce connector, with each binding's 'property bindings' mapping the field names in each to the correct type property. You should then be able to select either the 'SQL connector' or the 'Salesforce connector' binding, with the Flow loading from the correct place.