Constituency Nightmare

Hey Brandi,

We had a very similar thing happen.  Our nativity with a schedule bit us.

I was able to update the start and end date with this.  I strongly advise doing this in your Test environment first and using begin tran/commit tran to make sure you are updating the people you really mean to update.

update tx_const_cust

Set start_dt = '2016-04-10 00:00:00:000'

where constituency = 47

update TX_CONST_CUST

Set end_dt = '2016-04-11 00:00:00:000'

where constituency = 47

Dot

From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Brandi Cline
Sent: Wednesday, November 16, 2016 1:16 PM
To: Dot Krebs <dkrebs@actorstheatre.org>
Subject: [Tessitura Technical Forum] Constituency Nightmare

So, we somehow managed to set constituency start dates and end dates to the same date on a very large number of constituents. (10/26/2016)

This is causing the constituency to show in their header, despite the fact that it's not actually active.  We have multiple utilities running that should be updating these constituencies, but Tess seems unable to touch the ones with the same start and end date.

Is there a utility of some sort that would change either the start or the end date for these instances?  We've tried the Manage Constituency Utility with every combination of parameters that we could think of and it hasn't worked.  So far our only solution has been to go into each record with the error (over 9000 records) and manually adjust the end date.

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!