pickerFieldCustom: selected value is getting replace with identifiers value

The labels for the selected items are defined by the "selectedLabels" parameter.

Example: https://docs.appian.com/suite/help/25.2/recipe-configure-an-array-picker.html

thanks Stefan Helzle  for your prompt response. 

the expression rule is taking user input and doing a DB query which return back list of user and id like below :

sample data:{gaurav, Stefan},
identifiers: {1,2}

when user select gaurav ,pickerFieldCustom  is changing "gaurav" to 1 , that is the problem. 
please can you share a sample example if you have any. i checked your site also (appian rocks) but unable to get a solution. 

Thanks for your help.

i checked this  pickerFieldCustom: selected value is NOT staying also but unable to understand the data is in local!questiondetails object 
 

also in this example https://docs.appian.com/suite/help/25.2/recipe-configure-an-array-picker.html

it is a client side filtering where system is getting data before user entry , i am looking a server side filter 

Note from https://docs.appian.com/suite/help/24.2/Custom_Picker_Component.html 
If you are trying to decide whether to use a dropdown with search or a picker component, keep in mind that the dropdown search runs client-side and the performance cost of loading options happens on initial load whereas the picker search runs server-side and the performance cost of loading options happens while the user is searching. For small sets of options, we recommend using the dropdown component

Hi gauravp915957 ,

In pickerFieldCustom, there's a parameter called selectedLabels (a list of text strings) that accepts an array of labels corresponding to the currently selected items.

To populate this, you'll need to run an additional query using the selected item IDs as a filter to fetch their corresponding labels, and then pass those to the selectedLabels parameter.

This approach is also outlined in the recipe shared by Stefan. However, note that the recipe uses static data—you’ll need to implement a dynamic query that refreshes on every value change.

The data in this local comes from the same table that the picker is working with—it's simply filtered based on the selected items in the picker.

You can call a query on your data source by applying a filter on the primary key using the values from selectedValue (i.e., the selected items from the picker). This will return the list of corresponding records, which you can then use to display the selected labels in your custom picker.