An export from a table with field encryption would always yield a blank file Issue When an export is done on a table with field encryption, the resulting file would always be blank. This is true even if the logged-in user has the access to the encrypted data.ReleaseApplicable to all releasesCauseThe export is running as a background job as a System user. Anything running as a system user or a scheduled job that doesn't have a user session won't be able to access the key to encrypt or decrypt data and hence, we get a blank file.ResolutionThe data can be extracted from the table containing encrypted data by using web services (REST or SOAP). Another workaround would be to run a mass decryption job first, then run a data export report job, and then finally, run a mass encryption job.