Lookup - one to many not working properly
I have a Netsuite Lookup that looks for existing Customer Part Numbers based on the following additional criteria:
In the lookup One to Many is put to yes. With the path to many set to the line items in the JSON.
So I want to fetch all results on the combination of: "Customer Part Number" and "Customer". The results will be passed on to the next flow due to the following result mapping:
I tried the following scenarios with 3 line items:
Scenario 1:
Line item 1 has a customer part number that does not exist in Netsuite.
Line item 2 has a customer part number that already exists in Netsuite.
Line item 3 has a customer part number that already exists in Netsuite.
So lookup will be performed 3 times with the line items above. However both 3 times I will am getting an empty result:
"nsCustomerPartData": [],
"nsCustomerPartDataError": []
I actually excepted that line item 2 and 3 had results and only line item 1 was empty. This however is not the case.
Scenario 2:
Line item 1 has a customer part number that already exists in Netsuite.
Line item 2 has a customer part number that already exists in Netsuite.
Line item 3 has a customer part number that already exists in Netsuite.
Now I am getting results for every line item. For example line item 1 shows:
"nsCustomerPartData": [
{
"id": "xxx",
"recordType": "xxx",
"Name": "xxx",
"Item": "xxx",
"Customer": "xxx",
"Subsidiary": "xxx",
"customer ID": "xxx",
"Date Created": "15/09/2022 13:35"
}
],
So it seems the problem is that the lookup results will be empty for all line items when there is no result for the first line item. Is this a bug?
Comments
I have altered my question to make it more clear.
Hi Nuri Ensing,
We tried replicating the issue, but the issue is not reproducible for us and we are able to fetch the data as expected even if the first line item doesn't exist in the application,
We need to investigate this issue further to find the root cause, could you please create a support ticket for this issue with all the necessary details so that we can debug this issue?
Thanks,
Sukeerthi.
Hi Nuri Ensing!
I didn't see that you'd created a support ticket on this yet, so I created one on your behalf. Thank you so much for letting us know about the issue, and for being so active in the community letting us know how we can better improve your experience!
Thanks Courtney Jordan. I appreciate your help!
Please sign in to leave a comment.