NetSuite Script Error: Customer Sync - SSS_INVALID_SEARCH_COLUMN - taxable

NetSuite Script Error: Customer Sync - SSS_INVALID_SEARCH_COLUMN - taxable


This can be caused when SuiteTax is enabled in a NetSuite Account but is not enabled on POS Setting. It can also be caused by SuiteTax being enabled on POS Settings and SuiteTax installed in a NetSuite account but not provisioned correctly. In the latter case, contact NetSuite Support.
​

If SuiteTax is enabled in your NetSuite account, you must purchase our SuiteTax Module and enable it in POS Settings.

Enable SuiteTax




    • Related Articles

    • NetSuite Script Error: INVALID_KEY_OR_REF - Invalid entity reference key nnnnnnnn

      When a Sale or Return is written to NetSuite you may get this error thrown and the transaction appears on the Fail Queue of the device. eg. Request failed: bad request (400) {"error" : {"code" : "INVALID_KEY_OR_REF", "message" : "Invalid entity ...

    • NetSuite Script Error: SSS_INVALID_SCRIPTLET_ID

      Throughout various points in the App you may receive this error if one or more SuitePOS Scripts have been removed, de-activated or un-deployed. To resolve this issue you need to re-activate or re-deploy the scripts.

    • NetSuite Script Error: Item Sync - Unexpected Error

      "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 ...

    • NetSuite Script Error: NetSuite Data Center Error During a Sync

      Once in a while, during a sync, a "NetSuite Data Center" error message may pop up. This is thrown by design and is as a result of SuitePOS not being able to obtain the data center endpoint NetSuite uses for the REST API's for your account. This is ...

    • NetSuite Script Error: SSS_REQUEST_LIMIT_EXCEEDED

      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 ...