Okay here’s the scenarion.
Our main app starts on a table view for which there are four pre-programmed menu filters.
It was done this way so that further filtering could be done if necessary
For arguments sake call them SET-A SET-B SET-C SET-D
The table by defaults opens with no filtering applied just sorting.
When you want to edit the record from the table you click the button in the table for that entry.
There are multiple buttons for argument sake BUTTON-A BUTTON-B BUTTON-C etc
These BUTTONS go to pages created under the non filtered option.
Now when it becomes filtered I want the same function BUTTONS TO STILL BE CHOOSEABLE.
BUT, Knack generates a new version of the BUTTON-A, BUTTON-B etc pages under the new filtered set.
I cannot for the life of me work out how NOT TO CONTINUALLY REPLICATE THESE PAGES under the filtered records sub-sets.
It makes changes to the page a nightmare as you have to make the same change to 4 different page which are all the same !!!
It would be much more preferable to re-use the one page for all subsets.
Maybe I am missing something, or just been at the problem too long.
But for the liffe of me I cant see how else to do it
Filtered table selected using the buttons up top
Schema showing how pages are being duplicated making maintenance of them a nightmare.
Change 1 have to change all
Perhaps I am misunderstanding the whole child relationship of pages within Knack.
This method works but as I said, its a maintenance nightmare.
Appreciate slap on back of head for dumb or whatever you can add to this discussion
