Using the Lookup field mapping type in my Import flow

Integrator.io
, , ,
1

I'm trying to import Vendor Bill data. I have the Vendor ID from the source file, but not the Vendor's internalid. I can only choose either the Vendor Name or Vendor InternalID from the import field selections. Therefore, I am trying to lookup the vendor's InternalID by using the vendor ID which I have from the source file. It does not look like I used the Lookup field mapping type feature correctly because I am getting an error.

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

5301043caa20740200000001-fb12f9db41f947cdb46c804bb847172c.png
5301043caa20740200000001-fb12f9db41f947cdb46c804bb847172c.png663×126 3.6 KB

5301043caa20740200000001-394336b098a94c4a9d3bfedfed1ec434.png
5301043caa20740200000001-394336b098a94c4a9d3bfedfed1ec434.png777×782 19.9 KB

2

Try changing your operator to "equal to"

3

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.

4

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

5

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:

5301043caa20740200000001-759f98148d1046a4b288267dd7ffce30.png
5301043caa20740200000001-759f98148d1046a4b288267dd7ffce30.png745×1003 29.6 KB

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?

6

@steveklett @nnamdiamobi @coltonberry. Our support team was able to resolve the query raised by @helensarpong. 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.

7

@balasubramanianmahad 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?

8

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

9

Hi @steveklett. 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.