Dynamic Filter wiped out if Lookup grid has Search part

[RichCPT]

Take this as a comment or a question:

Shouldn't the "Lookup Definition Window" for defining the Lookup for a Texbox Control provide a distinction between a "Base Filter" and a "User Filter" like the "Action Javascript - Open a Grid Component?"

When defining a Lookup for a Textbox control, if the called grid has a search part then the filter specified by the caller is wiped out. I just needed a simple filter on two fields. So, I removed the fields from the Define Lookup Window's Filter and put them into the called grid's Search Part and set their properties to hidden and disabled (redundant, I know). I set their initial values to session variables. (I would feel safer using "arguments" like video M53, but that is a topic for my previous post!) And I verified the search values in these fields would not get wiped out if the user clicked the "Clear Search" button.

I'd really like to see the "Lookup Definition Window" and the "Open a Grid component" action javascript behave the same. It makes it difficult on the beginning developer to learn what can be done with the "Open a Grid component" and then have to figure out how to do the same thing in the "Define Lookup window", plus having to workaround other issues like: 1) "Do the filters support complex expressions?", and 2) "Why the entire filter is sometimes ignored?". It seems to me that with a little tweaking the "Open a Grid component" could include a property to specify what modes should be allowed for the called grid Select, Insert, Change, Delete. If "Selection" is allowed then other properties that we see in the "Define Lookup Window" would be available, like "field mapping".

- Rich Fulham

[GGandhi]

Re: Dynamic Filter wiped out if Lookup grid has Search part

When defining a Lookup for a Textbox control, if the called grid has a search part then the filter specified by the caller is wiped out. I just needed a simple filter on two fields. So, I removed the fields from the Define Lookup Window's Filter and put them into the called grid's Search Part and set their properties to hidden and disabled (redundant, I know). I set their initial values to session variables. (I would feel safer using "arguments" like video M53, but that is a topic for my previous post!) And I verified the search values in these fields would not get wiped out if the user clicked the "Clear Search" button.

1> i take this as a comment and a question.
2> i made two areas bold to address so we both know what i am talking about.

when an item is hidden the value is exposed, as far as i know. the user may not know but the program knows. on the other hand when disabled the user and the program do not know about that control. so any value that is in that control, the program does not know or cannot know. if you need to use that field for any purpose then it is best is to keep only hidden.

there is a check box on the properties of the search field definition - "has clear search properties" something like that. uncheck that, the clear search criteria will disappear. the user cannot wipe out what you set by clicking that button, it does not exist.

ps:
i just tested with some dummy initial value, and clicked the clear search criteria button. while everything cleared the the field that has an initial value did not change. you might want to test and see if that is correct.

[lgrupido]

Re: Dynamic Filter wiped out if Lookup grid has Search part

All that is fine, but the problem remains that if you set a dynamic filter and then try to search on a lookup, the dynamic filter gets wiped out.

Lets say you have a table related to a company, called contacts. it is a list of all the contact at a particular company. Create a lookup grid for the company contacts.

Now set a dynamic filter based on the company id and lookup the company contacts. Your initial list will show just the company contacts.

But lets say you have a search by last name in the lookup grid. If you use that search then you will see all of the contacts for all of the companies in the lookup grid that match the last name search, not just the ones related to your dynamic filter.

If the lookup grid wouldn't lose the dynamic filter on a search, you wouldn't have to jump through any hoops at all.

I have this problem now and am looking for a solution. Haven't found one yet either ....

[RichCPT]

Re: Dynamic Filter wiped out if Lookup grid has Search part

Yep, I wish more people would report this is an issue to AlphaSoftware. My first post does contain a workaround, if you are willing to use session variables (which I am super reluctant to use):

I removed the fields from the Define Lookup Window's Filter and put them into the called grid's Search Part and set their properties to hidden and disabled (redundant, I know). I set their initial values to session variables.