Branching
Omnata's git-style change management features
Branching for a sync can be opted into throughout the configuration process, depending on how you have configured your connections.
When to use branching
Branching can be use for both inbound and outbound syncs. However, branching is inherently more important for outbound syncs, since you are writing changes to the target endpoint.
On the other hand, branching for inbound syncs is less important as read operations don't materially affect data downstream.
There are two main branching modes:
Multi-environment; where you have separate test and prod instances of the target app or database.
Single-environment; where you only have one (assumed production) instance of the target app or database.
For single-environments, there are testing patterns we support (for outbound syncs only);
Alternate source via record filter You can select a small number of test records to push to the target app without creating a derived view or alernate source table.
Alternate source via different table You can select different source tables for test and main branches.
Alternate target location You can push data to a test area of your target endpoint like a folder, channel or dummy object.
A sync can operate in one of two configuration modes. This setting only impacts the way that syncs are configured and changes are managed, not the actual sync capabilities in any way.
See more in the Branching docs, and read an Overview of Branching on our blog.
Last updated