using the Lookup field mapping type in my Import flow

Comments

8 comments

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

    Try changing your operator to "equal to"

    0
  • Colton Berry

    I am also encountering this issue in my production instance. Interestingly, I did not experience this issue in my sandbox instance (also connected to the Netsuite sandbox).

     

    Message: Both lookupKey and lookupFilterExpression are missing for mapping {"celigo_classname":"Celigo.integrator.mapping.model.FieldMapping","jsField":"entity","externalField":"$.customer","lookupAllowFailures":false,"lookupType":"record","lookupSource":"customer","lookupValue":"internalid","internalId":true,"externalDatatype":"string"}

     

    I also attempted to change the operator to "equal to", which did not fix the issue for me.

    0
  • Nnamdi Amobi

    Did you ever figure out what was causing this? I'm having the same issue and it seems to have started out of nowhere.

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

    I'm running into this same error:

    Message: Both lookupKey and lookupFilterExpression are missing for mapping {"celigo_classname":"Celigo.integrator.mapping.model.FieldMapping","jsField":"celigo_nlobjTransformId","externalField":"$.orderID","lookupAllowFailures":false,"lookupType":"record","lookupSource":"salesorder","lookupValue":"internalid","internalId":true}

    Here's the lookup details:

    I've created the lookup 3 times and carefully configured everything, but each time I get this error in the preview.

    Anyone from Celigo have any insight or ideas?

    0
  • Balasubramanian Mahadevan Community manager Senior Technical Writer
    Engaged
    Celigo University Level 2: Seasoned

    Steve Klett Nnamdi Amobi Colton Berry. Our support team was able to resolve the query raised by Helen Sarpong. Here is a gist of the resolution provided by our support team:

    • You are getting an error message in your lookup mapping {"celigo_classname":"Celigo.integrator.mapping.model.FieldMapping","jsField":"entity","externalField":"$.VendorID","lookupAllowFailures":false,"lookupType":"record","lookupSource":"vendor","lookupValue":"entityid","internalId":true,"externalDatatype":"string"}
    • What we did is to configure the lookup again (since it wasn't configured upon joining the meeting) then enabled the flow and run the flow.
    • The record seems to be getting imported successfully but in the mappings upon hitting the preview, you are still getting the same error message.
    • Since the flow is enabled now, we remove the mapping where the lookup is configured and then re-add it back, just like a charm, the error disappeared and the flow is working as intended now.

    Please let us know if this helps in resolving your issue.

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

    Balasubramanian Mahadevan I appreciate the reply, thank you.

    Your described process didn't work for my case. This is a very annoying bug, it effectively makes the mapping preview unavailable. Is there a bug logged for this issue?

    0
  • Anitha Abraham Community moderator Principal Technical Writer
    Celigo University Level 3: Master

    Steve Klett, thanks for your patience. The QA team was not able to reproduce the issue. So, I've created a Support ticket for further investigation. 

    0
  • Balasubramanian Mahadevan Community manager Senior Technical Writer
    Engaged
    Celigo University Level 2: Seasoned

    Hi Steve Klett. Hope your issue has been resolved. If you are still facing this issue, please provide your credentials in the support ticket that was opened with the support team with incident #187271 and they will be able to look into this further.

    0

Please sign in to leave a comment.