-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Import related entities (api-chain) #17
Comments
tx!. I'll take a look. I'll give a try if I can sort it out the api chain import in one csv file :) |
It would be interesting to see if @colemanw has any idea about how we could make the metadata allow you to start from contact & find other entities (in api v4 I guess but we could update this easily to apiv4) - currently you can discover contact from email but not vice versa |
@eileenmcnaughton you right, my first impression is that the only way to "link" related entities from the parent Entity, is hardcoding who are the children per Entity. I don't see a way to discover them using api3, for instance in Contact there's no way using api3 to discover that Email, Phone, Address, etc.. could be created using 1-level api-chain. So do you think at this point makes more sense to start thinking on a migration to api4 than keep on adding exceptions or complex code to get this work on api3 ? |
@eileenmcnaughton Just asking before diving into the source code.
Is there a way a related entity to the main one could be imported in the same process? Like
Contact.Email
, within a Contact csv file, for example?My guess is not , because the mapping doesn't show related entities to be selected.
So if it's not the case, do you think it is possible / worth it to add the feature to import related entities using api-chain? I could try to implement that if it's feasible.
The text was updated successfully, but these errors were encountered: