Settings and activity
1 result found
-
190 votes
Hi everyone, we want to thank you all for your meaningful feedback and detail of the uses you each have for enabling duplicate names for contacts.
Right now, the contact name field is the key identifier that interacts with many other Xero features, and as such, changing how this field functions is not a small feat.
As noted by others in the comments, some users have found adding unique characters or using the account number in the contact name useful.
At this time we don’t have plans for developing the ability to have duplicate names of a contact in Xero. However, the work happening around core features might open the door for improvements like this down the line.
For now, we'll keep a close watch on the support this idea continues to build, and we’ll make sure to share updates if anything changes.
An error occurred while saving the comment An error occurred while saving the comment 
Roger Watts
commented
@Adam Bent
Nice workaround!
I expect Xero gives some sort of guarantee to all those involved in the after-market that the database schema won't be changed for x years...
Looking at the downstream implications of changing the primary key [Contact Name] it is hard to see how it could ever be rolled out without ensuing chaos.An error occurred while saving the comment Roger Watts
commented
This sounds like Xero has guaranteed the schema for a period of time to all the developers who are adding their $$$ to the big picture; I'm not sure that they wouldn't be having their own problems dealing with the issue.
The one thing that amazes me is that Xero doesn't keep any track of what the community is saying unless the message comes through CA onsellers (who aren't actually having to deal with user issues such as this).An error occurred while saving the comment Roger Watts
commented
Concatenated primary key of fname, lname, email perhaps?
I'll bet the John Smiths of the world feel picked on by XeroRoger Watts
supported this idea
·
In straight database terms the primary key being a concatenated fname & lname is probably unfixable. The problems it creates aren't in public view and who cares what the CFO and sysadmins think?
I guess Xero guarantees some sort of continuity to its add-on development partners and the total of all these people, along with Xero's *********** of the market, lead to them having to redesign their product as will all their service partners using APIs.
It is generally a waste of time complaining in this forum which is probably used by xero to deflect complaints which will continue, in their minds, ad nauseam.
Perhaps it is better to complain to the next level up in the chain/pyramid that has an interest in your issues with xero's product and let them do the same.