Seeding and syncing
ActivReporter uses a company database to duplicate the details found in the GP database you want to report on. Seeding and syncing are the methods used to keep the ActivReporter company database in line with the GP database.
Seeding is the process of creating the static copy of your GP data in an ActivReporter database. Initial seeding of the ActivReporter database occurs when you perform company configuration for the first time. Seeding includes creation of setup details such as GP categories, accounts, and transaction history. After initial seeding, you can reseed manually as necessary. To keep the company database synchronized with the source GP database, reseeding is sometimes required after an upgrade of ActivReporter.
In general, reseeding is required when you:
- Close the year in the Dynamics GP database.
- Upgrade the ActivReporter software (occasionally).
- Upgrade the Dynamics GP software.
Syncing is the automatic propagation of changes in the GP database to the ActivReporter company database. To accomplish syncing, triggers are added to the GP database. These triggers create messages which contain the details for updating the ActivReporter company database to match the GP database and add them to a queue. A separate ActivSync database stores these messages. The messages in the queue are processed by a service called the SQL Service Broker External Activator (SSBEA). As a result, users see the changes made in GP updated to the ActivReporter company database almost instantly.
If the sync process is interrupted, resuming the sync process should catch up with updates by processing any pending messages in the ActivSync database. In the event the ActivSync database itself is damaged, reseeding the company database from GP will re-establish synchronization. If you don't see changes being reflected in ActivityHD Explorer, check to see if the messages are stuck in the ActivSync database.