Daniel, In your Reports Layout view, the properties window should look like that. The first item in that list is <Expression...>, which opens the Edit Expression dialog. Here if select Globals->Language you will get the above value. Just the other day, one of my developers encountered the exact problem you mentioned.
Cheers, YM ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Daniel Sent: Friday, 1 June 2007 14:37 To: [email protected] Subject: RE: [OzTFS] Reporting Woes Yogesh, Thanks for your response. I have specified the language on the reports via the Language property on the Layout view. Can you give me an example of how I would use your expression to fix the issue I have described? I am using a non-queried parameter with a data type of DateTime. This creates the date picker control for me in the report which, as I mentioned, refuses to take Australian formatted dates when in Preview mode. However, when running the report after it is Deployed it suddenly accepts Australian dates. Michael. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of MULYE,Yogesh Sent: Friday, 1 June 2007 12:32 PM To: [email protected] Subject: RE: [OzTFS] Reporting Woes Daniel, 1. For custom reports you should use Language=User!Language expression. 2. Sub-reports will not have problems so long as the Language=User!Language is specified. 3. The TFS Datasources can be moved. They are shared datasources. I've moved them in Production to 'Datasources' folder nder root. 4. Not sure about the last problem, perhaps the reports' parameters are different. datatime parameter should allow setting both the date and time components and querying on them. Maybe you could specify which TFS reports have issues so I can confirm. Cheers YM ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Daniel Sent: Friday, 1 June 2007 11:29 To: [email protected] Subject: [OzTFS] Reporting Woes Hi all, Sorry for lumping so many questions into one post but I am finding lots of issues with reporting against the TFS Warehouse. I'm running a custom report against the TfsReportDS data source and find that I cannot get accurate time information returned in the report. I know that a particular change set was checked in at 23/05/2007 10:34:40 AM, yet the dates retrieved from the warehouse indicate 23/05/2007 1:11:08 AM (if I use the Changeset, File, Work Item or Changeset table's _LastUpdatedTime field) or 23/05/2007 12:00:00 AM (if I am using the Code Churn table's Date field). Looking at the change set from within Visual Studio (by going through Work Item history) you can see the correct check in time of 10:34:40 AM... so that time is being stored in there somewhere. Is it possible to get exact times back from the warehouse, and if so, which field should I be using to get the actual check in time for a Change Set? While I'm at it: other annoyances that I have found that I'm wondering if anyone has solutions to: * The DateTime picker field (for report parameters) in the Preview pane of the report designer will only accept US or universal formatted dates, regardless of the language specified for the report. (You will have to manually type in say 2007-23-05 or 23/05/2007 and can't pick the date using the calendar which will enter 23/05/2007 if you are using English (Australia) for the report). Is this a bug? Is there a workaround other than using US dates? * This also means that if you have a sub-report (and it uses a date parameter passed from the parent report) you will not be able to run the sub-report in the Preview pane. Your date gets converted from the manually entered US/Universal format to the form's specified language before being passed to the sub-report. In turn this means the sub-report fails as the Aussie formatted date is supposedly an invalid date when passed as a parameter. The only way I have found to test the embedded sub-report is to run it separately and manually enter the dates, or to deploy it and run it from team Explorer or directly on the Report Server website. * For some reason the servers we are using have their data sources (TfsOlapReportDS and TfsReportDS) stored in the root of the Report Server site. (Is this a hangover from beta versions of TFS that have been upgraded?) I am unable to find a way to specify the root of the report server as the location for the data sources in the Business Intelligence Project when setting the project properties (leaving the TargetDataSourcefolder field blank places your data sources in the TargetReportFolder, and not the root of the server) I've tested moving a dummy data source into a sub folder and it seems to update any dependant reports... but I'm reluctant to do this on the TFS data sources as its in a production environment. Can anyone else confirm that moving the data sources will not break dependencies and that it is safe for me to do so? * I have multiple custom reports using the same data source and deployed on the same server. On some of the reports you can manually enter a time as well as the date into the date parameter fields and successfully filter the results by both time and date. On other reports entering a time either returns no results or incorrect results. I can see no difference between the reports so I am wondering why the report server will allow times in the parameters in some reports and not others. Any ideas? Regards, Michael Daniel. OzTFS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by www.readify.net Notice: The information contained in this email message and any attached files may be confidential information, and may also be the subject of legal professional privilege. If you are not the intended recipient any use, disclosure or copying of this email is unauthorised. If you received this email in error, please notify the DEWR Service Desk and delete all copies of this transmission together with any attachments. OzTFS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. View the web archives at http://www.mail-archive.com/[email protected]/ Powered by mailenable.com - List managed by www.readify.net OzTFS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. View the web archives at http://www.mail-archive.com/[email protected]/ Powered by mailenable.com - List managed by www.readify.net Notice: The information contained in this email message and any attached files may be confidential information, and may also be the subject of legal professional privilege. If you are not the intended recipient any use, disclosure or copying of this email is unauthorised. If you received this email in error, please notify the DEWR Service Desk and delete all copies of this transmission together with any attachments. OzTFS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. View the web archives at http://www.mail-archive.com/[email protected]/ Powered by mailenable.com - List managed by www.readify.net
<<Outlook.jpg>>
