This control provides a nice UX to work with custom Microsoft Dataverse association (aka joint or many-to-many) tables on model-driven Power Apps (D365) forms.
There are several advantages to using custom Microsoft Dataverse tables to implement many-to-many relationships in Microsoft Dataverse. For more information and examples please read this post.
Data structure model for this control:
You can either take source code and embed it to your DevOps process (if planning to modify the control) or install a ready-to-use solution. You can find it in Releases Folder.
On the string (Single Text or Multiline Text) you can go to the Field Properties > Controls > Add Control.
| Parameter | Description | Example |
| Selector Table | Name for the Selector Table to show records to choose from in UI | crmvet_table2 |
| Selector Label | Logical Name for the Selector Table field to be used as a Label in UI for selector items | crmvet_uilabel |
| Association Table | Name for the Association Table (aka N:N Table) where joint/association records are stored | crmvet_table1_table2_association |
| Lookup to Associated Table | Schema Name of the lookup to the associated/target table in the joint/association table (N:N) | crmvet_Table2Id |
| Lookup to Current Table | Schema Name of the lookup to the current table in the joint/association table (N:N) | crmvet_Table1Id |
| Default Filter | Default Filter for Selector Table to define what records would be visible in UI | statuscode eq 1 |
| Visibility Toggle | Show or Hide in UI Selector Values. Useful if due to the number of options PCF takes too much space on a form | Yes/No |