Problems with transactions, transaction statuses a...
# general
p
Problems with transactions, transaction statuses and other names being different? Look no further!
Workaround: Change the user preference (Home icon->Set Preferences, Localisation->Language) to English (International) or English (US). This requires the Multi-Language preference (Setup->Company->Enable Features->Company->International->Multi-Language) to be enabled - I AM NOT SUPPORT - DO NOT ENABLE UNLESS YOU ARE SURE OF ANY SIDE EFFECTS. Be wary of date formats, so English (International) is probably the way to go. If in doubt, open a support ticket
This will correct the names in the UI, in workflows, saved searches & also through ODBC
k
Point to note, if you don't have Multi Languages enabled you won't be able to set the above preference
Not sure what it would affect integration wise if it's enabled just like that
p
Yeah, I said elsewhere that I cannot recommend just setting it. I am not support
d
Just my luck our account has multi-language switched off. I daren't try enabling it, as we're only just getting back to normal after things kicked off during lockdown.
p
Prolly worth opening a support ticket & seeing what they recommend. If the workaround doesn't work for you it might bump the priority for us all
d
I've got a case in and just awaiting a response. Our financial year is about to end, and we're about to stocktake, so can't afford system issues. I've mentioned this in the case.
They've just come back saying U3. I've just replied stating that it's unacceptable to us, as our year end is imminent and we've got staff who could be stocktaking being tied up with incorrect item numbers on pick notes, no bin numbers, etc due to scripted search issues. I've also CCed our Netsuite account contact in the hope that they'll escalate it.
k
Same - Its logged as U3. Will be escalated via account manager
p
The one I logged yesterday is also a U3
What defect number have you been given? Mine was 590783, same as @chri55tof
d
Same here.
m
+1 for a U3 defect escalated to our account manager here (no response) - Defect 590783. Complete nightmare.
p
Still not fixed. Grrr
d
Same here. We had an hour of downtime last night for planned maintenance, so I'd hoped it might get fixed then, but obviously not.
I'm assuming there's still no public facing way to check the status of a defect?
k
Our defect is 590783. We referenced the number on this thread
d
Our production account was fixed overnight. Sandbox has not been done yet.
p
Same. I have requested that our sandboxes are done