- Issue created by @jdleonard
- πΊπΈUnited States bluegeek9
I think this is a duplicate of π External Identifier field Active
- πΊπΈUnited States jdleonard Austin, TX, USA
I missed that issue, but looking at it, it's not clear that it's the same as this. It mentions "Create external crm entity" but is lacking detail. I based this issue off of what's in the 1.0.x branch. Feel free to close one issue if you think it makes sense.
- πΊπΈUnited States jdleonard Austin, TX, USA
The current External Identifiers field has a "Source" and an "External ID" for each value.
CiviCRM has a single "Contact Source" and a single "External ID". The tooltip for Contact Source is "Use this field to store a description of how/why this contact was added to the database. This field is usually auto-filled when a contact is created from a public form i.e. Event Registration."
That seems to be a different intent than the "Source" defined in CRM's External Identifiers field so I'm double checking what your intent was and whether we should adjust.
Separately, while I see some value in accommodating external IDs for multiple systems, I wonder whether that would better be accommodated using dedicated fields for each system, which could be provided by relevant integration modules. Should we ditch the External Identifiers field in favor of a simple single value External ID field like Civi has?
- πΊπΈUnited States bluegeek9
There is another issue that deal with the external entity field. π External Identifier field Active
There is half completed mork in that issue that I need to bring up to the current dev branch.
In this issue we will remove it as a default field. It will be spun off as it own module in the other issue.
- Merge request !45Issue #3525360 by bluegeek9: Make External Identifiers field optional β (Merged) created by bluegeek9
-
bluegeek9 β
committed 2311ab2e on 1.0.x
Issue #3525360: Make External Identifiers field optional
-
bluegeek9 β
committed 2311ab2e on 1.0.x
Automatically closed - issue fixed for 2 weeks with no activity.