Completed
Last Updated: 26 Jul 2019 15:08 by ADMIN
Release LIB 2019.2.729 (7/29/2019)
ADMIN
Polya
Created on: 15 Jul 2015 09:51
Category: PivotGrid
Type: Feature Request
6
PivotGrid: Add Culture support for QueryableDataProvider

		
6 comments
Grinden
Posted on: 13 Jun 2019 16:31

Hi,

I'm just dropping by to mention that it is 2019 and the dates are still backwards for approximately 95% of the world's population (just in case you'd forgotten).

Best regards,

Richard

ADMIN
Kalin
Posted on: 29 Mar 2017 12:08
Hi Richard,

We will consider planning this feature for some of our next official releases.
Please follow this feedback item for updates on its progress. 

Regards,
Kalin
Grinden
Posted on: 27 Mar 2017 19:36
I still can't believe this isn't treated as a bug and hasn't been sorted out yet. As far as an end-user is concerned the pivot grid is displaying an incorrect date. It's only an irritating problem if you're looking at several days worth of data, because that gives you context, but in some cases we are using the grid to view data across several hours on a single day. In that instance it's just wrong because there is no way to tell that the date might be backwards during the first 12 days of the month. Please consider fixing this soon.
ADMIN
Stefan
Posted on: 07 Mar 2017 15:36
Hi Yehudah, please use the Like button on the right hand side to cast a vote for this request.
Yehudah
Posted on: 02 Mar 2017 11:06
+1
Grinden
Posted on: 15 Jul 2015 14:40
This issue doesn't appear to be limited to just month names. If I select the original field e.g. "OrderDate" and add it to the rows or columns then this appears in Invariant culture format (e.g. 09/29/2014 00:00:00). I'm hooking the QueryableDataProvider into EF6, so I added an IDbCommandInterceptor to see what is coming back from the database. The value is coming back from the database in a DateTime object, so it must be somewhere in the Telerik code that the conversion is using the invariant culture.
Additionally, when selecting the day group, e.g. "OrderDate - Day" this is currently hardcoded to "Month-Day". I think this should use CultureInfo.DateTimeFormat.MonthDayPattern, because, for example, en-gb should have this as "Day Month".