Opening a ticket for tech support

[WilsonFlyer]

And the vicious cycle continues with a blow off. Got an email saying nothing was wrong and that they had left a waitlist on my dashboard so I could see it and delete it and that they had completed it with my account. Tried again. Still doesn't work.

I'm convinced they're not going to fix it, but now it's getting personal and insulting. The email was borderline condescending and it kinda ticked me off. I replied kindly asking for a resolution but I may be fixin' to get on the phone. I once had an employee tell me that there was nothing more dangerous in this world than me with a telephone and time on my hands. It's Friday and I have nothing to do. Connect the dots. Looks like that's where we are, unfortunately.

 

[n2mm]

I’m so sorry to hear that. So frustrating. I’m guessing that will happen to me Soon too.

 

[WilsonFlyer]

Well, I realized something I actually hadn't tried this morning. I tried it, and it worked. I tried my theory several times and it worked/failed every single time. I ended up calling and waiting for an hour to talk to somebody in MS. They were able to reproduce the failure and it working by replicating what I had found. We got the DVC IT group on the phone and having an IT background helped here because I already knew it was an overflow problem by this point. I never talked to the IT person, but my MS confirmed that the lady in IT had indeed found the problem/bug but wasn't sure if or when it may be fixed, but at least it's documented now. More importantly, I at least have a work around.

Apparently there was one thing I actually hadn't tried in all my testing. For the sake of brevity, I'm not going into elaborate detail here, but it a problem that very easily could happen to others so here goes.

It appears that my cached address record (street address specifically) has a bunch of acronyms and abbreviations in it. It is the one that my account was created with. Every time I make a reservation, at the end, an address correction box pops up with what appears to be a fully spelled out street address probably read from master tables at the USPS. That "suggested" correction is checked by default as opposed to the one I put in when my address changed years ago (They changed the name of my street/road. I didn't move.). OK. So they want to use that one. Fine by me. Submit. All well and good. Next screen is the "agreement"/last page to submit. I "agree" and submit and it fails. Here's the stickler. The subroutine that actually MAKES a reservation can hold the contents of this address correction in its entirety. The waitlist CANNOT. This has now been confirmed by IT. So my answer? Never choose the "Suggested" address change. Apparently I had never tried that. Mostly as a safety measure. I want(ed) everything to be documented the same. I always took the suggested address and had no reason to think I shouldn't. Every reservation I've ever made has that suggested address. I didn't WANT them to be different. But I can't do a waitlist that way. At least not for now. Maybe never. Who knows.

Is my problem fixed? No. But I have a workable solution. Not the same thing, and I don't like it, but I've hit the point of diminishing returns in trying to fight it. I've found a way to make it work, and I can live with it.

 

[n2mm]

Very interesting. I’ll remember to not select that. My address changed too. We didn’t move, but they changed our street names and numbers years ago.

 

[WilsonFlyer]

Very interesting. I’ll remember to not select that. My address changed too. We didn’t move, but they changed our street names and numbers years ago.

It's fine so long as it doesn't overflow space available. Apparently a problem in the working waitlist record but not in the working actual reservation record. Who'da thunk it? Now I remember why I stopped writing code 35 years ago and went into networking.