This content has been marked as final. Show 10 replies
If you leave search keys open on the target component search record you are moving to, it will give you the search page. I suggest you add the keys to your &AdditionalParameterString;
You might also use some code like below on the SearchInit of the target component search record.
Record.Keyfield1 = KeyValue1;
Record.Keyfield2 = KeyValue2;
Let me put you the scenario..
I cannot add SetSearchDialog.... cause it will change the functionality of the target component when tried to access alone..
I have created a custom Search Page where user gives search criteria & details are fetched in grid below.
There is a Search button which along with having code for Search criteria has the the sample code which I have mentioned, is written in the Field change of Search Button.
Now I had already used a hyperlink in the grid coloumn & written transfer function to do the needful, & it works fine..
However, I later I want to replace that grid coloumn with a HTML Area field & want the same functionality.
As of now, Hover Text works fine..
Custom Search Page works fine..
Correct value too is carried forward to the target Components Search page..
Only thing left is not automatically bypassing the Search Page of the Target Component..
As in Transfer Funtion:
Transfer( False, MenuName.MENUNAME, BarName.MENUITEM1, ItemName.EMPLOYEE_COM, Page.EMPLOYEE_PG, "U", SAMPLE_TBL.EMPL_ID, True);
The Last "TRUE" is responsible for bypassing the search page in target component along with the keys value passed.
In similar fashion any idea for my trouble??
You are seeing the search page, because of two reasons;
1. If a unique row is not identified
2. if Force Search Processing has been selected
see this about the key list in peoplebooks:
An optional list of field specifications used to select a unique row at level zero in the page you are transferring to, by matching keys in the page you are transferring from. It can also be an already instantiated record object.
If a record object is specified, any field of that record object that is also a field of the search record for the destination component is added to keylist. The keys in the fieldlist must uniquely identify a row in the "to" page search record. If a unique row is not identified, of if Force Search Processing has been selected, the search dialog appears.
If the keylist parameter is not supplied the destination component's search key must be found as part of the source components level 0 record buffer.
so if for example your search record has three search keys (emplid, empl_rcd, jobcode) you need to fill all three search keys. Or you cannot identify the row you want of the target component.
see also peoplebooks about this.
Force Search Processing has NOT been selected in any of the component.
Transfer function with providing only 1 key helps to bypass the search page, so I believe what you said was correct but not in this specific case..
I tried with providing all the keys but not helpful.
Unique row is identified since EMPL_ID is a key.