You’re offline. This is a read only version of the page.
Announcements
79
Hi Community,
I'm developing a model-driven app in Power Apps and have encountered a challenge with designing a user-friendly many-to-many relationship between two tables: Application and Condition.
Initially, I created a third table called "AppCond" to break down the many-to-many relationship into two one-to-many relationships.I then added a subgrid of AppCond to the Application form and filtered only related records. However, this approach requires users to open a separate form for the "AppCond" table to create new associations between Applications and Conditions, which can be inconvenient (Adding a new condition to an application does not happen directly in the subgrid).
Alternatively, I could have defined a direct many-to-many relationship between the Application and Condition tables, allowing users to add new conditions to an application directly from the subgrid on the application form. However, this approach poses another challenge: I wouldn't be able to extract the records from the automatically generated relationship (intersect) table in my cloud flow, as there is no way to list the rows of that table.
I need to use the data from the relationship table in my cloud flow, so I'm looking for a solution that balances user-friendliness and data accessibility.
Do you have any suggestions on how to design this many-to-many relationship in a way that allows users to easily associate conditions with applications while still being able to access the relationship data in my cloud flow?
Any ideas or best practices would be greatly appreciated. Thank you!
You are on the right track with AppCond table. Use the Quick Create form for creating records in the Subgrid. Here is a video by Lisa Crosbie on how to do it.
Share
Report
All responses (
Answers (
