# Using the Lookup field mapping type in my Import flow **URL:** \ **Category:** Integrator.io\ **Tags:** error-handling, import, lookup, netsuite\ **Created:** [September 8, 2022, 5:23am UTC](https://connective.celigo.com/t/using-the-lookup-field-mapping-type-in-my-import-flow/658 "2022-09-08T05:23:44Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![helensarpong](https://avatars.discourse-cdn.com/v4/letter/h/c77e96/32.png) [@helensarpong](https://connective.celigo.com/u/helensarpong)\ **Post date:** [September 8, 2022, 5:23am UTC](https://connective.celigo.com/t/using-the-lookup-field-mapping-type-in-my-import-flow/658/1 "2022-09-08T05:23:44Z")
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](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/d/d246129894891c508ea8b8fc8492e9322fbf0822.png) ![5301043caa20740200000001-394336b098a94c4a9d3bfedfed1ec434.png](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/b/bffe47b27d20091421ac9345afcee5e9d1d01232.png) ---
**Author:** ![steveklett](https://avatars.discourse-cdn.com/v4/letter/s/e495f1/32.png) [@steveklett](https://connective.celigo.com/u/steveklett)\ **Post date:** [September 8, 2022, 10:02pm UTC](https://connective.celigo.com/t/using-the-lookup-field-mapping-type-in-my-import-flow/658/2 "2022-09-08T22:02:38Z")
Try changing your operator to "equal to" ---
**Author:** ![coltonberry](https://avatars.discourse-cdn.com/v4/letter/c/7c8e57/32.png) [@coltonberry](https://connective.celigo.com/u/coltonberry)\ **Post date:** [March 6, 2023, 10:40pm UTC](https://connective.celigo.com/t/using-the-lookup-field-mapping-type-in-my-import-flow/658/3 "2023-03-06T22:40:25Z")
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. ---
**Author:** ![nnamdiamobi](https://avatars.discourse-cdn.com/v4/letter/n/76d3ee/32.png) [@nnamdiamobi](https://connective.celigo.com/u/nnamdiamobi)\ **Post date:** [April 1, 2023, 12:40am UTC](https://connective.celigo.com/t/using-the-lookup-field-mapping-type-in-my-import-flow/658/4 "2023-04-01T00:40:35Z")
Did you ever figure out what was causing this? I'm having the same issue and it seems to have started out of nowhere. ---
**Author:** ![steveklett](https://avatars.discourse-cdn.com/v4/letter/s/e495f1/32.png) [@steveklett](https://connective.celigo.com/u/steveklett)\ **Post date:** [June 8, 2023, 5:16am UTC](https://connective.celigo.com/t/using-the-lookup-field-mapping-type-in-my-import-flow/658/5 "2023-06-08T05:16:31Z")
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](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/5/511d1cc7d56383a5fecdea766fd7457fe70f36ac.png) 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? ---
**Author:** ![balasubramanianmahad](https://avatars.discourse-cdn.com/v4/letter/b/76d3ee/32.png) [@balasubramanianmahad](https://connective.celigo.com/u/balasubramanianmahad)\ **Post date:** [June 8, 2023, 9:25am UTC](https://connective.celigo.com/t/using-the-lookup-field-mapping-type-in-my-import-flow/658/6 "2023-06-08T09:25:24Z")
@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. ---
**Author:** ![steveklett](https://avatars.discourse-cdn.com/v4/letter/s/e495f1/32.png) [@steveklett](https://connective.celigo.com/u/steveklett)\ **Post date:** [June 9, 2023, 3:59pm UTC](https://connective.celigo.com/t/using-the-lookup-field-mapping-type-in-my-import-flow/658/7 "2023-06-09T15:59:22Z")
@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? ---
**Author:** ![anithaabraham](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/anithaabraham/32/6964_2.png) [@anithaabraham](https://connective.celigo.com/u/anithaabraham)\ **Post date:** [June 13, 2023, 11:09am UTC](https://connective.celigo.com/t/using-the-lookup-field-mapping-type-in-my-import-flow/658/8 "2023-06-13T11:09:24Z")
@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. ---
**Author:** ![balasubramanianmahad](https://avatars.discourse-cdn.com/v4/letter/b/76d3ee/32.png) [@balasubramanianmahad](https://connective.celigo.com/u/balasubramanianmahad)\ **Post date:** [June 23, 2023, 10:09am UTC](https://connective.celigo.com/t/using-the-lookup-field-mapping-type-in-my-import-flow/658/9 "2023-06-23T10:09:10Z")
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.