Relationship set ID is null when relationship is created in Constituent Update Batch

When relationships are created in the application, a Globally Unique Identifier is created to identify the relationship pair.  This ID is not being created when the relationship is generated via Constituent Update Batch.
Download and install the latest patch which contains all fixes from previous patches. If you are running an older version, download and install the latest version and then the patch. 

Steps to Duplicate

  1. Manually add a new spouse relationship to a constituent via the Relationships tab or Add Spouse tack on a constituent record
  2. Add a new spouse relationship via Constituent Update Batch including the following fields:
  • Spouse lookup ID, Spouse, Spouse relationship type, Spouse gender, Spouse reciprocal type
  1. Query on the constituents from both examples, outputting the Relationships\Relationship set ID
  2. Observe the field is null for the batch relationship, but populated for the manually created relationship

Environment

 Blackbaud CRM
 4.0
 4.0
 Service Pack 10

Was this article helpful?


Thanks for your feedback! Did this solve your issue?

Comments (optional):


Thanks for your feedback!
We're glad it was helpful but sorry it didn’t solve your issue. If you need assistance, click Chat with Support below.
We’re sorry to hear that. Please tell us why.

 I don't like how this works.

 The answer is confusing.

 The answer didn't match what I was searching for.

Additional Comments (optional):


Thanks for your feedback! If you need assistance, click Chat with Support below.
Thanks for your feedback. Help us make our products even better by sharing details in our Idea Banks or our online Community.
Thanks for letting us know. We'll work on clarifying the information in the article. If you need assistance, click Chat with Support below.
Thanks for letting us know. We'll work on updating the search engine to return more relevant results.