Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

  • slick07
    replied
    Sorry about the fetch call. I confirm that the problem is fixed. Thank you very much!

    Leave a comment:


  • Isomorphic
    replied
    You no longer need the call to fetchData() in your changed event - the call to setImplicitCriteria() causes the fetch.

    Leave a comment:


  • slick07
    replied
    Hi Isomorphic and thank you for the follow up. Actually we do not even need the setTreeRootValue() and probably remained there because we created this test case from an old one...

    I have removed the usage of setTreeRootValue() and tested with v13.0p_2023-03-02/LGPL Development Only (built 2023-03-02). The result is that now the TreeGrid remains empty no matter what I select within the SelectItem.

    Leave a comment:


  • Isomorphic
    replied
    A quick follow-up about using setTreeRootValue() - the method is designed to allow a TreeGrid to show a subset of data, and using it with keepParentsOnFilter requires fetchMode "paged" and custom server code on your part, which responds to the presence of keepParentsOnFilter in the DSRequest to return all the proper parent nodes.

    So, rootValue/treeRootValue are basically invalid in your use-case, where keepParentsOnFilter is set and the fetchMode is effectively "local".

    Leave a comment:


  • Isomorphic
    replied
    This issue has been sitting for a while but has now been addressed - you can try out the fix as of today's builds, dated February 24 and later.

    Your use-case (keepParentsOnFilter with implicitCriteria which is the PK of a specific record) is a bit unusual, so please do let us know if spot any other trickiness like this.

    Note that we're investigating a separate possible issue with the use of setTreeRootValue() in this use-case - for now, you'll need to remove your call to that method to see things work as you expect.
    Last edited by Isomorphic; 27 Feb 2023, 01:34.

    Leave a comment:


  • Isomorphic
    replied
    Thanks for the report - we're taking a look and will update here shortly.

    Leave a comment:


  • slick07
    replied
    Hi Isomorphic,

    After further tests it seems that for TreeGrids with setKeepParentsOnFilter(true); the implicit filter mechanism does not work correctly. Only the first applied implicit filter works correctly and any other subsequent implicit filters results in an empty TreeGrid.

    I have attached a test case to reproduce the problem. Just change the filter using the SelectItem.

    Using SmartClient Version: v13.0p_2022-12-31/LGPL Development Only (built 2022-12-31)

    Thank you!
    Attached Files

    Leave a comment:


  • slick07
    replied
    I confirm that the problem was fixed. Thank you!

    Leave a comment:


  • Isomorphic
    replied
    We've applied a fix for this regression in behavior - while cache-sync had been fixed, a logic flaw meant that setImplicitCriteria() itself was not initializing filtering for ResultTree.

    Please retest with a build dated October 28 or later

    Leave a comment:


  • Isomorphic
    replied
    In fact, we've reproduced this and we see what the problem is - we're making a fix and will update here when it hits builds.

    Leave a comment:


  • Isomorphic
    replied
    This seems an almost impossible result, given the changes we made.

    Please show standalone code we can run to see the issue.

    Leave a comment:


  • slick07
    replied
    Unfortunately now the filtering mechanism seems to got broken... The same code:
    - with the old version of SmartGWT it updates the interface accordingly with the applied implicit filters (but has the cache problems)
    - with the new SmartGWT version (SmartClient Version: v13.0p_2022-10-25/LGPL Development Only (built 2022-10-25)) it does not apply the implicit filters at all and it just displays all data as if no filter was applied. Furthermore if we apply an additional filter using treeGrid.filterData(filter); the TreeGrid becomes empty and remains that way no matter what we do and a bunch of "Attempted to use unknown operator undefined" warnings appear in the console.

    Leave a comment:


  • Isomorphic
    replied
    We've fixed cache-sync as it relates to implicitCriteria in ResultTrees, and this addresses your issue.

    You can try out the fix in builds of your branch dated October 21 or later.

    Leave a comment:


  • Isomorphic
    replied
    Apologies for the delay on this - it looks like some parts of implicitCriteria support are missing for ResultTree/TreeGrid.

    We'll look into it this week and let you know when we've added the incomplete bits.

    Leave a comment:


  • slick07
    replied
    Hi Isomorphic , Could you please give us a helping hand with the above misbehavior of setImplicitCriteria(Criteria) on TreeGrids? I can try to provide a test case if needed. Thank you!

    Leave a comment:

Working...
X