Initialize Grid with Default Search Values

[Dfred]

The Search Part in a grid component allows the specification of initial values. How do you get the grid to initialize with those values already filtered in the grid? This would eliminate the user having to click the 'Search' button every time.

[frankbicknell]

Re: Initialize Grid with Default Search Values

in the onSearchRender event - {grid.Object}.submitSearchForm();

[agillbb]

Re: Initialize Grid with Default Search Values

Hi Frank,
This would just create an infinite loop and crash the system.
But you could put it in the "onGridInitializeComplete" event and it should work o.k. (albeit a bit inefficiently).
Like:
{grid.Object}.setValue('S','ISACTIVE','True');
{grid.Object}.submitSearchForm();

But I have noticed that when you use this function, the search fields appear blank afterwards - not good.

Regards,
Andy.

[frankbicknell]

Re: Initialize Grid with Default Search Values

Hi Frank,
This would just create an infinite loop and crash the system.
But you could put it in the "onGridInitializeComplete" event and it should work o.k. (albeit a bit inefficiently).
Like:
{grid.Object}.setValue('S','ISACTIVE','True');
{grid.Object}.submitSearchForm();

But I have noticed that when you use this function, the search fields appear blank afterwards - not good.

Regards,
Andy.

Actually, I use that in many of my grids and it works perfectly.

[forskare]

Re: Initialize Grid with Default Search Values

The Search Part in a grid component allows the specification of initial values. How do you get the grid to initialize with those values already filtered in the grid? This would eliminate the user having to click the 'Search' button every time.

Click on the Grid -> Query which is where you set the table for the grid. Towards the bottom is a place to set the filter and the order. While I haven't tried this, if you wanted to view all records, a button could do that.

kenn

[agillbb]

Re: Initialize Grid with Default Search Values

Frank,
Apologies if I was incorrect - but exactly this has crashed my system in the past. Maybe something has changed?
The "onGridInitializeComplete" is still a reasonably good (alternative?) place to put this function.
Cheers,
Andy.

[lgrupido]

Re: Initialize Grid with Default Search Values

I'm placing this here so anyone else searching will see it to. The above mentioned method worked for me, but ....

According to a video by Selwyn, the script should be placed in onsearchRENDER event instead of onGridInitializeComplete

http://www.ajaxvideotutorials.com/V1...archFields.swf

{grid.Object}.setValue('S','ISACTIVE','True');
{grid.Object}.submitSearchForm();

[agillbb]

Re: Initialize Grid with Default Search Values

Yes, onSearchRender is the correct place for it as this is called after each and every search refresh. I had posted (above last year) incorrect advice.

[nlk10010]

Re: Initialize Grid with Default Search Values

I'm placing this here so anyone else searching will see it to. The above mentioned method worked for me, but ....

According to a video by Selwyn, the script should be placed in onsearchRENDER event instead of onGridInitializeComplete

http://www.ajaxvideotutorials.com/V1...archFields.swf

{grid.Object}.setValue('S','ISACTIVE','True');
{grid.Object}.submitSearchForm();

Sorry to dredge up this thread but I just ran into this issue. I could not get it to work if my Search part was embedded in the grid: If I tried then I wasn't able to enter ANY search criteria. The cursor would disappear and the Search button wouldn't respond. If I had the Search form in a separate tab then it seemed to work OK, though I'd have to investigate further. The problem with putting the Search form in a separate tab is that I want the grid to appear after I click "Search" and I can't find a way to do that.

So I'm stuck.

If anyone has gotten the onSearchRender to work when the Search is embedded in the grid I'd appreciate knowing how.

Thanks in advance.

[lgrupido]

Re: Initialize Grid with Default Search Values

Why do you feel that the search must be either embedded in the grid or in a separate tab?

Are you running your grid from an a5w form, or from a tabbed UI? In the tabbed UI, it should just appear in the correct place automatically.

From an a5w form, you just place it directly above the grid in the a5w form and they should work together fine.

I might be able to help if I had a bit more info.

Note: I have not tried the above with the search embedded in the grid. I've never even used that option. If it IS embedded in the grid, then you might try the ongridrender event instead.

[nlk10010]

Re: Initialize Grid with Default Search Values

Why do you feel that the search must be either embedded in the grid or in a separate tab?

Are you running your grid from an a5w form, or from a tabbed UI? In the tabbed UI, it should just appear in the correct place automatically.

From an a5w form, you just place it directly above the grid in the a5w form and they should work together fine.

I might be able to help if I had a bit more info.

Note: I have not tried the above with the search embedded in the grid. I've never even used that option. If it IS embedded in the grid, then you might try the ongridrender event instead.

I don't feel that it must be one or the other, I'm just trying to conserve screen real estate (the main and detail grids are rather large, there's a tabbed set of linked grids as well) and tabs do that quite well. I just tried the embedded thingie because, as I say, I couldn't open the main tab programmatically. The video referred to was interesting but I was curious as to why it didn't work in the embedded scenario, I finally figured it out, I think.

I'll give the non-embedded idea a try, the real estate consumed should really be about the same as the embedded approach and the onSearchRender should only fire once (I think).

Again, I'd really prefer to be able to programmatically switch tabs, we'll see how that works out.

Thanks for the ideas.

[lgrupido]

Re: Initialize Grid with Default Search Values

To save screen real estate, you can also show/hide the search part and/or hide the grid until a search is done.

[nlk10010]

Re: Initialize Grid with Default Search Values

To save screen real estate, you can also show/hide the search part and/or hide the grid until a search is done.

Yes, hiding the Search part seems to be the best alternative to Tabs, unfortunately if you try using a FreeForm edit region in the Search part then invoking this option hides everything (Search Part, Grid, Detail Part and LinkedGrids). But I think I can get by without using the FF region.

Thanks, all in all I think this would be the best option.

[lgrupido]

Re: Initialize Grid with Default Search Values

I just did a quick test of that and it worked fine for me. I created a free form edit on one of the search fields, put that field and another field in there, and ran it. It only did the show/hide for the search part, nothing else.

But mine was a very simple example.

[nlk10010]

Re: Initialize Grid with Default Search Values

I just did a quick test of that and it worked fine for me. I created a free form edit on one of the search fields, put that field and another field in there, and ran it. It only did the show/hide for the search part, nothing else.

But mine was a very simple example.

Well thanks for trying, I can get by without using the FF region since the Search part will be kept closed most of the time.

And yeah, it could be that my grids are much more complicated or it could be a small detail (setting) that is causing everything to be hidden, perhaps the fact I need a Custom master template to include the Linked Grids. Don't know, most likely it's unknowable ( :) ), but hiding the straight (non-FF) Search grid works well enough.