Hi @srosenbloom,
Is there a reason you can't just add a one to many relationship to your table and a subgrid on your form, allowing you to associate multiple clients with a particular record?
For your clients scenario, I would strongly not recommended using a Choice(s) column in these scenarios:
- The list is long (more than 20-30)
- The list of items can change occasionally/frequently
- You need to apply security to control which items can be seen by different users
- You need to store additional attributes (columns) about the items
Especially for something like clients, you should be using the out of box Account or Contact table. A Choices (multi-select) column in particular has many other limitations beyond a regular Choice field. It can't be used for:
- Business rules
- Dataverse workflows
- charts
- Reports
- Rollup and calculated fields
- Others..
---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.
