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.
- Open Setup. Click Object Manager. Click ß Signature. Click Fields & Relationships.
- 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.
- Click the Field Label of your field. Click Edit.
- Add (custom) to the end of Field Label. Add _Custom to the end of Field Name, for example Initials_Custom. Click Save.
- 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?
Thank you. Your answer helps us know which articles work.
Related
- All Simple Signature troubleshooting
- Install the newest version of Simple Signature. TAF works on bugs in the newest version only.
Still stuck?
Open a case, and paste the exact error text into it. Our support team answers by email.