Error in import : ignoring current record as ignoreExistingRecordsOnAdd is true    Found a record with id 73422

Comments

5 comments

  • MaElena Hernandez Instructional Designer
    Celigo University Level 4: Legendary

    Hello. Is this an issue in a Celigo University course? If not, you may want to post this in the general Community discussion area. 

    0
  • Kathyana Rule Community moderator Technical Writer
    Engaged
    Celigo University Level 2: Seasoned

    Hello JCS Celigo Integrator 2

    I have moved your post to the Troubleshoot custom flows section for more visibility. Thanks! 

    0
  • Scott Henderson CTO
    Celigo University Level 1: Skilled
    Answer Pro
    Top Contributor

    I recommend contacting customer support. If you want help from the community we need more info. Can you share screenshots of your flow, the import drawer, the error drawer, etc...?

    0
  • JCS Celigo Integrator 2
    Engaged

    I have created a ticket to the Celigo support team for help.

    It is a custom flow. In this flow , Current working of the flow is in export side reads the sales order details from NetSuite and In lookup, the shipped shipment details get from the ShipBob[third party]. Import side, create Item fulfillment in the NetSuite for the shipped shipments (When we unchecked the ignore existing record  checkbox in the import side).

    Actually, we need to check the ignored existing record check box in the import side of the flow. when I checked the check box and give the filter. If any condition occures, It always ignore the records and didn't create item fulfillment in the NetSuite. 

     

    Import side

    Import mapping

    0
  • Steve Klett Strategic Partner
    Celigo University Level 4: Legendary
    Answer Pro
    Great Answer
    Top Contributor
    Awesome Follow-up
    Engaged

    If it's finding an Item Fulfillment transaction in NetSuite with a custbody_jcs_shipbob_ifshipmentid with that value, then it's existing. You mention 73422 from the error, but from the screen shot the shipmentid is something different.

    When you encounter this error, take the ID that is reported (e.g., 73422) and search NetSuite for a transaction with that value in the custbody_jcs_shipbob_ifshipmentid. Once you find it, you'll have clues to figure out what's going. Something is creating the fulfillment and setting that ID, then it seems like the flow is trying to create it again.

    Things to check:

    1. If you find the existing fulfillment, is it set to picked or packed instead of shipped? If so, you probably have a status on your sales order export "pending Fulfillment" which is missing the fact an IF already exists
    2. ShipBob is a whacky system with a whacky API. They create shipment records as soon as you send them an order. I'm sure they have some explanation, but it makes everything awkward when working with them. If your flow isn't smart enough it will pull in the Shipment from ShipBob before the order has actually been shipped. This could be creating an item fulfillment and (see #1)
    0

Please sign in to leave a comment.