Incident Protected Information Field Encryption Issue: Invalid attempt. Encrypted data could not be savedProblemThe customer wants to encrypt one field on the Incident table and populate it via a record producer. However, if an end user without the ITIL role attempts to submit the record producer with a value in that field, they receive an error message and are unable to submit the catalog item. Steps to reproduce Go to portalRequest the record producer <rec_prod>Populate the field (The one that was encrypted)Submit the requestGot error: Invalid attempt. Encrypted data could not be saved Root CauseThere is a role used as part of the encryption context and due to this, both scenarios (protect and create) cannot be on the same place. Users without that role cannot do anything under that table.record.Steps to Resolve1. Ensure the users that want to use the record producer to create incident have the role used on the encryption context2. Alternatively, the users that have the role can submit the incidents on behalf of the users which do not have the role. Note: The only problem with this is in case there sensitive information that cannot be shared.