msspurlock / reportsync

Automatically exported from code.google.com/p/reportsync
1 stars 0 forks source link

Non-ASCII chars in the .rdl file cause upload error: The definition of this report is not valid or supported by this version of Reporting Services. #48

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Just create a report where a cell/expression uses a Non-ASCII char (Example: 
euro € symbol) 
2. Try an SSRS expression like that: 
=IIF(TRIM(Fields!CurrencyCode.Value)="USD","'$'#,0.00;('$'#,0.00)",
IIF(TRIM(Fields!CurrencyCode.Value)="EUR","'€'#,0.00;('€'#,0.00)",
IIF(TRIM(Fields!CurrencyCode.Value)="GBP","'£'#,0.00;('£'#,0.00)",
IIF(TRIM(Fields!CurrencyCode.Value)="ZAR","'ZAR'#,0.00;('ZAR'#,0.00)","'$'#,
0.00;('$'#,0.00)"))))

What is the expected output? What do you see instead?

An exception with this message error when the program executes uploadReport:
"The definition of this report is not valid or supported by this version of 
Reporting Services. The report definition may have been created with a later 
version of Reporting Services, or contain content that is not well-formed or 
not valid based on Reporting Services schemas. Details: Invalid character in 
the given encoding."

What version of the product are you using? On what operating system?

ReportSync.v1.1.2

Please provide any additional information below.

Change the XML encoding from Encoding.Default to Encoding.UTF8 in ReportSync.cs 
-> bwUpload_DoWork(object sender, DoWorkEventArgs e) -> Line: 122

Original issue reported on code.google.com by micheleg...@gmail.com on 25 Jul 2014 at 9:44