Toggle which record types to sync, how to sync them, and how long stale data should be kept

When you click into an app you will see a data schema of all the different types of data you can sync. You can toggle on or off what data you'd like to begin pulling into Middle and which syncs you'd like to use.

To recap, there are three types of syncs:

  • Complete transfers - Grab all the data available from an endpoint or external resource. This sync is common for smaller datasets.

  • Primary key lookups - Request data for a specific record using a primary identifier. For example, if Middle grabs a record, such as an invoice, and sees a user ID associated with that sale, Middle will perform a sync to grab that user's data.

  • Recent record lookups - Syncs data from a datetime range. For example, grabbing all sales that have occurred in the past hour, every 20 minutes. The datetime scope and frequency of these syncs are configurable from the developer portal.

When Middle syncs a record from an external source, if it finds a record, it compares the new record to the old. If the new record is different, it updates the existing record in the Middle database. If the record in the database is not found, it is inserted into the Middle database.

Ad-hoc syncs

Syncs are setup to run at frequencies determined via the developer portal. However, you are able to initiate a sync manually by triggering an ad-sync. For complete transfers, an ad-hoc sync will grab all the data from an endpoint or resource. For a primary key lookup, you will need to input a primary ID to grab data for. For recent record updates, you will need to select a datetime range you'd like to get data from.

Data retention overrides

Via the Settings portal, you can configure how long data is retained in Middle before it's deleted. A synced record will be deleted when its "last purposeful use" date exceeds the number of days your set for data retention. A record's "last purposeful use" date is refreshed (i.e., set to now) every time that record is referenced in a workflow execution or trigger execution and every time that record is updated.

Record retention rules can be overridden at the connection and record type level using data retention overrides. You have the option to either disable all data deletion for that record type in the specific connection or you can set the number of days records will be retained without a workflow or trigger referencing the record.

Last updated