Historical Re-sync

during each run, a sync bridge will return the new or updated records since the last run well, what about after the first run; what if i didn't get all the records replicated from the source connector? when historical data needs to be loaded each source connector will have certain capabilities relaitve to how the vendor has built their api option 1 re sync all historical records when you need to sync historical data, datalakehouse io aligns with the vendors api capabilities and provides the ability to resync this historical data for the source connectors that allow you to set the data on the historical sync, under the options tab the historical load start date field is available before setting a date, as the source system administrator how far back data is available and if there are any api limits for your source system for example, your salesforce contract will specify the amount of data that you are allowed to pull via the api on a monthly basis once you know the historical date, set the historical load start date field accorindgly in the source connection next, go to your sync bridge and click actions re sync all history and the bridge will execute a historical sync based upon the historical load start date please not that processing time of the sync bridge may take significantly longer to run depending on how much data is being replicated during the historical sync option 2 individual entity historical sync in certian situations, you may only want to perform a historical sync on certain entities once you know the historical date, set the historical load start date field accorindgly in the source connection next, while in the source connection , click on the source schema tab a list of all the entities available to replicate will be displayed if the source system vendor has provided the appropriate api, a re sync icon will appear to the right of the table/entity as show as #1 in the image below clicking this icon will tell the sync bridge to do a historical sync on that entity during it's next scheduled run if the table/entity is not available to run a historical sync then the sync icon will be grayed as in #2 in the image below this may be due to the fact that the vendor controls the api in order to ensure data integrity this data integrity is enforce by only allowing a historical sync on the higher level table/entity in the image below, the employee entity is the main entity and when a historical sync is activited on the employee entity, all the other entities with the name employee will have a historical sync