@igorp Wrong subsidiary?

Eventually it turned out to be a NetSuite SS 2.0 defect

How did you get this resolved?

Sorry man, missed the notification. It wasn't resolved, It's a SS 2.0 defect. Unbelievably, the defect was opened as U5, meaning 4-6 week, so we are now trying to escalate it and talking with the account and region managers. Defect 475182 I think that you should also open a case regarding this issue and reference this defect number. If the amount of affected accounts will start growing, maybe they will handle it more seriously.

Thank you! I will open a case and reference the defect in hopes to get this escalated! Outside of you telling me it was resolved, having a reference number to build a case against is the next best thing I suppose. I must have missed the release that caused the defect too, cause I didn't recall there being a release on the 7th but thats when it started (i also am not the best at paying attention to the small releases)

It looks like it's the 7th indeed, probably some hotfix that messed it up. We are ongoing 2 UAT's so the system is heavily used and tested and this error wasn't encountered prior to this date.

I submitted my case yesterday, referenceing the Defect # and they said they moved it from a U5 to a U4, so I hope that helps @igorp, 1-3 weeks instead of 3-6

At least something.... we are pushing the region managers to handle it. It's ridiculous that a defect that is preventing something so common as SO editing is U5,U4. It should be critical since basically it's a business down situation.

i agree