Hi,
I am using two dataverse tables, Main Table and Child Table. In the Main Table I am using a lookup column, say Players, that refers to Child Table column and get values from there. I am displaying this Main Table in a form in Canvas App. With look up column in the form, I can allow multiple selection in the App for Players column, but the data stored in the Main Table for this look up column Players wont store multiple values, it only stores a single value though multiple values are selected in the app. It seems that look up column has this limitation or if there is anything I am missing !
I wanted to know if there is any other way we can do or design dataverse tables in a way that fits the above requirement.
I am using the Child Table because, I have to add or delete values, so the process becomes dynamic.
Thanks.
Hi @Saideep
As @skoofy5 outlined, you will need to create a many-to-many relationship. This might be helpful to understand how they work in canvas apps: https://youtu.be/L_WaeffrMcc?si=yqT2lgkYnUWXC9oj
You've got two choices:
Here's an old article that can talk you through it in a little more detail - https://carldesouza.com/understanding-intersect-entities-and-nn-relationships-in-dynamics-365/
Hi @MattB_Motive ,
Is there an alternate way of doing to achieve the above requirement.
All I need is a way to populate choice values in a combo box to allow multiple selection and all selected values should be stored in that column, and, the ability to dynamically add and delete the choice values.
Thanks.
Hi @Saideep
A lookup column in Dataverse creates a one-to-many relationship, so yes, by design you can only assign one record to the lookup column.
WarrenBelz
791
Most Valuable Professional
MS.Ragavendar
410
mmbr1606
275
Super User 2025 Season 1