cancel
Showing results for 
Search instead for 
Did you mean: 

what is the best practice for Lookup search using MDM java api

Former Member
0 Kudos

Hi All,

         I have a main table along with one lookup value as one of the fields, when i am trying to include the lookup value in into my search criteria along with the main table fields i am using the following two scenarios, in both the cases i am able to achieve the correct search functionality what i need to know from you is which one is the best practice for the search criteria for lookup values ?

          1. Earlier i used to pass the RecordID to my PICLIST SEARCH CONSTRAINT of the lookup value to my  i need to search.

          2. where as in this scenario instead of passing RecordID of the lookup value simply i am passing the search string to my SEARCH CONSTRAINT  entered               by the user for lookup value to search 

Thanks,

Ramprasad.

Accepted Solutions (0)

Answers (1)

Answers (1)

monalisa_biswal
Contributor
0 Kudos

Hi Ram,

Its better to pass lookup search values in picklist search constraint rather than text search constraint.

As for the text search constraint, you need to pass display value for the lookup field. So If in case the  lookup table has more than one fields and display field in main table has changed, search will fail.

Also performance wise picklist search is faster compared to text based search.

Thanks,

Mona

Former Member
0 Kudos

Hi Mona,

             Thanks for your valuable information

Ram.

junwu
Active Contributor
0 Kudos

i disagree....how you can  get the exact lookup id? you are expecting user to fill the accurate value?

just go with text search, it is easy and functional.