I would import to employee in to a new field temp_team for example. Add a business rule to the object to search an link on update. Search and link the team you wish the employee to me part of. When the import runs it will put the team next to the employee (using a primary key like loginid) then search the team and add the employee to it, if the employee has many teams every time it updates the temp_team it will do the search and link function. Once they have all imported turn off the business rule.
Thank you so much for your response.
I understand your approach and seems a good way to achieve this
I have added a new field temp_team under Employee object
Just I have a doubt on the business rule that I have created under the Employee object
Which relation should I select (last step) ? and Can you tell me how to configure the Search and like action ?
A last question : Could you tell me in which tables data is stored ? (Relation between Employee and associated teams)
You should be using this relationship: ProfileEmployeeAssociatedByStandardUserTeam a part from that the rest of your search an link looks ok.
Thank you for your response
I have a problem when importing the csv file.
In my file I have 2 Columns analyst Mail address and their associated teams
When I launch import it fails and in logs it says that required fields under Employee should be specified: Last Name, LoginId, UO, Name
Is it a normal behavior? For me The Primary Email should be enough to identify the employee
Have you an idea please?
In my previous image I may have given you the wrong relationship (its right in my second post) this is one from my test system:
This rule is on the Employee object, ensure it is set for update or new or both depending on your usage.
CSV import file
Here are excerpts from the import routine:
Did you manage to get this working?