I use the NetSuite x Square IA and run into daily errors that take a while to diagnose. The two errors I get are:
Failed to add Square Order#xxxxxxxxx. Failed to save record because Please configure the inventory detail for this line.
And:
Failed to add Square Order#xxxxxxx. Inventory not available at the location# x for item xxxx.
The second is much more helpful as I can build a tool to lookup the item and locations so we can rectify the issue, however with the first one I have to cross reference our inventory against the orders items and this takes a while if its a high volume of errors. The correct solve to this issue is to fix the cause of the errors not symptoms but that is a businees change and for now I need this fix.
Any advice on how to access the post hook scripts(if I can change the error functions) would be helpful or any other ideas anyone has.
Can I use the Celigo error API to retrieve more information about the error based on its error id or trace key.
Regarding the first error, this typically occurs when inventory detail is required by NetSuite but there is insufficient information provided. This usually happens when there is not enough bin quantity, inventory status, or lot/serial number available for the item being posted.
Could you please check whether there is sufficient quantity available for those? If there is, you may try creating a sample transaction directly in NetSuite to see what inventory details are required.
If you are using lot-numbered or serialized items and there is sufficient quantity available, you may also consider enabling the checkbox shown below.
For bins, the flow typically relies on NetSuite to auto-assign them.
Regarding your question about accessing the hook, unfortunately, this is not possible since it is a prebuilt integration. Celigo integrator.io has certain limitations on what can be accessed or modified within prebuilt flows.
Yes, it is always due to lack of inventory. I’m looking to be able to use the errors to diagnose which item I need to transfer into the location for the error to clear and hoping to be able to extract more from the error key if able.
I will take a look at the checkbox and see how it goes!
Unfortunately, for the Integration App only has the capability to download the error messages and not the items listed within the retry data. However you may use our Errors API endpoints, and use the GET under /data.
