• Kitty Kachhawa 6
  • NEWBIE
  • 0 Points
  • Member since 2016

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 0
    Questions
  • 1
    Replies
Dear community

We are looking for a solution to prevent standard Lead-Account-mapping during conversion. As is, when converting and merging a Lead into an existing Account, an empty Account billing address would be set by the Lead address. While this behaviour is not so bad for completely new Accounts, in a merge it is devestating for us.

It often happens, that active clients still apply on our website, e.g. for an additional product or so. Those clients already have an Account. Usually, we only use the shipping address and only fill in the billing address if it happens to be different. That means, in most cases the billing address is empty. When a Lead is now converted and merged to such an Account and the Lead address differs from the Account's shipping address, we might not realise it until we already sent out the invoice to the wrong place. That is why we need to prevent that standard mapping.

I have looked into solutions with Apex but I am still clueless. According to this entry on stackexchange, at least the custom field mapping is executed already before the before triggers. I guess that standard field mappings also apply then. That leaves me literally no option to prevent the change. Because in the before trigger I would not even see that the billing address is being updated.

Does anybody have an input for this?