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. Our support team answers by email.

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
Simple Signature · Troubleshooting

Signatures stop working after the update to 5.8: a duplicate Initials field

What to check, and how to fix it.

Last updated 27 Oct 2026

The short version

Simple Signature 5.8 adds its own Initials field to the ß Signature object. If your org has its own field with the API name Initials__c, the two fields clash. Rename your own field, and signatures work again.

What you see

After you update to 5.8, signatures stop working. Simple Signature keeps trying to connect, or signature requests are made but never go out. The logs show an error about a duplicate field name.

Why it happens

For the initials feature of version 5.7.52, TAF's steps told admins to make a rich text field on ß Signature with the API name Initials__c. Version 5.8 brings its own Initials field, so admins no longer make one. An org that has its own Initials__c field now has two fields with the same name.

Check this first

Open Setup. Click Object Manager. Click ß Signature. Click Fields & Relationships. In the Field Name column, look for Initials__c with no signature__ in front. That field is yours. The Simple Signature field shows as signature__Initials__c. If you find no such field, this article does not fit your problem. Open a case.

If your PDF template shows the initials with a merge code, open a case before you rename. TAF support tells you what to change in the template.

What to do

  1. In Fields & Relationships on ß Signature, find the row whose Field Name is Initials__c. Click the link in the Field Label column of that row. The field's page opens.
  2. Click Edit. The edit page opens.
  3. In Field Label, replace the text with Initials (custom). Now you can tell your field from the Simple Signature one.
  4. In Field Name, replace the text with Initials_Custom. Click Save. The field's page opens again and shows the API name Initials_Custom__c.
  5. Take a test signature, or send a test signature request, the same way your users do.

How to check it worked

  1. For a signature on a record: the signature saves, and a new ß Signature record shows it.
  2. For a signature request: the signer gets the request email.

If it still does not work

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

Applies to

Simple Signature 5.8.x. This fix comes from solved support cases.

Was this helpful?

Related

Support

Still stuck?

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