Error code: sss_invalid_sublist_operation
Error message: "Failed to create, update/transform record because You have attempted an invalid sublist or line item operation. You are either trying to access a field on a non-existent line or you are trying to add or remove lines from a static sublist. Tip: Please make sure that all the line items that you're trying to use exist on the record. Settlement details: Settlement Id# 0123456789, Amazon AFN Order# 123-9999999-000000."
Reason: Settlement Payment flow creates Customer Payments in NetSuite via Transactions > Customer > Accept Customer payment. This page has a limit of 10,000 transactions. If the Invoice the Settlement is trying to pay does not show on this page, that is when you will see this error. Due to NetSuite limitation, customer payments can’t be applied against an invoice when the customer has more than 10000 open invoices.
Resolution: Usually, this gets resolved when you click Retry data. If it doesn't resolve you'll need to further check:
- If the invoice is showing on this page or if it is included in the 10,000 limit.
- If it is not showing, you'll need to check why it is not showing or process those showing on the page first to free up some space so that other Invoices will get in the 10,000 limit.
Comments
I found a workaround for this. It's not perfect, but it works fairly well.
For the user specified in the Celigo -> NetSuite connection settings, go toTransactions > Customer > Accept Customer Payment screen where the 10k invoice limit is imposed. Now, change the sort the list of 10k invoices. You do this by clicking the column header names in the columns listed in the sublist view, it might take some time for the sort to apply (it's a ton of data). This will change the range of invoices shown on the screen. The login used by the connection will now see the same sort as the logged in user. When you re-run the flow, you should get more successful payments applied.
Chris Harper I've come back to this tip a couple of times now. Just wanted to say thanks.
Please sign in to leave a comment.