Hi Keith
Have a think about it. It's all the data in one line and processing each field sequentially with no reference to any other field. The best the import can do is try to match by looking at multiple fields to match the value it has - that is one for one.
There is no way on the import to tell the import to also look at State when evaluating County so it picks the record where State and County match.
I'm presuming you are using dependant picklists to filter the the County table by the State (already entered) on the form data entry. (thats a UI tickbox on the classic interface - hasn't made it to the new make.powerapps.com that I can find yet).
There really is no solution apart from genuine code for the import (which is fairy simple exercise) or perhaps Flow (automate) but I don't know about that - would be tricky but i guess a Flow expert could do it.
Pete
------------------------------
Peter Hale
Naish Pty Ltd
------------------------------
Original Message:
Sent: Nov 03, 2021 01:17 PM
From: keith courtemanche
Subject: Large Import of Line Item Details is not working
Hi all,
We sometimes receive very large orders consisting of hundreds of line items. To expedite the data entry we successfully created an Excel order header and an Excel line item import template/sheet that usually works on about 2/3 of the line items being imported. The items that are not importing are failing because of a custom field labelled 'county' This field contains all US counties and the message CRM is giving us is "A duplicate record was found' This makes sense because, for example, Orange County exists in more than one location in the US. What is odd to me though is the the state is a required field and there isn't more than one Orange County in the state that was chosen. i.e. the user entered California and entered Orange County but still got the error. Note: If a user enters this information via the GUI the only counties that appear for CA are CA counties so the system is filtering based on the state. So long story short it seems the data import process is not aware of the state and it looking in the entire counties table.
Is there a way to solve for this and what am I missing in terms of how the import process works?
Thanks
------------------------------
keith courtemanche
FCS
------------------------------