This error may also be reported as: You entered "(null)" into a field where a numeric value was expected. Please go back and change this value to a number.
This may occur when you have "SuitePromotions" in NetSuite enabled and have processed sales and then you disable "SuitePromotions" and you try to do a Created From Return in SuitePOS. These failed transactions end up in the Failed Queue of the device.
This has been logged as a NetSuite Defect. Defect 599806: RESTlet > Transform Invoice to Credit Memo > Cannot read property "promotions" from undefined
At a convenient time, you may want to consider enabling "SuitePromotions" in order to allow the failed transactions to post (after a sync on the device). The longer term solution is a NetSuite fix for the defect.
This is a somewhat misleading (and very rare) error that primarily occurs in the SPOS_Sale script. It occurs when the integration to NetSuite has something wrong with the format that it is expecting. This is around field validation for required ...
This is specific to the Sales Order Module and when Avatax is Enabled. In order to determine the Tax before checkout, the system has to temporarily write a Sales Order and then remove it. Sometimes it may not be removed due to other issues such as ...
"Unexpected Error" can have many causes. It is important that you log with "bug" with NetSuite so they can tell you exactly what it is. One thing to look at is the number of items you are syncing. We suspect that some of these errors could be due to ...
This happens when the NetSuite concurrency limit (set by NetSuite) for your account is exceeded. Typically this occurs when you are simultaneously syncing many terminals at the same time. for example, if you have a concurrency limit of 5 and you try ...
In the context of SuitePOS, this (somewhat misleading) error can can experienced when a return (or sale) is made and the script SPOS Return (or SPOS Sale) is executed. This occurs because the "Customer (or Anonymous Customer)" for which the ...