Hi All,
I have 3 entity: entity A,B,C
A and B has 1:N relation
A and C has 1:N relation
Here is scenario, i need to import data into C, How can i authenticate the match of A with C to import.
As A has look up on C, WHEREAS B has look up on A, So TO IMPORT we need to have B LOOKUP VALUE with C.
Compexity is B has category "DISPLAY" which can be linked to A entity with many record., like a,b,c
so now Display has three record each have A entity lookup a,b,c ---- so it becomes DISPLAY with lookup a, Display with lookup b,
Display with look up c.
BUT IN subcategory which we want to import, how will we authenticate the which display should be imported as in SUB CATEGORY
lookup will see only LOOKUP with Display as its will see only primary filed of category. it will not see Dispaly a,Display b etc.
HOW CAN WE AUTHENTICATE THAT THIS Display is with a or Display with b etc because we will only see Display in look up.
Give some idea how to import such scenario , if possible else some other feasible solution.
*This post is locked for comments
You need to create a unique field. I had similar requirement and I created a new field and populate the field with the concatenated value of the 2 fields to make it unique. So in my case, I had the entity called Source which had the field called Category. record for this entity has multiple duplicate value but the values were unique for the category. E.g.
Source1 Cat1 [Unique Name: Source1Cat1]
Source1 Cat2 [Unique Name: Source1Cat1]
Source2 Cat2 [Unique Name: Source2Cat2]
Now when I imported by other entity which had the lookup to source, instead of mapping the name fields, I mapped it to the unique field. Thus CRM did a search on this field and was able to find the correcr record thus avoiding duplicate look up reference found error.
Hope this helps.
Right ravi, You understood it correctly i get multiple record with name Only Display in C entity look up.
So you mean without third field unique we can not map?
So what you suggest, we dont have unique, so what should be done?
Hi,
You need to have an additional field which uniquely identified the record . For example, if your entity Entity B has multiple records with the same category, you need to have a separate column which uniquily identiy that record like DisplayA, DisplayB etc. On your excel sheet with Entity C records, instead of using Display use the actual value DisplayA, DisplayB etc.
Now on Entity C during import, you need to map the value from this new column. This way, on import, CRM will search for Entity B with the value in your new field.
Hope this helps.
Hi Shahzeb Khan,
You will be able to import the data into entity C with a SQL Server Integration Services (SSIS) package.
Could you please provide sample data on A, B and C?
I havent fully understood that question but here is what I think you might be looking for.
For a lookup field to resolve during out of the box data import, we should have the lookup entity data imported first before we import the record that uses that value otherwise the import will fail because it wont be able to resolve the value.
If you need to import data to C and if C has lookup to A, you will need to have the A data fully imported first.
But from your question, the following part seems to suggest that B has Lookupt to A and C has lookup to A.
if you provide sample data and i will be able to suggest a solution.
If we have circular dependency, we may have to think about re-desining the solution.
Hope it helps
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,240 Super User 2024 Season 2
Martin Dráb 230,149 Most Valuable Professional
nmaenpaa 101,156