How to repopulate data tables in ADC
If the data in your extract seems wrong or a specific table does not update after Sage 300 is updated. You can set the table to repopulate in ADC to refresh the entire table. We do not recommend that you just set it to "Always repopulate on update" as this can alter the timing of your ADC updates depending on the data size of the table. Occasionally updating all tables is ok but having the longer run times all the time could cause Scheduled tasks on repeat to fail.
The following are reasons that we recommend setting a table to "Always repopulate on update" on syncs:
There are some third party applications that write to Sage Tables without triggering that there is an update on specific rows, therefore the standard sync process doesn't pick up changes on the row
Note: This could also include updates to tables using the direct ODBC connection via Microsoft Access
Some year-end tax update pushes from Sage version upgrades don't trigger that there are updates on specific rows, therefore the standard sync process doesn't pick up changes on the row
Note: Because this is generally a 1-time event annually, this can be achieved by selecting "Repopulate on next update"
What to do when you get the following error:
Errors: [GLT_CURRENT__TRANSACTION]: Source and Destination (SQL) record count do not match after second attempt. No Repopulate Attempt due to Source row count greater than 5000000 records
In this situation you can fix that error by setting the GLT_CURRENT__TRANSACTION table to repopulate or always repopulate in the ADC table settings. As a warning the table load will take much longer if you repopulate a table of that size. Setting to always repopulate will permanently alter the run times of your local ADC sync to be longer. To fix this you would open ADC, go to the connection with the error table and click the + to the left of the connection name. Scroll down to find the table you need to edit and then select the 'Repopulate on next update' or 'Always repopulate on update' checkboxes. Click the save button, and run an update on the table.
You can also set the entire connection to repopulate by clicking the checkbox to the left of the connection name in ADC. Then you would click the Repopulate All Tables button in the upper right of the application. When prompted you have to click yes to proceed. Once set it will run an update as if you had selected a specific table and set it to "Repopulate on next update".
Related Articles
Troubleshooting Problems Data Sync to AnterraBI
Some of the common reasons for the anterraDataCenter sync to stop running are as follows: anterraDataCenter subscription has expired. A new Activation Key is required. Upon annual subscription renewal, Anterra proactively sends an email with the ...Allow Non-Administrator Users to Run ADC Updates
Running All Connections This is the easiest configuration and allows any user to run the configured connections for all active tables. Create a shortcut to ADCUpdate.exe (located in the anterraDataCenter installation folder). You can place this ...Data Trimming Security Report
To help clients better understand what end-users see, Anterra has implemented user security audit reports. Reach this area of Anterra’s site by going to Admin, then User Admin, then User Data Trimming Report. This is a Pivot grid allowing clients to ...Data Synchronization - Status display in the AnterraBI™ Menu Bar
Version 25 Release Anterra has added a data synchronization status icon on the AnterraBI menu bar. The icon is to the left of the Alerts Icon and rotates when your data or your cube is updating: When you click on the icon, you will see the status of ...Set up SQL Data connections for Sage Crystal Reports
Overview Sage 300 CRE uses Crystal Reports to generate formatted reports. To connect Crystal Reports, and thus the Sage report designs to your data which ADC has extracted into SQL Server, you will need to: Create a 32-bit ODBC connection called a ...