Inactive membership assigned

We have not seen this specific issue. Do check out all of the hot fixes to 12.1 they were very important to improved stability on our system.

--Tom

On Wed, Mar 25, 2015 at 2:36 PM, Tessitura Technical Forum wrote:

Hi everyone,

Over the past few days, there have been 4 instances where the same old, inactive member level is assigned to a constituent whose donation is processed through the Orders module. Donations of the same amount processed over the web are assigned the correct member level. Donations of the same amount processed through gift entry have the incorrect member level unavailable for selection at the bottom of the listing in gray, and the Member Level defaults to the correct active level.

When the operator opens the Membership to try to change the member level to the correct one, the application displays a long ugly error with Updates VXS Customer Membership, and forcibly shuts down. The only way to correct these member levels is through the back end.

I guess this might be one for TASK. But has anyone seen this? We're in our initial week of post-v12 upgrade and I've been seeing lots of exciting things in the database - I guess I have to wonder if this is related?

thanks for any tips,

frannie



This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical 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!

Thanks for the tip, Tom. I hopefully applied all hotfixes but still saw this behavior.  I ended up going to TASK and it turns out this is a reported defect.  It will be fixed in 12.5. Hope this helps anyone else who sees this behavior.

thanks!

frannie

Thanks for the tip, Tom. I hopefully applied all hotfixes but still saw this behavior.  I ended up going to TASK and it turns out this is a reported defect.  It will be fixed in 12.5. Hope this helps anyone else who sees this behavior.

thanks!

frannie