January 14, 2013 at 8:59 am
Hi
My report is outputting as UTIF-8 but the bank is complaining about that. They say to use DOS, by which I assume they mean csv. I can see that I should be able to modify the url of a report to over-ride the global config settings by using '&rc:OutputFormat = csv'. But where/how do I do that?
I am using Report Builder, not BIDS. Is it possible to do that there?
Thanks in advance,
March 5, 2013 at 8:27 pm
Flybridge (1/14/2013)
HiMy report is outputting as UTIF-8 but the bank is complaining about that. They say to use DOS, by which I assume they mean csv. I can see that I should be able to modify the url of a report to over-ride the global config settings by using '&rc:OutputFormat = csv'. But where/how do I do that?
I am using Report Builder, not BIDS. Is it possible to do that there?
Thanks in advance,
UTF-8 is a unicode standard. The alternative to using Unicode is the old ASCII.
I suspect this stackoverflow answer is what you need, but be aware that changing the RSReportserver.config file (on the report server itself) will apply to all reports. If you have unusual characters in your reports or you use multiple languages (particularly unusual languages such as Thai) then you really do need to output in unicode.
In that Stack Overflow link, LachlanB shows an answer for adding new export options.
As for the URL override, that is just a way of extending the URL.
e.g if this is the link to your report
http://reportmanager.com/reports/report.aspx?ItemPath=ReportName
then the override option would be something like this
http://reportmanager.com/reports/report.aspx?ItemPath=ReportName&Format=CSV
But it's not. The way to see what the URL would be is to run the report, chose the save as CSV option and then quickly copy the address from the web browser. Supplying this URL link directly to your client would let them render and open a CSV file directly.
I suspect, however, that your client might not have direct access to the report manager website and you are sending them reports, so the URL option is not necessarily what you want. You would still have the problem that the CSV will be rendered in unicode unless you make the config file changes as above.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply