Error with Saved User Signature After Upgrade to Version 11

asked on May 9, 2022

I have a user who is receiving an error when using their saved signature in Forms after the upgrade to Version 11 Update 2.

They can click a signature field, and it'll automatically add their signature as it always has, and it looks good.

But then they get a validation error on the field stating "The supplied value is not a valid signature".

It doesn't appear to happen if they use the options to draw or type their signature, just using the saved signature from their profile.

It's happening in both Chrome and Edge, and isn't happening to any other users that I'm aware of (including not happening to myself in either our test or production environments).

I'm uncertain what could be "invalid" about her saved signature file.

Has anyone encountered this issue before?

0 0

SELECTED ANSWER

replied on May 9, 2022

Hi Matthew,

Forms now validates value of signature field on submit, which is expected to be a Base64 image.

According to your description, it seems to be related to saved signature data of the specific user. Does the issue persist if user edits and saves signature again in Account page?

0 0

replied on May 10, 2022

I don't really understand what the issue is, but I believe I have confirmed that editing the signature and saving again does solve it.

I didn't realize that you could just click edit on the signature, click Accept, and then Save without actually changing anything about it. But that worked.

I was curious about this and wanted to test under my control instead of the user's - so I copied the user's signature from their user profile in the production database into my own user profile in the test database, and confirmed that if I copied the base64 code out of the database and into a text editor that visually they appeared identical. Then I confirmed that in the test environment in Forms I now saw their signature on forms and received the validation error. Then I went into the profile, did the steps to edit and save it (without changing it in any way). Then I tested on the form again, and now the validation error did not occur even though the signature looked the same. I went back to the database, and copied the values back to the text editor and now they appeared different. I put the values into a base64 converter and they both worked, and both visually appeared the same. So it looks like something changed with the way the image was saved that although the image loads and appears correct, the validation doesn't like it - that's weird, but at least I have an easy and verified process for the user to get the system to accept their signature going forward.

Thank you.

0 0

Question

Question

Error with Saved User Signature After Upgrade to Version 11

Answer

Replies

Sign in to reply to this post.