Can we create multi select only for Data Reference page list ?

The requirement we are trying is,

I have created a embed pagelist and confgured in the view rule with default operations like Add/Edit/Delete

like below

We are storing below data inside workpage with embed list

Objective ID Objectives copied from Amount requirement ID
1 D-2 10000 D-1
2 D-1 9000 D-2
3 D-4 2000 D-3
4 D-2, D-3 1000 D-4

In the above table requirement ID column will have the unique value entered by the user while adding the record.

When user is adding new record to the table list, Objectives copied from this field should allow the user to select multiple options(multi select) source from the Requirement ID column values exist till now

So here, how can we achieve the multi select option for the Objectives copied from column, since the data is entered by the user is in the embed pagelist and not the datatype.

@SreenivasuluV16633502 the only out of the box solution is for single picklist, I’m sharing here because it isn’t well known and others may find this useful. This allows you to source a picklist from your embedded data BUT doesn’t not do multi-select

Data references are the only controls that do multi-select like this, so you would have to implement it this way. You can use the same data reference you have mentioned above, “Objectives”, but would need to create a specific data page that loads the embedded data from your existing case.

  • There are a number of ways to do this, early in my Constellation days I was using an OOTB data page, something like D_CaseDetails to load it, but that was very clunky
  • I believe you can use caseInfo.content to load the details from the redux store - you just have to be sure to make sure the embedded data is saved (e.g. via a prior step in a screenflow), you would have trouble doing this all in one form I think…

What is the business outcome?

Am curious on the business outcome here? Is it to manually copy objectives from one requirement to the next? If that is the case, maybe using something like the below could help? Break it up, into actions, then copying and loading data would be easier? Both for you as developer but also for end user (moving away from an “excel like” experience)