Just had an odd one, a script that’s been in place...
# suitetalkapid
dclarke
06/17/2020, 9:01 AMJust had an odd one, a script that’s been in place for a while that checked if an item was an “Inventory Item” just failed, because the type returned was “Inventory item” (lower case I), anyone else seeing things like this?
p
PNJ
06/17/2020, 9:14 AMYes. The workaround is to change the user preference for Language to English (International). They've messed up English (UK)
PNJ
06/17/2020, 9:14 AMPlease open a ticket with support so that the priority is upped, it's currently a U3 defect
PNJ
06/17/2020, 9:15 AMPNJ
06/17/2020, 9:16 AMDefect # is 590783
d
dclarke
06/17/2020, 9:25 AMAh thank you @PNJ
k
Kushington
06/17/2020, 11:14 AMThanks @PNJ This has broken some of our ETL processes in the Database...
Kushington
06/17/2020, 11:14 AMDo you have a list of the value that were changed?
p
PNJ
06/17/2020, 11:15 AMThe main things are transaction type names & transaction statuses. The easiest thing to do is use the above workaround
k
Kushington
06/17/2020, 11:16 AMI don't think this will fix the valeus in the database, workaround is fine for the UI
p
PNJ
06/17/2020, 11:16 AMIt does
PNJ
06/17/2020, 11:17 AMThe DB values are driven by the language selection, I have tested it
PNJ
06/17/2020, 11:17 AMThey obviously use an abstraction layer when presenting data over ODBC
k
Kushington
06/17/2020, 11:20 AMGreat! Will change this now on Sandbox - thanks for your help
p
PNJ
06/17/2020, 11:37 AMNo worries
PNJ
06/17/2020, 11:37 AMI changed all of our ODBC users this morning & it seems to have resolved the issues
d
dclarke
06/17/2020, 4:07 PMWe’re seeing it affecting SuiteScripts too that do text comparisons of statuses