Allow Us To Create/Edit The Custom Field Unique Keys
Log In
Activity Feed
Sort by
P
Pallavi Kothari
Merged in a post:
Ability to choose the "unique identifier" fields
J
Jeremiah Vanderlaan
It would be nice if we could select which field was the "unique identifier" for contacts.
I don't want to enable duplicate contact, because then I will get a new contact every time that contact submits a form.
But, if I could select which fields are to be considered "unique" ... that would be nice. It would be great if we could use a custom field for this too. Then we could import IDs from other systems and use that.
P
Pallavi Kothari
Merged in a post:
Allow custom fields to be unique identifier for contacts.
G
Gohar Nadeem
Under "Contact Deduplication Preferences" allow custom fields to be selected as unique identifier "Find existing contacts based on"
A
Adam Campbell
It would be great to have the ability to update the unique key for the custom field to streamline custom values. Since this feature is hidden upon creation, many users don't pay attention to it, resulting in long, non-uniform unique keys. When it comes to adding these custom values to emails, funnels, etc. it makes it difficult to format. Since they can't be edited, it results in having to delete and recreate custom fields with the unique key in mind.
In a perfect world, there would even be a section in the settings that created redirects for old custom values to point to the new custom value.
F
FusionPro Staff
Yes we have this issue as well with forms making new contacts when "duplicate contacts" is enabled. Any new form that is submitted just creates a new contact, but can there be a way to give each form an option to either honor the duplicate contact option or ignore it. That way certain forms can continue to gather data for contacts that are already in the CRM. This is crucial for us. Thanks out there to the dev team. You guys really do a wonderful job!
J
John Demitri
I like the idea but you can get this done by deleting the custom field and creating a new one with the name being what you want as a key and then edit the name after creating it. If you are coming back later and want to change the key after you have data in the field you can create the new key and then run a workflow to update the new key with the old key and then delete the old key.
M
Mark Joseph
John Demitri: how do you run a workflow to update the new key with the old one?