**we are self-hosted**
Is is possible that this utility deleted card numbers my coworker recently entered?
My coworker entered 5 card numbers yesterday. I ran the utility last night and this morning the card number were gone. The documentation here says it deletes inactive cards. My assumption is that my coworker didn't mark these as inactive when she entered them yesterday.
Any thoughts?
Ashley Elliott
Database Administrator
St. Louis Symphony Orchestra
314-286-4198
ashleye@slso.org
Yes. We have an open ticket about this, and have had for about six months, I think.
Thank you!!!
Ashley
(I don't know what I would do without these forums)
Hi everyone,
Thanks for the posts. Noting that after seeing the discussion here I did some investigation on status of the original ticket, and as recently as this morning there was internal activity with new information about the issue and next steps. Support and the development team have been collaborating on identifying the underlying issue, and based on what they found along with the info in the original ticket we likely have a defect to look at. It's been moved along with that priority, and we'll have a look at getting it fixed up.
Thanks,
Chris Szalaj
Product Owner, Business Facing Products
Tessitura Network
Thanks, Chris -- this seems like a rather important bug to note for folks, especially in a time when credit card accounts are so important for refunds. Can you share any additional details or what the investigation into the underlying issue has found. We just ran this utility as part of our normal new fiscal year processes and, while we excluded all individuals with Ticket History in the past two seasons, it would be helpful to know how broadly this issue applies to organizations and the nature of it, so we can mitigate as needed.
DGomez
Thanks.
Hi Daniel, At this time, the defect appears to be related and isolated to storing the account id (act_id parameter in CheckoutEx4) with orders saved via the API when Hosted Payments are used online to authorize payment for an order. When the order save occurs via TNEW, the act_id value is being saved as 0 in the Tessitura database. This results in the purge utility not recognizing it as a card that has been used and purging the card.
At this time, we believe the issue is isolated to orders using hosted payments online.
Chris
Hey Chris,
Wanted to reach out to follow up on this. With the newest service pack release was this defect resolved? My colleague did not see it mentioned in the release notes nor was it listed on the defect list from what she could tell. Do you have a defect number we can check?
-Maureen
Hi Maureen,
The card to keep an eye out for is DEV-7097. We currently have this in the February service pack, 15.1.17.