Time Series Analyst: Issue with Date Picker Control

horsburgh[CodePlex]
ODM tools uses a Month/ Day/ Year format to select the date range. I then queried a dataset directly from the ODM database using an SQL query for the exact same parameters [SiteID], [VariableID] , date range used in ODM Tools and replicated the graph manually
in Excel, verifying that ODM tools was correctly querying the dataset.
nbsp
The TSA WEB app gives an error to the effect of ‘Non valid start date’ if you select the exact same dates using the calendar entry form
(which is a pop-up javascript tool…)
nbsp
The javascript populates the form in M / D / Y format, however:
Manually changing the date from M / D / Y to D / M / Y will ‘correct’ this formatting, and the app will produce the graph
nbsp
After a bit of poking around, I tried a quick edit of the javascript source hosted on our IIS web server. Changing the part:
nbsp
dateFormat:”mm/dd/yy” to dateFormat:”dd/mm/yy”
nbsp
seems to resolve this issue for dates picked by the user … I’m still not 100% sure if this will fix dates that it populates initially or when you change sites/variables.
nbsp
Hopefully this will clear up some issues users may be having with the CUAHSI tools, let me know if you need any further info.
nbsp
David T. Krupicz
Central Lake Ontario Conservation Authority

Start with the JavaScript date-picker source hosted on the IIS web server and inspect the dateFormat setting and where selected dates are initially populated or updated after site and variable changes. Reproduce the invalid start-date error with the calendar, then verify that the same date range produces the graph without requiring manual format changes.

Written by the indexing model from the issue text.