Hey... having a weird bug that is an open case but...
# general
s
Hey... having a weird bug that is an open case but we are still struggling. We import Sales Orders from Shopify and we set the shipping cost manually. When we perform any edit to the sales order it reverts the shipping cost to waht is in the Netsuite Shipping Items list for that shipping method. Only started happening early last week. Is this happening for anyone else?
m
We had a user report something that I believe is the same issue though I haven't been able to verify it. Has support's response been of any use so far?
a
This has been happening to us as well. For a magento integration but otherwise the exact same issue - started on 6/13. I'm trying to get an answer from support now - if y'all learn anything, would love to hear it.
s
support is saying the issue is with one of user event scripts but I call BS. They have shown in their QA environment that by disabling all of our scripts it doesn't exhibit that behaviour, however, my gut tells me they our scripts are not the issue. I made no changes to any scripts last week
are you using Avalara Avatax by chance?
a
we are using avalara, yes. my rep has at least admitted it may not be a script issue, which i agree - we haven't touched any scripts in like 2 years so i know for a fact it's not a script issue.
one weird thing i noticed is that on transactions before the 13th, you can see an "impact change" in the system notes (triggered by a script update to the record to set a location field), but the new/old values are identical. however starting on the 13th, that impact change also occurs with the setting of that location field, and this time it's an actual change to the amount by adding/updating the shipping cost.
which to me suggests that it's not a script issue as the script was always triggering a "recalculation" of the shipping/amount, it's just that it used to realize it should stay the original amount, and now it's overriding it or something.
m
We also use Avalara, though we haven't updated the bundle in over 3 months so I'd be surprised if this issue was due to something on their end. We do update our scripts pretty often but I haven't made any changes recently that should be affecting the shipping charge, and we don't have any scripts that set the shipping item so I'm confident it's not an issue in our scripts.
Have either of you gotten a defect # from support or are you still trying to convince them that it's a real issue?
a
no defect number yet 🙃 if I do get one i'll share it here so y'all can tie your cases to it as well
s
I have a case number but have not heard back if they have filed a defect
Do you guys have a Case number?
m
I filed Case 3457211 yesterday, but haven't heard anything substantive back yet.
a
my case # is 3456135 - i've been able to show in Sandbox that the same behavior occurs outside of a script as well, so I'm hoping they will file a defect soon.
s
Thanks
my case number is 3452014 if you want to add it to your case. I reached put to NS support and added your case #'s to see if it can help expedite the fix
out not put
a
Thanks! i've also shared both of your case #s with my rep - hopefully that will push them to realize it's a defect since our accounts are all unrelated, using different scripts, etc
s
quick ? .... Do you have Bronto installed?
m
We do not. I did receive an update on our Case that supposedly an e-fix released late last week has fixed this issue, but maybe only for transactions created after the fix was released (6/20/19)? That doesn't make a ton of sense to me and I don't know how to reliably test that, but I wanted to pass it along in case it could help either of you.
a
Huh, good to know. I ended up finding a workaround on Friday - we had a script + workflow combination which was clearing and then re-setting the location field with the same value (just mistakes made years ago with people who weren't as familiar with NetSuite). Removing that workflow/script section, so that the location just stayed what it was originally set, stopped the re-calculation of shipping for us. Obviously there is (was?) still some defect because it had been working fine for years, but if y'all happen to have anything setting a location value that you can remove/avoid, that might be worth trying if that e-fix didn't resolve it.
Ah and no, we don't use Bronto
Just got a defect number finally, in case your reps haven't associated it yet - 545596
m
That's interesting, we got defect 545633 for this issue ~30 minutes ago. What's the subject of yours? Our is
Edit Sales Order/Invoice > Add New Items > Shipping Cost Changes to the Default Value
. Maybe getting all of our cases on the same defect will up the priority of it.
a
Mine is called 'Sales Order/Cash Sale > Shipping Cost changed by a Scheduled Script', so I guess they are creating different defects since we technically have different "triggers" of the recalculation of shipping cost.
m
That's weird, I'm assuming they're the same underlying issue. In any event, I'm glad we've at least got defects filed - hopefully they'll actually get a fix pushed out soon enough.
a
Ha, just got an update that actually my defect is expected behavior, due to another defect 511881 which was fixed on june 12th. They said "If you do not want to change the shipping cost, kindly update "shippingcostoverridden" flag to "T". nlapiSubmitField ( 'salesorder' , recordId , 'shippingcostoverridden' , 'T' , false );"
So i guess that actually all this time the fact that the shipping cost wasn't being re-calculated was a defect that they're saying they fixed...
m
Wow, that's pretty ridiculous. We've been on NetSuite for over 7 years and this is the first time our shipping charges are automatically updating, are they saying that they've let that defect sit untouched for that long?
Also, support giving examples like that in SS1.0 instead of 2.0 seems like something they might want to start changing - I thought they were trying to push people into using SS2.0 whenever possible?
a
wow, yeah, my client has only been on netsuite for ~3 years which is still absurd but at least somewhat reasonable given netsuite's bug release schedule. but 7 years! how do you push a bugfix for something that's been broken for 7+ years on a random wednesday without warning, especially when it affects financials
m
Yeah, as much as I hate to say this as it relates to other long-standing defects, after a certain amount of time (and 7 years definitely qualifies), it's not really a defect anymore, it's just the way the system works.
e
Same issue but NS support will point to the script because the log shows the 'Total' value changed along with the field that the script set. I can't undeploy the script since it is prod and sandbox is too outdated to reproduce the issue.
s
I got the "This is now expected behaviour" line as well. I have taken steps to revert the shipping cost to what comes in via Shopify, and I have also checked the shippingcostoverridden flag as well. will report back tomorrow on how it goes when we go to bill our orders from today
m
I had no idea that the shippingcostoverridden field existed, but after playing around with it for a couple minutes it does appear that it's a reasonable solution for this issue. Additionally, it seems like setting a manual shipping cost in the UI automatically sets that field to true so at least for the bulk of our orders that alone should resolve this issue (except for a few that seem to still have the flag set to false - I wonder if that was the real defect that's already been fixed).
Thanks all for your updates - I'm curious to see what comes of our case since I haven't gotten that response yet, but at least we've got something functional to go off of for now.
s
Good News! shippingcostoverridden fixed our issue. We now set this to be true when we import the order and we are able to modify the SO after the fact and the shipping cost remains. Big Thanks for your help! 👍🏻👍🏻
This is going to save us many hours a day! Now NS just needs to fix another defect (unrelated to this one) and we will back to normal
w
Hey, started noticing the same issue and found this thread. I can’t find this shippingcostoverridden anywhere…can’t search it either. Any ideas why?
I looked to see if it was hidden on the form (although that wouldn’t matter for the search) to no avail
m
I'm pretty sure it's only accessible by script - I couldn't find it anywhere in on the forms or in searches.
a
yeah it seems to be a script-only field for some reason
s
yes. you can only set it via script