Home Dashboard Directory Help

Report Builder 1.0 and 2.0 ignore regional settings by default by michael12345



Sign in
to vote
Type: Bug
ID: 794448
Opened: 7/18/2013 5:03:15 PM
Access Restriction: Public
User(s) can reproduce this bug


We are in New Zealand, and our users are almost exclusively in New Zealand/Australia. Therefore, everyone wants their dates in D/M/Y format, their default page size to be A4, and their units of measure to be metric (i.e. cm/mm).

Both RB1.0 and RB2.0 appear to ignore our local settings by default, assuming that we'll want a page size of Letter, measurement in inches, and date format of M/D/Y.

I get this issue even though the regional settings on my local machine, and on the report server are set to "English (New Zealand)". This occurs in both the Report Builder 1.0 that is once-click launched from Report Manager, and in Report Builder 2.0 (10.0.4000.0) that I have installed locally.

RB3.0 does appear to obey our regional settings to the extent that it defaults to A4 and metric measurements, but still the US date format. The version of RB1.0 that SSRS2012 pushes down to clients when they click the "Report Builder" button in Report Manager also has the problem.
Sign in to post a comment.
Posted by Microsoft on 6/2/2014 at 4:48 PM
Thank you for submitting this feedback. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SQL Server. The reasons for closing these bugs are following:
1.     The fix is risky to implement in the current version of the product (service packs)
2.     Scenarios reported in the bug are not common enough
3.     A viable workaround is available
Thanks again for reporting the product issue and continued support in improving our product.
Matt Jones
SSRS Tiger Dev Team
Posted by Microsoft on 5/14/2014 at 4:49 PM

Thank you for submitting this feedback. We are investigating the issue and will update you when we have more information.

Matt Jones
SSRS Tiger Dev Team
Sign in to post a workaround.