Marking a field as Sensitive data doesn't save to the database.

[OwainWilliams]

We recently upgraded Umbraco 8.1.4 and Forms 8.2.0 to U8.6.1 and UF8.4.0

Preupgrade, we had a field on a form marked as Sensitive data and everything was fine. After the upgrade, if any data was added to the sensitive data field, it's not saved in the database.

Support ticket Id: #51768

Reproduction

Specifics

Umbraco 8.6.1
Forms 8.4.0

Steps to reproduce

Create a form and add a field, such as a short string. Complete the form and you will see that the data is stored in the backoffice. Now mark this same field as sensitive data. Complete the form again and then check the backoffice, you will see no data is visible, it doesn't matter if you are an admin with permission to see sensitive data or not. If you check the database table, you will see the data hasn't been saved at all. It's gone.

If you now change that field back to non-sensitive, fill out the form again, your data is now saved as expected.

Expected result

The data should be saved in to the database and visible in the backoffice.

Actual result

No data saved in the database table or visible in the backoffice.

---

This item has been added to our backlog AB#6694

I am also having this issue!

[nul800sebastiaan]

Yikes! We're looking into it.

[OwainWilliams]

Great, thanks @nul800sebastiaan - a bit of a GDPR issue if we can't mark things as sensitive. I sent a screen capture with my support ticket if you need help to reproduce. Didn't want to share it on github as it was a live site.

As above, I have a ticket I worked through with support (Derek) yesterday. (#51863) This also contains screenshots and examples.

[nul800sebastiaan]

Alright, just got a fix for this from my colleagues, which can be used until we can release 8.4.2 soon:

UmbracoForms.Files.8.4.2-alpha.20200515.7.zip

It's enough to update the dlls, that's where the fix is located. We do apologize for the inconvenience!

[rickbutterfield]

I know this issue is closed (so I'm happy to log this somewhere else) but thought it might be worth noting that the DLLs fix also resolves an issue where sensitive fields weren't available in a custom workflow Record.

[nul800sebastiaan]

I have an updated version available, as @aaron-sadler-activeis pointed out that the previous version would not allow him to update any fields from his own custom workflows.

So the rules now are as you would expect:

• If the user sets Include sensitive data to true in the workflow settings then that workflow will receive sensitive data field and they can be updated from your custom workflow code.
• If the user set Include sensitive data to false in the workflow settings then that workflow will not receive sensitive data fields and they can not be updated from that workflow. The values will be saved on the record as-is.

UmbracoForms.Files.8.4.2-alpha.20200525.16.zip

@aaron-sadler-activeis we'd love to hear back if this now fully works again as you expected!