Same donor, different batch

Our Patron Services Manager asked me this question:

Tessitura is not allowing me to add a pledge to an account in one batch if I have a pledge to the same account in another batch that hasn't been posted yet.  This just started happening last week.  Previously it wasn't a problem.  It is for a matching grant campaign we have going on now. 

This is the message I get: 

Data in tx_cust_membership table is checked out by another batch.  No data moved to mirror tables.

 

Thanks,

Jan LaRocque

Houston Symphony

  • Jan,

    I'm assuming these are two pledges to the same campaign?  If so, it sounds like you might have the "single open pledge" box checked in the campaign. Have you checked that?


    Dale

  • Dale,

    No, the "single open pledge" box is not checked.   Should it be checked or unchecked?

    Jan

  • Former Member
    Former Member $organization
    This indicates that a gift for this customer has been entered in a controlled batch that is open or held.  When a gift is entered for a customer in a controlled batch that affects a membership campaign, the membership rows are moved into the controlled batch's mirror tables and are locked in the database.  This will preclude you from entering another gift or pledge for this customer/campaign until the controlled batch is closed which will unlock the membership records for this customer.  This has always been the behavior for controlled batches.
     
    Bob
    From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of Jan LaRocque
    Sent: Thursday, May 07, 2009 12:48 PM
    To: Robert Bell
    Subject: [Tessitura Development Forum] Same donor, different batch

    Our Patron Services Manager asked me this question:

    Tessitura is not allowing me to add a pledge to an account in one batch if I have a pledge to the same account in another batch that hasn't been posted yet.  This just started happening last week.  Previously it wasn't a problem.  It is for a matching grant campaign we have going on now. 

    This is the message I get: 

    Data in tx_cust_membership table is checked out by another batch.  No data moved to mirror tables.

     

    Thanks,

    Jan LaRocque

    Houston Symphony




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
  • I'm having this same error come up on a constituent when we try and add a pledge.  There are no transactions for this patron in open or held batches but when you look at tx_cont_memb she has an entry in the 'mir lock' column when all the others have zero value.

    Is there a clean up procedure I can run in the same way that you can unlock seats?

    Thanks, Suzanne

  • Suzanne

    I suggest you open a TASK ticket for this problem.

     

    Best wishes

    Tony