ParamQuery grid support forum

General Category => Bug Report => Topic started by: ami dev on December 04, 2018, 07:12:46 am

Title: Default order after filtering by range
Post by: ami dev on December 04, 2018, 07:12:46 am

We were wondering if this is a glitch for the latest version.
Once we filtered by range, the default displaying order won't be restored even though we remove the filter.
For example, see the default order for the demo page.(see 1-1.png)
https://paramquery.com/pro/demos/filter_header_local

1. Filter only "United Package" by Shipping Via and the result is correct.
(Uncheck Shipping Via and check "United Package": see 1-1.png, 1-2.png)
2. Remove the filter but the displaying order look different than the default displaying order.
(Check Shipping Via: see 2.png)

Select filter for version 4 was restored the default dsiplaying order by removing filters by the way.

Title: Re: Default order after filtering by range
Post by: paramvir on December 04, 2018, 10:33:27 am

I'm able to reproduce it, so moving it to bug log, thanks for raising the issue.

Title: Re: Default order after filtering by range
Post by: paramvir on December 17, 2018, 09:22:09 am

This is fixed in v5.6.1

Title: Re: Default order after filtering by range
Post by: ami dev on December 19, 2018, 11:23:16 am

In the list without paging, We confirmed that it is fixed.
However, in the list where paging exists, this bug is still occurring.

You can confirm by adding the following settings to the demo page.
https://paramquery.com/pro/demos/filter_header_local (https://paramquery.com/pro/demos/filter_header_local)

Code: [Select]

pageModel: {
    type: "local",
    rPP: 10,
    rPPOptions: [10, 100, 500]
},


Title: Re: Default order after filtering by range
Post by: paramvir on December 19, 2018, 11:17:53 pm

Noted, thanks for pointing it out.

Title: Re: Default order after filtering by range
Post by: paramvir on January 28, 2019, 02:29:30 pm

This is fixed in v6.0.0

Title: Re: Default order after filtering by range
Post by: ami dev on January 28, 2019, 02:38:43 pm

We confirmed that it was fixed.
Thank you very much.