Deletes
How Bracket handles deleted records
Summary
Currently, Bracket supports delete syncs for specific data source integrations. In the table below, you can see which sources are supported.
Currently, Bracket only supports deletes on tables & collections less than 0.5 GB
| Data source | Deletes supported? |
|---|---|
| Postgres | Yes |
| Salesforce | Yes |
| Hubspot | No |
| Airtable | Yes |
| Google Sheets | Yes |
| MySQL | Yes |
| MongoDB | Manually on legacy app |
| Firestore | No |
| Snowflake | No |
| Notion | Manually on legacy app |
Manual deletes
By default, all new syncs have a manual delete policy. If deletes to the data source are supported, you can review these deletes at any time by navigating to the “Deletes” tab.
Once there, you can see the history of delete scans and delete executions. You can initiate a new delete scan by clicking “Refresh,” then manually review deletes from both synced sources.
If you choose to leave the records in the paired data source, Bracket will no longer give you the option to delete the record in the future. If you decide you’d like to delete it later, you’ll need to do so directly in the data source.
Automatic deletes
If you want all deleted records to automatically sync every day, then go to the “Advanced” tab on your sync and change the delete protocol to “Automatic.”
With an automatic delete policy, Bracket will execute all deletes after its daily scan at midnight UTC.
What if I delete records, and deletes are not supported?
If you delete records in one source, and deletes are not supported for the opposing source, then nothing will happen to the paired record in the opposing source. Essentially, the paired record becomes orphaned and can safely be deleted.