Thought I'd found a workaround for this but just discovered I haven't.
A grid has a Search Part, and the Search Part property "Hide Grid when no search active" is checked. Great.
Now I need to hide the Search Part Submit button until particular search criteria are selected. This isn't an option in the Search Part properties, there's no way to customize the Search Part toolbar like the Grid or Detail Views toolbars, and the Search Part submit button has no HTML button id to reference. I successfully created what I thought was a workaround to this, creating an HTML button in a Search Part freeform region with onclick="{grid.Object}.submitSearchForm();" and style="visibility:hidden". I then used Javascript to get the id of the button and make it visible when certain search fields had criteria in them. Frankly, pretty proud of myself.
But as you can see in the attached image, if I make the button visible and then switch to another tab, it shows up in the other tab as well. It seems this is the case unless the Tabbed UI opens an a5w page with a component on it (as opposed to the Tabbed UI opening a grid directly on a "virtual page").
This is a function I need in lots of grids and I can't lose the functionality of opening grids directly from buttons in my application, so I've got to get something workable and universally functional.
All ideas are welcomed... Thanks in advance.
A grid has a Search Part, and the Search Part property "Hide Grid when no search active" is checked. Great.
Now I need to hide the Search Part Submit button until particular search criteria are selected. This isn't an option in the Search Part properties, there's no way to customize the Search Part toolbar like the Grid or Detail Views toolbars, and the Search Part submit button has no HTML button id to reference. I successfully created what I thought was a workaround to this, creating an HTML button in a Search Part freeform region with onclick="{grid.Object}.submitSearchForm();" and style="visibility:hidden". I then used Javascript to get the id of the button and make it visible when certain search fields had criteria in them. Frankly, pretty proud of myself.
But as you can see in the attached image, if I make the button visible and then switch to another tab, it shows up in the other tab as well. It seems this is the case unless the Tabbed UI opens an a5w page with a component on it (as opposed to the Tabbed UI opening a grid directly on a "virtual page").
This is a function I need in lots of grids and I can't lose the functionality of opening grids directly from buttons in my application, so I've got to get something workable and universally functional.
All ideas are welcomed... Thanks in advance.
Comment