Date format bug in Sprint Burndown report (Visual Studio Scrum 1.0 RTW) – non US locales only.
Only applies if you are in a non-US locale.
Working through a Visual Studio Scrum implementation on a client site at the moment we noticed there seems to be a date format bug in the Sprint Burndown report in Visual Studio Scrum 1.0 RTW if you are in a non US locale. This prevents the current sprint bring calculated and the report falls over with an error:
Query execution failed for dataset ‘dsSprintsCurrent’. (rsErrorExecutingCommand)
The conversion of a nvarchar data type to a datetime data type resulted in an out-of-range value.
My fix is in the RDL and to replace the line:
DECLARE @Tomorrow DATE = CONVERT(DATE, DATEADD(day, 1, @Today)
with
DECLARE @Tomorrow DATE = CONVERT(DATE, DATEADD(day, 1, CONVERT(DATE, @Today, 103)))
No doubt there will be an update at some point but thought put up this information to help anyone who has this issue.
Update (22nd July 2010): The official fix revolves around the data type of the “Today” parameter in the report which is incorrectly set to a string:
<ReportParameter Name="Today"> <DataType>DateTime</DataType> <DefaultValue> <Values> <Value>=today</Value> </Values> </DefaultValue> <Hidden>true</Hidden> </ReportParameter>


Team Foundation Server – Scrum Reports Failing “for some” team members - Willy's Cave - Site Home - MSDN Blogs said,
[...] For more details about issue have a look at: http://stuartpreston.net/blog/2010/07/21/date-format-bug-in-sprint-burndown-report-visual-studio-scr... [...]
Add A Comment