This site was built to compliment the existing NetSuite Professionals Slack Community by adding a means for members to easily find answers to common questions and to create a searchable database of those questions and answers.

NetSuite Professionals

Screenshot 2024-12-04 at 10.50.35 AM.png

so, in the process of debugging something, NS told me to set an existing WF to run on create of transactions.  I was a bit paranoid of the impact, so to test this, I created a test WF that ran on create of Sales Order and just created a log message so I could watch when it was running.  I noticed that it was running several times a minute … triggered from our website … including in the middle of the night, etc.  I asked (about 10 times since April) what was triggering it.

their answer, after months of incredibly annoying back and forth was the above.

Completely useless answer - it's their product they should know how to support it or at least know how it works

NS Support is clueless and most of the time useless, I do everything I can on my own before reaching out to them.

there are some OK folks in support but most are clueless.

Or they call you at 11:30 pm your time, and they get upset that you can not work with them. I was like dude, I am in bed already!

We just had a tech crisis where an unnamed partner's data was being throttled into NS.  And I have to praise NS Support/Engineering for getting it figured out and fixed.  Took several days and some (very) late nights, but after seeing this, I'm really relieved that they figured it out.
/bullet -dodged

I am shocked by this message to you though. Wow.

I had support tell me that my issue was, and I quote, 'is probably nothing they can do about it, it is a fact of life at the moment I'd say'.  I'd love to be able to turn round to my user base and tell them it is what it is and they just have to live with it!

oh yeah I got the “fact of life” message on a previous ticket

```Good day, Hope this email finds you well. I have reached out to our engineers and they have said that the problem is that even though you do not use any legacy functionality directly, it is still used by the workfow to perform the logic.

And since they will not be fixing internally the legacy functionality, this error as well will not be fixed. With this, they decided that this is considered as fact of life.

As much as I wanted to further help, we have no more action item on this case, hence, we will be closing this,

I am really sorry for the frustration and thank you for your understanding regarding this.```

fact of life as a term for stuff they know is wrong but don't want to fix is deeply orwellian of them.

it’s f*cking unprofessional is what it is