11831207 - Convert the Sage 100 Connector From Trigger Audit to Row Version Sync
When the Sage 100 Connector was created in 2018, it was built upon the synchronization engine used by our Ecommerce platform for almost two decades. We refer to this system as Trigger Audit internally. This system was built with two purposes - audit row-level changes for every watched table and trigger synchronization based upon those changes. The change tracking was very helpful for auditing issues in an Ecommerce environment where it is difficult to get steps of what happened from an end user. The downside was that it generated a lot of data and the conversion of the audit logs to change events didn't always perform very well. Another issue was that the Ecommerce environment was almost exclusively a one-way sync - item and customer data would go up and sales orders would come down. The addition of two-way sync for customers, ship tos, and sales orders in 2019 across multiple connectors exacerbated the downsides of the trigger audit system. Because of these issues, we went back to the drawing board and created a system that was tightly focused on handling change events in the most efficient manner possible. We refer to this system as Row Version internally. This system was first deployed to our M1 Connector in 2019 with great success. With the completion of this project, the Sage 100 Connector has now been fully converted to the Row Version system. The change from Trigger Audit to Row Version requires a data conversion. This conversion is completely automatic but does require a managed cutover from a prior version. This data conversion is what caused the point increase from 10.x to 11.x. For customers that are not using the Sage 100 Connector, 11.x can be treated as a point release to 10.x.