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.

Parents Reply Children
No Data