Hello everyone,
We're having a little trouble updating attributes recently. I went through and updated every new/returning season ticket subscriber's attributes to make sure it appears under their name on the main ticketing screen throughout the remainder of the next season. This was a lengthy process, and took quite some time.Now, to my horror the next week, I discovered that these updates didn't "take."
Example being: I changed every SUB constituent attribute and extended them to 12/31/2017. BUT when I returned to all of these, they had reverted to saying SUB through 12/31/2016.
I did a little experiment yesterday - Save the attribute with the save icon vs save by hitting the x in the right hand corner and saying "yes" to saving changes. I figured maybe only one of them worked. Interestingly this morning BOTH worked, and all my changes seem to have remained despite closing tessi and batching out.
I've tested a lot of things - maybe I accidentally made the changes in Test mode (nope, the changes don't appear to be present in test mode either, and I know for a fact at one point making changes I was live). Canceling out of orders vs hitting "done" out of orders (makes no difference)So here's the thing: I want to get these things updated and I need to do it before the end of the year, but I would hate to spend more time manually updating something that won't stick. Does anyone have similar experiences or know what could have gone wrong so I can be guaranteed not to repeat my work?
Thanks everyone!
Just took a look and it doesn't seem like I can see anything scheduled to do that.
Few other quick things: I was saying attributes, I meant constituencies (got mixed up, constituencies in under the attributes tab, it's still early in the morning on the west coast) - Sorry!
I also don't have full administrator privileges, so maybe I just can't see the scheduled plan?
Lastly, is this the kind of data that could've gotten messed up due to the DDoS attack last week? I know I'm kind of grasping at straws.
Thanks for your help!
Unknown said: Just took a look and it doesn't seem like I can see anything scheduled to do that. Few other quick things: I was saying attributes, I meant constituencies (got mixed up, constituencies in under the attributes tab, it's still early in the morning on the west coast) - Sorry! I also don't have full administrator privileges, so maybe I just can't see the scheduled plan?
There's a similar utility for Constituencies. I'd ask your administrator. I'd also ask about:
All of these update Constituencies at our organization.
Unknown said: Lastly, is this the kind of data that could've gotten messed up due to the DDoS attack last week? I know I'm kind of grasping at straws.
No.
Tyler:
Is it possible that your organization has a scheduled job that runs the Manage Attributes utility to add/update the SUB attribute with a date of 12/31/2016? With the parameters set correctly, a job like that would easily undo all your hard work overnight.
You can check scheduled jobs from within the application by going to the Tools > Maintain Report/Utility Schedules menu. If you find a job that looks like it’s running Manage Attributes, you can click Parameters to see what it’s set to do.
I'd also check to see if your subscription package history job is being ran with the constituency code in question as that procedure (TP_UPDATE_PACKAGE_HISTORY) will End date your subscription constituency with rules which may not be jibing with what you intended. If so you can modify your Package History SQL job to execute that procedure without supplying the constituency code.