Chaining Parent Filters Doesn't Properly Update Value Selection List

Luke shared this problem 6 months ago
Completed

Scenario happens when you have Filter A as the parent of Filter B, which is the parent of Filter C.
Then if you change your selection for Filter A, the Filter B options will change to only what should be available, but the Filter C options DO NOT update (or even reset to just "-Select-").

Example


Filter A (City)Filter B (Property Type)Filter C (Address)
Los AngelesOcean Front1 Pine Street
Los AngelesCommercial Property2 Daulton Street
San DiegoOcean Front3 Beach Street
AustinCommercial Property4 West Street

In this example if you have ["Los Angeles", "Ocean Front", "1 Pine Street"] selected and switch filter A to "San Diego" then "1 Pine Street" will still be selected instead of returning to "-Select-" or "3 Beach Street" (And when you look at the dropdown list it still only shows "1 Pine Street" until you alter the selection of the filter's direct parent, not one of its parents ancestor filters). Is there a way for the the filters to be fixed so ALL descendant filters recalculate?


(In my environment I am using "Cached Values on Demand", not sure if the issue persists for all types though)


Application Version:9.7.0.3
java.version:11.0.20.1
os.name:Linux
os.arch:aarch64
os.version:5.15.0-1041-aws

Replies (4)

photo
1

Hello Luke,

Thanks for reaching out to Yellowfin support.

To gain a better understanding, could you kindly create a new report, describe the issue, and share it's screen recording with us?

Also, Could you please replicate the issue using ski team database and share the yfx file with us? That would be greatly appreciated.

Regards,
Sharwari Inkane

photo
1

Hello Luke,

I hope all is well

I just want to touch base to see if you had a chance to read through my response. If you can let me know that would be great.

Regards,
Sharwari Inkane

photo
1

Hello Luke,

Greetings for the Day.

This is a follow up reminder that 2 days have passed without any activity in this ticket. When there's no activity, it usually means either that you have identified the solution for the reported issue or that the matter is no longer relevant and after 5 days (2 days from now) without any activity, we assume that the ticket can be closed.

If this is not the case, please do reply and let us know how we can be of further assistance, we would be happy to assist.

Regards
Sharwari Inkane

photo
1

Hello Luke,

Greetings for the Day.

This email is to notify you that we believe that you have identified the solution for the reported issue or that this ticket can be resolved for now. Because of age and inactivity I am going to go ahead and mark this ticket as Completed. However, if you ever wanted to revisit this or have anything else I can help you with, please let us know, we will be more than happy to do so.

Regards
Sharwari Inkane

Leave a Comment
 
Attach a file