Articles in this section

Resolve Amazon error: Invalid sublist or line item operation

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:

  1. Retry Data:

    1. Click Retry Data in the settlement flow. This often resolves the error:

    2. If the error persists, further checks are required: 

      • Verify if the invoice is visible on the Customer Payment page or included in the 10,000 invoice limit.

      • If the invoice is not visible, identify why it is excluded or process visible invoices to free up space, allowing additional invoices to fall within the 10,000 limit.

You can also try the following steps to resolve the error:

  1. Apply date range filters:

    • If the required invoice is not in the oldest or latest 10,000 invoices, apply a date range filter using the "From" and "To" date fields in the sublist to narrow down and locate the invoice.

  2. Customize filter criteria:

    • Refine the sublist further by customizing filter criteria for better flexibility in locating invoices.

  3. Ensure user/role consistency:

    • Confirm that the user/role modifying the sublist matches the user/role authorized for the flow connection to avoid permission-related issues.

Was this article helpful?
1 out of 4 found this helpful

Comments

4 comments
Date Votes
  • 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. 

    3
  • Chris Harper I've come back to this tip a couple of times now. Just wanted to say thanks.

    1
  • We encountered a use case where neither the oldest 10,000 invoices nor the latest 10,000 invoices were part of the settlement we were trying to reconcile. By applying a date range filter to the sublist (using the "From" and "To" dates), we were able to efficiently cherry-pick orders from within a large sublist of open invoices. Further customization of the sublist filter criteria has provided even greater flexibility.

    That being said, it is crucial to ensure that the user/role modifying the sublist is the same as the user/role that has authorized the connection for that flow step.

    2
  • Thanks, Brian Kozanecki, on behalf of anyone else stuck where you broke through. We'll definitely add your well written advice to the troubleshooting tips. 

    1

Please sign in to leave a comment.