Details
-
Type:
Improvement
-
Status: Done/Fixed
-
Priority:
Major
-
Resolution: Fixed/Completed
-
Affects Version/s: None
-
Fix Version/s: 1.0
-
Component/s: None
-
Labels:None
Description
The framework for managing unique key consists of
1 - modifying the schema generator to enable parsing unique keys in xml and
adding them to Contacts.sql file.
2 - adding support for error reporting of unique key violations.
The following entities need unique keys.
crm_country - name+iso_code
(country_code, idd_prefix, ndd_prefix are all international/national dialing related and may not be unique - so let's leave these out)
crm_state_province - name+country_id
crm_county - name+state_province_id
crm_domain - name
crm_mobile_provider - name.
crm_im_provider - name.
crm_location_type - domain_id+name
crm_relationship_type - domain_id+name_a_b, domain_id+name_b_a (name_a_b can match name_b_a w/in same record)
crm_group - domain_id+title, domain_id+name (name is derived from title by system)
crm_category - domain_id+name
crm_custom_group - domain_id+title, domain_id+name (name is derived from title by system)
crm_custom_field - custom_group_id+label, custom_group_id+name (derived from label)
crm_saved_search - domain_id+name