HippobyteDocs
Expand All

Collections
A core building block of every connector

To allow for additional flexibility in synchronizing data, each Application Connector is segmented into Collections. Collections refer to each API endpoint of the source Application Connector.

Each Collection can be scheduled and synchronized independently of every other Collection within the Source Application Connector.

Schedulers

Schedule each collection within your Application Connector to run on different schedules. i.e. In a typical project management application project attributes change often whereas project manager attributes do not.

Synchronization Strategies

Mix and match Collection sync strategies to fit your data needs. Given the above example, perhaps you wish to audit changes to project task attributes, but not project attributes.

Your Collection set-up would resemble the following:

  • Project Task Collection:
    Append - Log or audit record changes over time
  • Project Collection: Incremental - Synchronize records based on last updated date

Data Exclusion

Exclude historical or immaterial data by providing an effective date for a collection. Data records older than provided date will not be replicated. The default setting is set to January 1, 1970, the basis of the UNIX Epoch time.

Have Questions? Reach out, we are happy to address any questions you may have.
© 2015 - 2021 Hippobyte, Inc. All rights reserved.