ValueFilter Unique Values Displaying Objects Instead of String

ValueFilter Unique Values Displaying Objects Instead of String

Posted by: johnny.su on 18 June 2019, 10:49 am EST

• 

  johnny.su

  • Post Options:
  • Link
    Copy

  Posted 18 June 2019, 10:49 am EST - Updated 3 October 2022, 10:59 am EST

  Hi,

  I just upgraded Wijmo from 5.20173.409 to 5.20181.462 and my custom filtering is not working as expected.

  I override the unqueValues property on the ValueFilter with custom string values. On initial open (see attached pic #1), it’s showing the values as objects. Like somehow it’s parsing the custom string values. But then on subsequent opening of the filter it’s working as expected (see attached pic #2).

  Could you advice what might be going on?

  Thanks,
  
  Johnny

• 

  johnny.su

  • Post Options:
  • Link
    Copy

  Posted 18 June 2019, 10:54 am EST

  Also, I’m setting sortValues to false and overriding the uniqueValues property in the filterChanging handler. The changes seemed to reflect only on subsequent opening of the filter. As you can see that the second picture the values are not filtered.

• 

  johnny.su

  • Post Options:
  • Link
    Copy

  Posted 18 June 2019, 11:09 am EST

  I just want to clarify my initial post. It’s not parsing the override strings. It’s just getting the values on the binding which are Objects. But it should be using the custom values on the initial filter opening like in the attached pic #2.

• 

  abhishek.dutta

  

  • Post Options:
  • Link
    Copy

  Posted 18 June 2019, 9:23 pm EST

  >> Filter showing [object object]

  We are sorry but we were unable to replicate the issue at our end. Please refer to the sample that we used to replicate the issue:

  https://jsfiddle.net/odws8zkL/

  Feel free to modify the above sample or you may provide your sample that replicates the issue.

  >> Changes showing on the second opening

  This behavior is observed because you are applying uniqueValues in the filterChanging event which fires when the filter has been edited by the user. So, when we first open the filter, the filter is not edited so the filterChanging event does not fire. After the second time, the filter has been edited so the filterChanging event is triggered.

• 

  johnny.su

  • Post Options:
  • Link
    Copy

  Posted 19 June 2019, 2:29 am EST

  Hi,

  Filter showing [object object]
  
  My backing binding is an object so that’s why the filter is showing [object Object]. This part I’m okay with as long as I can show my modified unique values. The issue below is what I’m trying to solve.

  Changes showing on the second opening
  
  How can I make sure my changes are shown on the first opening?

  Is there an initial opening event instead of the filterChanging event that I could add an handler to to apply my changes. The version that I was previously on that not have this issue.

  Thanks,
  
  Johnny

• 

  abhishek.dutta

  

  • Post Options:
  • Link
    Copy

  Posted 19 June 2019, 9:06 pm EST

  Hello,

  Filter changing event firing at the second time was actually an issue which has been fixed in the latest build (5.20191.612). Could you please try upgrading your application to this build?

  Please let us know in case you face any issues regarding the update.

  You can download the latest build from the link below:

  https://www.grapecity.com/download/wijmo-enterprise