This article only applies to firms integrating CCH Axcess with Aiwyn.
We must do this to account for deleted records which occur in the aforementioned tables. Because the DAU tables do not function like normal SQL data tables, Change Tracking does not always account for deletions.
In lieu of this, Aiwyn has rerun flows on our side that take the newly updated table, run it against our database, and handle deletions for the firm by inactivating any record in Aiwyn's system that does not exist in the newly updated table.
These 4 tables must be fully refreshed first so that the update from Axcess to the DAU can pass the full refresh for these 4 tables in addition to passing the normal data update for other tables that do not need a full refresh.
What can go wrong
If a deletion is missed, the contact may remain active in Aiwyn and continue receiving invoice or statement emails in error.
If the full refresh runs but the DAU update then fails, data will not flow from CCH into the DAU, leaving Aiwyn out of sync with CCH. The two scheduled tasks are intended to run five minutes apart; if their schedules drift out of that relationship, data could be compromised.
This deletion-handling issue and the resulting full-refresh requirement apply to CCH Axcess only, not to other practice management systems.
Related
- CCH Axcess DAU update and full-refresh schedule
- Enable Update Cadence and Full Refresh in DAU
- How Aiwyn detects changes in your practice management data