Just a heads up. transactionShipment.shippingmetho...
# suiteql
r
Just a heads up. transactionShipment.shippingmethod in a suiteql query used to give the shipping method text previously, now its giving the internal id suddenly for one of the accounts. At least 30 or so script started failing because of it. Netsuite did this changes out of the blue.
👍 1
e
We experienced the same thing. Had to deploy hot fixes this morning.
d
Any more updates here? We seem to have customers down because of this.
r
Nope, a colleague was on a call with Netsuite support for an hour, they put him on hold for almost 15-20 minutes. I eventually realized the issue and updated the scripts.
I am happy with this change, sometimes I wanted the internal id in some of the customisation. But had no way to use text or do some hard coding for mapping text to internal id. But they are implementing a change like this without any prior notification is concerning.
d
yeah, did you create a fall-back in case they revert this. These types of changes should be communicated in advance. I assume this was a mistake and they will be reverting it when they continue to get calls. They are about to get a lot from our base.
however, yes, the change is beneficial because it requires us to do one less join I believe.
r
We have all the scripts in bitbucket. And can always revert the commit as long as there are no other conflicts if needed. Pipeline from bitbucket will take care of the rest.
d
Copy code
While we are waiting for the next support representative to take over this case, we would like to inform you that this might be related to one of the on going issue in NetSuite.

This issue seems to be caused by the ShippingMethod field, which has changed from a string to an integer in the TransactionShipment table.

Our engineers are working on a fix.
that’s from NetSuite Support
👍 1
We got a U2 on it.
e
Ours reverted back to previous over the weekend.
r
same, we reverted the code changes as well.