I am struggling to understand the correct design pattern to use in PowerApps to approach forms where a many to many relationship exists.
In my attached image I have depicted the classic many to many relationship between SQL tables. I understand how to build the relationships and associated views to render galleries in PowerApps. The part I am having trouble with is how to provision a form/control so a user can perform the following basic tasks:
•Show current values associated with Goal ID 1.
•Provision choices to add/remove associated items.
•Update the bridge table with the user's changes.
Because this would be a relatively common scenario, I want to be sure my approach makes sense before repeating it.
Some basic questions I am having:
- Should I use the built-in edit forms or abandon these altogether? I like the ease with which the regular table fields are provisioned but for this situation the edit form fields will obviously not work.
- Should I somehow use a list box to show the current choices associated with the current item, allowing the user to add or remove from the list box and then try to commit the list box back to the bridge table as a way to update?
- Is there maybe another way of looking at this entirely that is simpler and more straight-forward?
- Is a normalized table structure simply not supported/recommended?
I really appreciate the expertise of those on this board who have been farther down this road... At the moment I just can't seem to get my mind around how this should work yet it is such a common scenario if using SQL tables as a source.