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
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
Comment