Set Default Search Operator at SFM level instead of Globally

[mmajerus6]

Currently, when searching in an SFM lookup field, there are (4) choices for search operators: Contains, Starts with, Ends with, and Exact Match. However the default search operator can only be set globally. For some of our lookups, Contains works well and is reasonably quick, but for other lookups where the results can be 10's or 100's of thousands of records, we need the search operator to be Exact Match. If the user accidentally forgets to change the operator from contains, the lookup just hangs and we have to refresh our browser tab.

We would like this setting to be configurable within each SFM lookup rather than at a global level in order to make the data entry efficient and drive adoption of the SFMs.

            

Lisa Mercer​ Anita D'Souza​ Brittany Taylor​

[Anita_Dsouza]

Thanks, Michael Majerus ! We can definitely look at supporting this in the new SFM Designer.

[lisa_mercer]

@Anita_Dsouza  @shivaranjini_g  Can we please get an update on this one?

Thanks!

[shivaranjini_g]

@mmajerus6 Admin's capability to set default search operator at SFM level has been enabled in the designer in ServiceMax core release 21.1. Now you can set the search operator for each lookup field added to the SFM page layout. If not set then global operator will take precedence.

This property will be respected on Web delivery.

[mmajerus6]

Thanks so much @shivaranjini_g for the update and also for the enhancement!

[elina_ristila]

@shivaranjini_g Great news! 

Planning to add this feature to Go app?

[shivaranjini_g]

Not immediately. @archana123 for GO