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

Go from record to record without a trip back to the list

Get started

Install a TAF package, set it up, and give it to your users.

Implementation guides

Guides for all four apps are ready.

How-to articles

One article for each task

Book a demo

See a package in a live org

Compatibility

Editions and releases we support

Get help

Open a case. Our support team answers by email.

Open a support case

Our support team answers by email

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

We write these pages for Salesforce admins.

Implementation guides

Guides for all four apps are ready.

How-to articles

One article for each task

Change log

What changed in each release

Compatibility

Editions and seasonal releases

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

Signatures stop working after an update: your field has the same name as a new Simple Signature field

This article tells you what to check, and how to fix the problem.

Last updated 27 Oct 2026

The short version

A Simple Signature update added a field with the same name as one of your own fields on the ß Signature object. The two fields clash, so signatures stop working, and the debug log shows a duplicate field name. Rename your own field.

What to do

If a PDF template uses your field in a merge code, open a case before you rename it. TAF support tells you what to change in the template.

  1. Open Setup. Click Object Manager. Click ß Signature. Click Fields & Relationships.
  2. In the Field Name column, look for two fields with the same name. One field has signature__ in front, and one does not. For example, signature__Initials__c belongs to Simple Signature, and Initials__c is yours. If no two fields match, open a case.
  3. Click the Field Label of your field. Click Edit.
  4. Add (custom) to the end of Field Label. Add _Custom to the end of Field Name, for example Initials_Custom. Click Save.
  5. Take a test signature, or send a test request, the way your users do. The signature saves, or the signer gets the request email.

If it still does not work

Open a case. Include your Simple Signature version and the old and new names of your field.

Applies to

Simple Signature (all versions). This fix comes from solved support cases.

Was this helpful?

Related

Support

Still stuck?

Open a case, and paste the exact error text into it. Our support team answers by email.