Studio web - edit grid - Update entity using multi select

Hi All,

in my studio web app (not VB app), I want to use a multi select dropdown within an edit grid. I want to safe the result into my entity.

When I add Controls.Solutions.Loesungen.SelectedItem.MyEntityField.ToList() as variable the result is not saved in my entity. I have tried to save it into a text field in the entity and into a choice set.

How can I do it?

Thank you!

Hi @PeCour

To save multiple selections, change .SelectedItem to .SelectedItems. Because a multi-select dropdown outputs an array, it cannot bind directly to a text field or Choice Set. Instead, go to the Edit Grid’s Row Modified event and convert the array into text using the expression =String.Join(", ", Controls.Solutions.Loesungen.SelectedItems).

Cheers

Hi @bhavesh.choubey1,
thank you but this is a VB.NET App formula. “SelectedItems” is not available in Studio Web Apps.

Error: SelectedItems not member of EditGridControl

Hi @PeCour

Use the grid row value directly instead:
Controls.EditGrid.SelectedRow.MyEntityField

For a multi Select dropdown inside an Edit Grid, bind the column directly to:

  • Entity field type =Choice Set (Multiple)
    Or List(Of String)

Do Bind the grid column directly to a multi-choice entity field and save the row/entity, not the control value.

Happy Automation

yes you’re right,

now go to your Edit Grid’s Row Modified event. In your update/save rules mapping to your entity text field, write the following expression using the local event context variable

=String.Join(", ", EditGrid.NewItem.MyEntityField)

Cheers

@PeCour

Can you please show how you are trying to save..as in new apps you ahve to write flow for everything that you need..and the flow for this needs to be created msotly in row modified

cheers

@Anil_G with the help of @ppr I have advanced and found out how to bind the coice set but there is still one open point that I am investigating.

I have created a choice set: PASoftwareanwendungen.
I bind it to the “Multi select” edit mode
List source: {new PASoftwareanwendungen().Excel, new PASoftwareanwendungen().App}.ToList()
Column: nothing (I have tried “Name” → no results found"
Flow: Controls.Solution_Fixed.EditGrid.SelectedItem.Software.ToList()

Result:
It works. It writes back the selected choice into the entity.

Open issue:
Choice set: It shows the number of the selection and not the name or displayname “Excel” etc.

in the past, we had options like getChoiceSet(“ChoiceSetName”). But Studio Web Apps do not support a few well-known Functions, we had used on VB.Apps.

Maybe Integration Service to Datafabric can help. Otherwise the Datatype: PASoftwareanwendungen should be investigated more in detail. Maybe populating the dropdown with a Dictionary can also help as workaround.

Additional we also suggest to have a closer look on the functionality of Grid-edit and a ChoiceSet column in detail. Maybe not offered but expected: the edit Ui should indicate for the editing row: which choice option(s) is defined for the row and which other unused choice-options are available

I have contacted UiPath support and see below the answer. It is a known limitation. Below is a possible workaround:

I wanted to share an update on the behavior you’re seeing with GetChoiceSet in your Studio Web app. After confirming with our official documentation, this is a known and documented limitation of Studio Web Apps rather than an issue specific to your configuration.

Per UiPath’s Studio Web “Known Limitations” documentation, Studio Web app projects currently do not support entity choice sets, along with the GetChoiceSet and GetChoiceSetValue functions. The same limitation applies to the Fetch and FetchOne functions, and to the Query Builder as a whole.

The recommended approach in Studio Web is to use a Query Entity Record automation within your workflow instead of relying on these functions. You can then bind your dropdown or list control to the output of that automation.

For your reference: https://docs.uipath.com/studio-web/automation-suite/2.2510/user-guide/known-limitations#known-limitations