"No such column" error on the Signature object

Last updated 27 Oct 2026

The short version

Simple Signature needs the user who signs to have Read and Edit access to every field on the ß Signature object. When the user cannot reach one of those fields, or the object a field links to, Salesforce reports the field as missing. The signature, its image or its PDF then fails. Give the user the missing access, and the signature saves.

What you see

A Flow with the signature form fails, or a deployment fails on a test class. The error, or the debug log, shows this text:

No such column 'signature__Lead__c' on entity 'signature__Signature__c'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names.

The field name in the quotes changes. Customers saw signature__Lead__c, signature__Email_With_External_Limits__c and signature__qr_code_type__c.

Sometimes the signature record saves, but no signature image and no PDF come.

Why it happens

The field exists, but the user has no access to it. This happens in two ways:

• The user has a permission set or profile that your org built. The Simple Signature permission sets give access to all the Simple Signature fields. Your own permission set does not get the new fields when you update the app. So the error often starts right after an update.
• The user is the guest user of a site. The guest user can see the field. But the field links to another object, such as Lead, and the guest user cannot read that object.

Check 1 fixes the first case. Check 2 is only for signatures on a site.

Check 1: the user's access to the Signature fields

The quick fix is a Simple Signature permission set.

1. Open Setup. In the Quick Find box, type Users. Click Users. Click the user who got the error. The user's page opens.
2. Scroll to Permission Set Assignments. Click Edit Assignments. Add Simple Signature (User). A user who sets up Simple Signature gets Simple Signature (Admin) instead. Click Save.
3. Have the user take the signature again.

If your company rules do not let you use that permission set, give the same access in your own permission set:

1. Open Setup. In the Quick Find box, type Permission Sets. Click Permission Sets. Click your permission set.
2. Click Object Settings. Click ß Signatures. Click Edit. Tick Read, Create and Edit for the object. Under field permissions, tick Read and Edit for every field, your own fields too. Click Save.
3. Click Object Settings again. Click ß Steps. Click Edit. Tick Read, Create and Edit for the object. Tick Read and Edit for the field with the API name signature__FieldSet__c. Click Save.
4. Have the user take the signature again.

Check your permission set again after each Simple Signature update. New versions can add fields.

Check 2: a site guest user

Do this check when the signature happens on a site, and the field in the error links to another object. For example, signature__Lead__c links to Lead, and signature__Contact__c links to Contact.

1. Open the guest user's profile. For a Salesforce Site, open the site in Setup and click Public Access Settings. For an Experience Cloud site, open the site in Experience Builder, click Settings, then General, and click the guest user profile link.
2. Give the profile Read access to the object the field links to, for example Lead. Click Save.
3. Take the signature again on the site.

The Simple Signature (Guest) permission set gives no access to Lead, Contact or Opportunity. You give that access yourself. If the form shows fields of that object, also add a sharing rule for it.

How to check it worked

1. Take a test signature the same way the user did. For a guest user, sign on the site. It saves with no error.
2. Open the new ß Signature record. The signature image is there. If your setup makes a PDF, the PDF is there too.

If it still does not work

Open a case. Include your Simple Signature version, the full error text, and whether the user has a Simple Signature permission set or one your org built.

Was this helpful?

Yes No

Related

• All Simple Signature troubleshooting
• Install the newest version of Simple Signature. TAF works on bugs in the newest version only.