Constituent Update Batch - Update Existing Attribute in Collection Field - End Date

Mimi Klimberg · February 2021

Can you use the Constituent Update Batch to end date a specific attribute inside an attribute group. When I try to do it, BBCRM adds a new attribute with the end date - instead of end dating the current attribute.

Note that the constituent may have more than one attribute in this group associated with their record. I want to select a particular attribute and end date it.

We currently need to do all of this by hand. HELP.

Liz Hackett · February 2021

Hi Mimi,

You can't use a batch to update/end date an attribute, but you can use a datalist and default values to put the end date in the end date field.

There is some info in this post but if you have further questions, I'd be happy to jump on a quick call with you (FYI Im in Australia so we'd have to sort out the time diff!)

Has your organisation set up data lists in CRM?
https://community.blackbaud.com/forums/viewtopic/511/43726

Mimi Klimberg · February 2021

Yes. We do use data lists for integrities but I am not sure I understand exactly how to do this. I would greatly appreciate a quick call. We have so many old attributes that need to be end dated (thousands). I need a reasonable way to do this -- manual would be painful. How can we connect. MIMI

Lois Smith · February 2021

Mimi, yes, you can end date specific attributes in a constituent update batch. You have to include the specific system record ID for the attribute you want to end date in your import file.

Set up a time with me and I would be happy to show you.

Stephanie Boyce · March 2021

Hi Liz - we use the constituent update batch to update attributes every year. As long as you have the GUID for the specific attribute you want to update/end date we have not run into any issues.

Stephanie

Constituent Update Batch - Update Existing Attribute in Collection Field - End Date

Comments

Categories