People import fails when entries have a Domain Name / Link that doesn't have a corresponding entry in Companies

[zakgreant]

Bug Description

When importing People entries, the entire import fails if there is an entry that contains a Company / Domain Name / Link that doesn't exist.

Expected behavior

Any of the following would be preferable:

• a warning during the import - or -
• the import succeeds and Company entries are created for Domain Name / Links that don't exist - or -
• the import succeeds but I must manually set the relationship between the Person and the Company entries - or -
• the import succeeds, but entries that have Domain Name / Links that don't exist aren't imported

[Lakshayyy-m]

Will wait for the member of the team to decide the intended behavior.

[BOHEUS]

@zakgreant

• are you self-hosted or cloud?
• if self-hosted: which version are you using and do you have by any chance relevant logs/errors from Docker containers or Console tab in devtools?

CC: @etiennejouan

[etiennejouan]

Hi @zakgreant, we’re aware of this. For now, a workaround is to import all your domains into companies (if a domain already exists, it should not create a new company), then import your people.
This isn’t prioritised yet, but we plan to enhance the API with "connectOrCreate" capabilities. You would then be able to choose the expected behaviour at import time: connect or fail (as today) or connect or create.

[Lakshayyy-m]

Hey @etiennejouan , do you want me to work on it or is it supposed to be done internally?

[etiennejouan]

Hi @Lakshayyy-m, thanks for your support but we're not sure yet about the implementation. connectOrCreate would take place in ORM which is a critical layer.