i have updated my Reports' XLS and XLSx Export Options to have Text Export Mode = text so when i export the report to Excel the fields that come in encrypted will have been deencrypted and can thus be read in Excel.
this used to work until we upgraded to the latest web viewer with the nicer looking menu system.
do i need to do anything further to make it work now?
Hi,
Are you referring to the XtraReport class?
Hello Benjamin,
It isn't clear what you mean by "come in encrypted/decrypted".
Let me clarify the situation: when the TextExportMode property is set to Text, the data fields are exported as strings with the corresponding formatting applied. Would you please clarify the actual issue? I suppose that the corresponding fields are exported without formatting embedded when the brand new MVCxWebDocumentViewer is used. Would you please confirm my assumption?
In addition, the sample project demonstrating the issue would be greatly appreciated.
Thanks,
Dmitry
we have some fields in our database that are encrypted at rest. So, in order to view the values of those fields in a report we need to decrypt them. in the Before Print event we do this call our own decrypter.
private void Description_BeforePrint(object sender, System.Drawing.Printing.PrintEventArgs e)
{
if(Description.Text.Contains("µ"))
Description.Text = Utility.CryptoService(Description.Text, false);
}
This will show the decrypted data on the report and when send to any medium (DOC, Printer, PDF, etc) except XLS and XLSx.
Also, see picture attachment, setting Text as the Text Export Mode value under XLS Export Options under Export Options under the Report Properties has allowed this to work in the past. now it doesn't work.
Please help.
Hi Benjamin,
Thank you for the detailed description. I managed to reproduce the same behavior on my side and forwarded this thread to our R&D team for further research. Please bear with us. We'll reply here once we have any progress in this regard.
Any update on this?
Hello Benjamin,
I'm afraid that I have nothing to inform you with at the time being: this issue is being currently researched by our developers and it seems that there is no time frame as to when it will be completely fixed. Please keep an eye on this thread for further updates.
Thanks,
Dmitry