about 2-5 weeks before they started updating accou...
# randomk
KevinJ of Kansas
10/16/2020, 2:19 PMabout 2-5 weeks before they started updating accounts to 2020.2 - there was an English UK update that threw a bunch of stuff out of wack.
p
PNJ
10/16/2020, 2:46 PMYeah, that was the worst deploy I've ever seen
PNJ
10/16/2020, 2:46 PMThink they've given up on that now!
k
KevinJ of Kansas
10/16/2020, 6:14 PMThe worst part was the "oh hey this is how everything works now - but we aren't gonna warn you that we're changing it so you can update ALL your scripts that reference this"
s
stalbert
10/16/2020, 7:15 PMinteresting - it was just a language update?
p
PNJ
10/16/2020, 7:18 PMYes. They renamed transaction types and statuses too, which royally broke lots of things. They also presented the new values over ODBC, which killed lots of our ETL
PNJ
10/16/2020, 7:18 PMThe UI was also a complete mess, with a mixture of upper & lower-case names all over the place
PNJ
10/16/2020, 7:19 PMThe best one was workflows. You know how they have a “state”? That was renamed to “county” in the workflow UI 😂😂😂 (lol)
🤣 1
PNJ
10/16/2020, 7:23 PMmessage has been deleted
s
stalbert
10/16/2020, 7:26 PMthey didn't rename any fields though, right? that would be truly troublesome
k
KevinJ of Kansas
10/16/2020, 7:28 PMIf i recall they did rename a couple standard fields
KevinJ of Kansas
10/16/2020, 7:28 PMsomething about shipping i think
KevinJ of Kansas
10/16/2020, 7:29 PMdefinitely changed statuses.
s
stalbert
10/16/2020, 7:29 PMstatus string values you mean?
p
PNJ
10/16/2020, 7:29 PMYes
k
KevinJ of Kansas
10/16/2020, 7:33 PMswitched number of Ls in fulfilled - everywhere
s
stalbert
10/16/2020, 8:19 PMyeah, that's why I try to avoid string values for any lists, but recognize it's unavoidable in some places.