top of page

Making Blackbaud CRM Integrations More Flexible with BrightVine Data Link

  • Aug 12
  • 2 min read

The Execute Data Form Dynamic Operation has been a game-changer for integration since its launch last year, elevating the import process for Blackbaud CRM via BrightVine Data Link (BVDL). This powerful feature allows you to call any Add or Edit data form within Blackbaud CRM, supporting both out-of-the-box and custom forms. The flexibility this brings means you can now process data for all areas of CRM, including custom tables.


Blackbaud CRM Integrations

Now, this functionality is even smarter! In BVDL, the Execute Data Form Dynamic Operation can be executed conditionally. So, what does that mean for you? Let’s dive into a practical example.


Conditional Execution in Blackbaud CRM Integrations: Importing Interactions with Responses


Imagine you’re importing interactions where some records have responses and others do not. Instead of applying a blanket rule to all interactions, you can now configure your data form execution to trigger only when a response exists. Here’s how:


1.    Set Up Your Import File/API Integration & Field Mapping

  • Create field mapping as usual and connect your data source.

  • In the Interaction collection, map the interaction fields as you normally would, but now map the Interaction Responses to the Interaction Placeholders.

2.    Configure an Orchestration with an Execute Data Form in the Preprocessing Step

  • Set up an Orchestration and include an Execute Data Form as a Preprocessing Step.

  • Enable Conditional Execution by checking the box to use a Conditional Set.

  • Base the condition on one of the placeholders (Response fields) and set it to 'Not Equal to Blank'.

  • Select Data Form: Constituent Interaction Response Edit Form and set Staging Table: Interaction.

3.    Map the Response Collection

  • Map the Placeholders to fields such as Response Date, Category, and Response Type.

  • Map Record ID (GUID) to Record ID.

  • Save the Dynamic Operation

4.    Run the Import Job

  • Configure the import job with the mapping and Orchestration.

  • Execute the job in Staging Only mode to validate that the Response data appears in the placeholders.

  • Process the staged records.

5.    Verify the Logic

  • Navigate to the Interaction and click Edit Responses.

  • Voila! The Response is now present and properly mapped.

 

Why This Update Matters

This enhancement allows you to streamline data imports/integrations by ensuring information is added only when applicable—eliminating unnecessary processing and reducing potential data inconsistencies. By using conditional execution, you’re not only optimizing performance but also enhancing data integrity.


Give this functionality a try! Your data imports will be transformed forever.

 

 

 

 

 


Comments


Commenting on this post isn't available anymore. Contact the site owner for more info.
bottom of page