[CLOSED] GridFilters feature messes with Paging/Sorting?

[vadym.f]

Hi,

This seems like a difficult to reproduce behavior or bug. My code sample is definitely suffering from it on a more consistent basis but I've been trying to see if any demo is affected. Please check the GridFilters Local demo at https://examples2.ext.net/#/GridPane...Filters_Local/. Click on the ID header twice. Page to the next page until you reach the last page. Notice that ID 27 is at the very bottom despite the sort order being DESC. Page back to the first page and notice that ID of 1 is at the top despite the descending sort order.

Remove the filters and notice how sorting and paging now work as designed.

[Vladimir]

Hi Vadym,

We recall such a bug.
http://forums.ext.net/showthread.php?25172

It should be fixed in SVN.

Could you, please, try to reproduce it with the trunk?

[vadym.f]

Hi Vladimir,

Has it been fixed in branches or tags in SVN? I update the source code from http://svn.ext.net/premium/branches/2.2.

Update:
Never mind, I should probably get it from the trunk at http://svn.ext.net/premium/trunk

[Vladimir]

No, it is in the trunk only. And it will go to the upcoming v2.3 release.

[vadym.f]

Confirmed. That problem is gone from the trunk. However, I've spotted a new issue that didn't exist in the branches. Date model field and/or date column now misbehave displaying empty strings for valid dates. Please notice that my code and data have been unchanged between the switches from branches and trunk.

    <ext:Store runat="server" ID="Store1" PageSize="20" OnReadData="Store1_Refresh">
        <Model>
            <ext:Model ID="Model1" runat="server" IDProperty="ID">
                <Fields>
                    <ext:ModelField Name="ID" Type="Int" />
                    <ext:ModelField Name="Code" Type="String" />
                    <ext:ModelField Name="CreatedDate" Type="Date" DateFormat="yyyy-MM-ddTHH:mm:ss" />
                </Fields>
            </ext:Model>
        </Model>
        <Sorters>
            <ext:DataSorter Property="CreatedDate" Direction="DESC" />
        </Sorters>
    </ext:Store>
<ext:GridPanel ID="GridPanel1" runat="server" StoreID="Store1">
                <ColumnModel ID="ColumnModel1" runat="server">
                    <Columns>
                        <ext:Column ID="Code" runat="server" Width="180" Text="Code" DataIndex="Code" />
                        <ext:DateColumn ID="CreatedDate" runat="server" Width="160" Text="Created Date" DataIndex="CreatedDate"
                            Format="yyyy-MM-ddTHH:mm:ss" />
                    </Columns>
                </ColumnModel>
                <Features>
                    <ext:GridFilters runat="server" Local="true">
                        <Filters>
                            <ext:DateFilter DataIndex="CreatedDate">
                                <DatePickerOptions runat="server" TodayText="Now" />
                            </ext:DateFilter>
                        </Filters>
                    </ext:GridFilters>
                </Features>
</ext:GridPanel>

[vadym.f]

It's turned out that the model field DateFormat option isn't very robust after all. I've had to modify my T-SQL SELECT query in order to chop off milliseconds. DateFormat="yyyy-MM-ddTHH:mm:ss" doesn't recognize a value as valid date if it has trailing non-zero milliseconds. For instance, this date would be displayed as empty in my setup:

2011-07-17 13:25:41.123

I've tried to alter the DateFormat following MS suggestions at http://msdn.microsoft.com/en-us/library/bb882581.aspx but it never worked. As I said earlier, a T-SQL workaround truncating milliseconds eventually did the trick but it's obviously not what you want to do to fix the UI.

SELECT CONVERT(datetime, CONVERT(char(19), getdate(), 126))

[Vladimir]

Are you sure that DateFormat is required in your case? If you remove DateFormat then does it work?

In any way, such format ("yyyy-MM-ddTHH:mm:ss") cannot parse date with milliseconds
To support milliseconds you should use "yyyy-MM-ddTHH:mm:ss.fff"

[vadym.f]

Indeed, DateFormat wasn't necessary and it works well without it. I couldn't get milliseconds to display with your suggestion though. Somehow, .fff is recognized as string literal.

Update:
Based on the client side formatCodes enumerator defined in ext-all-dev.js file, the date format to capture milliseconds should read

Format="yyyy-MM-ddTHH:mm:ss.u"

or

Format="yyyy-MM-dd HH:mm:ss.u"

It worked for me.

[Daniil]

I guess this also might work in your case.

<ext:ModelField Name="CreatedDate" Type="Date" RenderMilliseconds="true" />

[vadym.f]

I guess this also might work in your case.

<ext:ModelField Name="CreatedDate" Type="Date" RenderMilliseconds="true" />

Thanks Daniil! It works in the sense that date time literals with non-zero milliseconds like 2011-07-17 13:25:41.123 get displayed correctly. To actually view the milliseconds, I still need to define the Format property on the DateColumn:

Format="yyyy-MM-dd HH:mm:ss.u"