Details
-
Type:
Bug
-
Status: Done/Fixed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 3.3.6
-
Fix Version/s: 4.4.0
-
Component/s: None
-
Labels:None
Description
We created a new organisation sub-type, called Electorate. We created a relationship between an Individual and Electorate of "Candidate for"
We imported a bunch of electorates as Electorate type contacts.
We imported a group of individuals with a column that has the Electorate that they are a Candidate for, and used the "Candidate for" matching to "Organisation Name (match to contact) *"
The attempted import of this relationship to an Organisation contact sub-typem, Electorate, did not find a match to existing Electorate "Organisation sub-types" (perhaps only searching in traditional Organisation names), but then ironically the Organisation contact created was given the Electorate sub-type, because the relationship of "Candidate for" can only be with an Electorate sub-type and not an Organisation. So it is good that the import creates the right sub-type, but bad that it doesn't search to match the Name of the contact in the right Organisation sub-type, so as to avoid creating additional duplicate contacts. This may be related to the bug previously reported that you can't import custom fields to contact sub-types, which I think is a major problem too as it renders sub-types pretty useless if you can't import, for example, the "Required Swing" to an Electorate only custom field.