Skip to content

Settings and activity

1 result found

  1. 127 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hey community, thank you for your continued interest in this idea.

    Wanted to provide an update here as it's been a while since we last spoke to duplicate contacts.

    I do understand that, at face value, this seems like a quick fix. However, as the contacts screen interacts with many other parts of Xero, this work can not commence until the modernisation of other, related systems is complete. 

    Due to this, we do not expect support for duplicate contacts to be delivered in the coming short-term.

    In the meantime however, we're keen to continue collecting feedback and votes on this idea, and I will update you here as soon as there's more work to share.

    An error occurred while saving the comment
    Roger Watts commented  · 

    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.

    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 Xero

    Roger Watts supported this idea  ·