First, I should mention that we have a high threshold for matching for reasons related to BBIS Donation Batch.

Changing the constituent in the Membership Dues batch involves:

-Opening the Dues Batch

-Clicking on the Bill To field

-Searching for the correct constituent - and selecting (this is when the transaction details are removed)

**If the constituent doesn't exist, our gift accounting department creates the constituent outside of batch due to the more complete functionality that exists in the Constituent - Add Data Form

-- I do think it will also be common for the case of Gift of Membership as well.

Hi Greg,

Can you provide more details on your process for changing the constituent?  Is it duplicate management?  Gift of Memberships?

Thanks,

Trit

I didn't mean to post this without a summary. Hopefully this comment will be sufficient. 

We just started using the BBIS membership module and have found the functionality of the supporting batches to be highly frustrating. When you try to attach a membership batch record to a constituent, it deletes all of the relevant information from the batch record (membership type, amount, etc). Support informed me that this is "working as designed" because there are instances where a change of constituent would change what options are available (i.e...you cannot get a renewal if you are not a current member).

I would like to suggest that the batch be changed so that, if you change a constituent on a membership batch record, it would raise a validation error as opposed to just deleting all the pertinent information from  the record.

With the current working behavior of the batch, we either have to come up with a customization to keep track of what the customer actually bought...or we have to rely on writing down every transaction on a sticky note before attaching a transaction to the correct constituent.