Skip to content
Book a Demo Open a Case

Salesforce apps by To A Finish

Four managed packages that run inside your own Salesforce org.

Simple Signature

Document creation and e-signatures in Salesforce

Address Verification

Clean, verify and geocode Salesforce addresses

Highlighter

Colors, renames or hides Salesforce fields

List Browse

Browse Salesforce records without list clicking

Get started

Install, configure and roll out a TAF package.

Implementation guides

Guides for all four apps are ready.

How-to articles

One article per task

Book a demo

See a package in a live org

Compatibility

Editions and releases we support

Get help

Open a case and a person reads it.

Open a support case

The fastest route to an answer

Give us access

Let us sign in and see the problem

Support home

Guides, release notes and the case form

Troubleshooting

Search by the error text you see

Documentation

Written for admins, not for developers.

Implementation guides

Guides for all four apps are ready.

How-to articles

One task per article

Change log

What changed in each release

Compatibility

Editions and seasonal releases

Simple Signature Address Verification Highlighter List Browse Support Book a Demo
Address Verification · Troubleshooting

Record failed to update. Possibly due to a Duplicate or Validation Rule.

You see this error text in Salesforce.

Last updated 11 Oct 2026

What to do

The message reads, for example: Account Billing Record failed to update. Possibly due to a Duplicate or Validation Rule.

If a bad address gets the result Bad or Blank Address, but a good address shows this message, the check worked and the save failed. In TAF's support cases, a wrong field in the mapping of the address caused it, not a duplicate rule or a validation rule.

To work around it, edit the address entry on the Data Mapping tab. Clear the optional fields you mapped, for example Geocode Precision. Click Save. Change the test address and verify it again. Then map the optional fields again, one at a time, and verify after each one. The last field you mapped before the error is the wrong one.

Applies to

Address Verification 7.3.x. This fix comes from the tested Address Verification implementation guide.

Was this helpful?

Related

Support

Still stuck?

Open a case and paste the exact error text. A person reads every case.