If Using Backups and Snapshots
Please be advised that if anyone wishes to use both the OnePlan_to_SQL_OneAnalytics and TakeOnePlanSnapshot strategies, we highly recommend that two separate integrations be made. Both strategies use the OData Table Name field, so if there are different tables that are to be snapshot than backed up, this can cause unnecessary tables to be created for the client.
OnePlan_to_SQL_OneAnalytics – Full Sync Only
It’s essential to note that the OnePlan_to_SQL_OneAnalytics strategy operates as a full synchronization mechanism. Users do not have the option to selectively choose specific fields from each OData table to transfer over. The strategy mandates the inclusion of all fields associated with each OData table, ensuring a comprehensive synchronization process.
OData Tables with Paging Limitation
OData tables that employ paging mechanisms, especially those managing large volumes of data, may encounter limitations during the synchronization process. In some cases, a complete sync might not be achievable for such tables due to the inherent challenges posed by paging. This limitation is recognized within the current integration framework.
Snapshots not Available for all OData Tables
As of right now, the snapshot feature applies to all tables except for Capacity, ResPlan, Timesheets, and Teams.