There are two processing options in a Brightvine Data Link (BVDL) import job configuration which give you the flexibility to review the import data before committing or skip that if you don't need to review before the data is imported.
With this option, the selected staging templates or file mappings are run. The BVDL performs matching and data validation on the records, but nothing is committed outside of the staging tables.
Tip: the number of records processed will be reported as 0 at this point.
The following actions are available from the main status page after running the import with Staging Only:
To review all data, click the ‘View All Staging Records’ button.
To review and correct only the records that contain validation exceptions or are potential duplicate constituents, click the ‘Fix Exceptions’ button.
To commit the records to your database, click ‘Process Records’.
Staging and Processing (formerly Staging and Engine)
With this option, the selected staging templates, the full import engine, and any applicable post-processing packages are run. This means that the records will be fully staged, processed, and committed.
Tip: In the case of revenue, “committed” means the revenue records will have been added to a batch.
You can choose this option if you do not wish to review the staged data, allowing the import to be fully scheduled and run without any manual intervention.
Total records processed, and number of exceptions will be reported on the main status page. These numbers refer to the total number of top level records in this run – constituents, events, and designations. After the process completes, you can review all data committed and correct any exceptions in the same manner as described for Staging Only.
Why build a BVDL post-processing package?
After the BrightVine Data Loader has processed all records, it kicks off a separate SSIS project, BVDL Post Processing. Why would you use this? There may be certain actions you need to perform after all the records have been created or updated, and these actions can be placed in a custom post-processing package. The post-processing package can be paired with a specific staging template. If it is, it will only be run if that staging template was run, and it will only consider records imported by that staging template.
One example of how this capability could be useful is in the case when the import is a sync process with another system. The post-processing logic could write back the Blackbaud CRM™ record IDs to the source system in order to maintain a cross-reference between the systems. The external ID column present in all BVDL staging tables is a useful tool for this case as well, providing a place to store identifiers or other information from the data source without affecting the import process.
Alternatively, the post-processing package can be set up to run in all cases regardless of what staging templates were selected. This would be useful if there are custom business rules that require some additional action performed on all records or if there is any desired custom reporting or logging for all BVDL imports.
Load Revenue Updates Using the BVDL
Did you know you can load Revenue Updates into Batch using the BVDL?
Users have always been able to import revenue data into an enhanced revenue batch with the BVDL. With version 3.0, users can now import revenue updates into a revenue update batch allowing them to adjust amounts or other payment details, add acknowledgements or attributes, and more.
Some features included with the new revenue update support:
- Specify the revenue update batch template to use for each import in the UI. - New fields have been added for staging adjustment information. - Import adjustments and new revenue from the same file or data source – records will be routed to an enhanced revenue batch or update batch accordingly. - As with new revenue, these records can be included in imports involving constituent data, interaction data, and any other areas the BVDL supports. - Defaults set in the revenue update batch template will be honored. - The batch group feature available with new revenue is also available for revenue updates – based on this staging field, revenue updates are split into separate update batches automatically
Want to learn more about the data loader? Connect with us today for demo.