Repository navigation
_lf - does it work across parent child connections? #628
Unanswered
LeighBerrell
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I have a table hierarchy STANDARD -> CATEGORY -> SUBCATEGORY. I hoped to set up three grids, filter the STANDARD grid by standard name, which would be a connected field in the two grids below, and use linked filters to filter those other two grids, but alas it doesn't seem to work as STANDARD is short text in the top grid and a connection field below, Any idea on whether this is possible with KTL?
So I tried something else that comes close but still doesn't work. I created in the CATEGORY table a short text field called STANDARD TEXT, have it conditionally set to the value of STANDARD. Then in the grid I deleted STANDARD, added STANDAR AS TEXT, and renamed it to STANDARD. I can see _LF from STANDARD grid is trying to work as a linked filter - its setting up a filter on CATGEORY grid saying "STANDARD contains COMPANY" (also tried is) but the filter doesn't work - unless I click into it on the category grid and simply reapply in which case it works as expected.
You can see here uits TRYING to set up the right filter, but its not effective. If I click on that filter and just submit without changing anything, it works....
If I click on that filter and just submit without changing anything, it works.... (a null result is correct for this filter)
All reactions