Some Customers cannot sync Sales Orders / Item Fulfillments from NetSuite

NetSuite has released their fix for Defect 651305: SuiteScript > RESTLet Script > TypeError: Class constructor CounterEntry cannot be invoked with ‘new’ which is impacting ShipHawk and other SDN Developers.

In order to renew the cache, we deployed a new version of ShipHawk bundle - 2021.7.2

We recommend updating the ShipHawk bundle to the latest version 2022.7.2, and expanding the saved search criteria so that un-synced orders (if any) will be imported in ShipHawk from NetSuite.

There are no current updates at this time.

Our engineering team continues to investigate, monitor, and also work toward a workaround that is not dependent on NetSuite's fix.

As previously noted, NetSuite has identified another defect which they have also deemed U2, a critical defect.

Defect 651305: SuiteScript > RESTLet Script > TypeError: Class constructor CounterEntry cannot be invoked with ‘new’ which is impacting ShipHawk and other SDN Developers.

NetSuite is working diligently to address this critical issue.

Additionally, ShipHawk engineering continues to investigate possible workarounds that do not depend on NetSuite’s resolution of these critical defects.

We will continue to share information until this is fully resolved.

We continue to investigate, monitor, and also work toward a workaround that is not dependent on NetSuite.

As previously noted, NetSuite has identified another defect which they have also deemed U2, a critical defect.

Defect 651305: SuiteScript > RESTLet Script > TypeError: Class constructor CounterEntry cannot be invoked with ‘new’ which is impacting ShipHawk and other SDN Developers.

NetSuite is working diligently to address this critical issue.

Additionally, ShipHawk engineering continues to investigate possible workarounds that do not depend on NetSuite’s resolution of these critical defects.

We will continue to share information until this is fully resolved.

We continue to triage this escalation with NetSuite.

NetSuite has identified another new defect 651305: SuiteScript > RESTLet Script > TypeError: Class constructor CounterEntry cannot be invoked with ‘new’ which is impacting ShipHawk and other SDN Developers.

The urgency level of this defect has also been escalated to U2, identified as a critical defect. NetSuite’s management and engineering teams are currently investigating and working on a resolution, with a range for solution within 1-2 days.

ShipHawk’s engineering team deems this urgent and as our greatest priority. We continue to closely work with NetSuite on a resolution and will continue to update you as we know more.

We continue to monitor the issue and are working diligently with NetSuite technical support to resolve this issue as quickly as possible. We will continue to provide updates until this issue is fully resolved.

We continue to triage this escalation with NetSuite.

NetSuite has acknowledged Defect 651122: SuiteScript > RESTLetScript > TypeError: Class constructor CounterEntry cannot be invoked without 'new' which is impacting ShipHawk and other SDN Developers.

NetSuite has escalated the issue to "U2" and understands this is a critical defect with U2 priority, NetSuite's target resolution period is 1-2 days. That said, the resources we are working with are telling us they are confident it will be resolved today.

Within the next week, we will provide you with a full post-mortem, including our plans to further mitigate unplanned changes made by NetSuite and/or dependencies between ShipHawk and NetSuite.

If you are experiencing this issue, you can directly reach out to NS and reference NS support case #4491650, Defect 651122

We continue to triage this escalation with NetSuite.

NetSuite has acknowledged Defect 651122: SuiteScript > RESTLetScript > TypeError: Class constructor CounterEntry cannot be invoked without 'new' which is impacting ShipHawk and other SDN Developers.

NetSuite has escalated the issue to "U2" and understands this is a critical defect with U2 priority, NetSuite's target resolution period is 1-2 days. That said, the resources we are working with are telling us they are confident it will be resolved today.

Within the next week, we will provide you with a full post-mortem, including our plans to further mitigate unplanned changes made by NetSuite and/or dependencies between ShipHawk and NetSuite.

If you are experiencing this issue, you can directly reach out to NS and reference NS support case #4491650, Defect 651122

We continue to triage this escalation with NetSuite.

NetSuite has acknowledged Defect 651122: SuiteScript > RESTLetScript > TypeError: Class constructor CounterEntry cannot be invoked without 'new' which is impacting ShipHawk and other SDN Developers.

NetSuite has escalated the issue to "U2" and understands this is a critical defect with U2 priority, NetSuite's target resolution period is 1-2 days. That said, the resources we are working with are telling us they are confident it will be resolved today.

Within the next week, we will provide you with a full post-mortem, including our plans to further mitigate unplanned changes made by NetSuite and/or dependencies between ShipHawk and NetSuite.

If you are experiencing this issue, you can directly reach out to NS and reference NS support case #4491650, Defect 651122

We are continuing to investigate this issue. We have escalated to NetSuite and are working with them for resolution. Our next update will be within 60 minutes.

We are continuing to investigate this issue. We have escalated to NetSuite and are working with them for resolution. Our next update will be within 30 minutes.

NetSuite is experiencing an issue impacting multiple partners and current NetSuite users. We are working with their team on an immediate resolution. Our next update will be within 30 minutes.

NetSuite has rolled back a change they made last night that caused issues for SuiteApp Developers who use NApiVersion 2.x. According to NetSuite technical support, their changes are reverted now, but some files in NetSuite may still be cached.

If you are still experiencing issues, it may be due to file caching.

We will continue to discuss this issue with NetSuite to learn what mitigations can be put in place to avoid an issue like this in the future and will provide our findings in a post-mortem.

At this time, our engineering team is still investigating this issue.

NetSuite users are facing issues with item fulfillments and order sync in ShipHawk. When NetSuite users save an Item Shipment record, the error is shown:

TypeError: ItemFulfillment.find is not a function [at Object.afterSubmit (/SuiteBundles/Bundle 161164/ShipHawk (2)/event_scripts/shiphawk-update-fulfillment-event-script.js:55:35)]

This was first reported at 9:12 PM PDT. We are currently investigating and have reached out to NetSuite support. No changes that could cause the issue were made by ShipHawk.