Grid column filter values are not encoded in url

Grid column filter values are not encoded in url

Posted by: bozjator on 3 December 2019, 2:07 am EST

• 

  bozjator

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 3 December 2019, 2:07 am EST

  Hi,

  I have a problem with special chars in values in column filters.
  
  If i want to filter column by value “word1 & word2”, the & sign is not encoded in the url and i get an error.
  
  Here is an example of call that a grid makes after setting a filter: domain.com/odata/table?$format=json&$count=true&$skip=0&$top=200&$filter=((ColumnName%20eq%20’word1%20&%20word2’))

  So in the url, in the part %20&%20 you can see that & sign is there in a normal “shape” and is treated the same as the & between $skip=0&$top=200 (so its treated as a part of url and not as a part of value for filtering).

  Is there a way to make filter values encoded?

  Regards

• 

  manish.gupta

  

  • Post Options:
  • Link
    Copy

  Posted 3 December 2019, 4:55 pm EST

  Hi,
  
  As per your question, you are using the OData API to show the Data in FlexGrid API. The FlexGrid provided built-in collection view for OData, named ODataCollectionView. Please refer to the following demo sample for reference:
  
  https://www.grapecity.com/wijmo/demos/Grid/Data-binding/ODataAPI/purejs

  In the sample, as we applied the Value Filter for Two values using the Filter Dialog, the Server call will be as follows:

  $format=json&$inlinecount=allpages&$filter=((CustomerID%20eq%20%27ALFKI%27)%20or%20(CustomerID%20eq%20%27ANTON%27))
  

  The above observation is with the latest build 2019v3.637. Please let us know if you have any further queries.

  Regards,
  
  Manish Gupta

• 

  bozjator

  • Post Options:
  • Link
    Copy

  Posted 3 December 2019, 9:17 pm EST - Updated 3 October 2022, 9:11 am EST

  I think we don’t understand each other.
  
  Here is an example from page for which you give link (please see the image below):
  
  I was filtering column Company Name by the word “word1 & word2”, and this gives an error, because this word is not properly encoded to be put into url. You can see it on the image.

  

  1605×902 229 KB

• 

  ashwin.saxena

  

  • Post Options:
  • Link
    Copy

  Posted 4 December 2019, 3:35 pm EST

  Hi Blaž,

  We have forwarded the issue to the dev team with internal tracking id 409351. We will update you as soon as we will hear from them.

  Regards,
  
  Ashwin

• 

  bozjator

  • Post Options:
  • Link
    Copy

  Posted 22 January 2020, 8:16 pm EST

  Hi,

  I think this was fixed in Wijmo Build 5.20193.646
  
  Can you please confirm this?
  
  Is there a list of all fixes that were made in Wijmo Build 5.20193.646 ?

  Regards

• 

  ashwin.saxena

  

  • Post Options:
  • Link
    Copy

  Posted 22 January 2020, 9:02 pm EST

  Hi,

  Yes, the issue is fixed in the latest release build.

  PFA: Fixes in the latest release.

  ~regards

  ChangeLog.zip