Share
Report
60Hi,
I am trying to build an eform application in the form of Canvas app and store data in Dataverse. The application will collect input from users and include approval flow. I only have the experience on building Canvas app using Sharepoint lists as datasource in the default environment and in the past I would design lists like below:
| Checklist | |
| Column Name | Data Type |
| Question 1 | Choices |
| Question 2 | Choices |
| Question 3 | Rich Text |
| Applicant | Person |
| Reviewer | Person |
| Approver | Person |
In the above list, I can directly search Person in the column but in Dataverse table I can only create Lookup column and refer to User table(default table in Dataverse).
Recently I find that in Dataverse table relationships can be built within different tables so I start to think about how to design the data model of an application for better maintainance on the data. I suppose the tables will be like:
| Employee Information | |
| Column Name | Data Type |
| Full Name | Text |
| Title | Text |
| Organization | Text |
| Checklist | |
| Column Name | Data Type |
| Question 1 | Choices |
| Question 2 | Choices |
| Question 3 | Rich Text |
And I can build N:N relationship between these tables. Here are my questions:
1. Is it correct to design data model like this for my case?;
2. How to leverage table relationships in Canvas apps, for example, how to submit updates in a form control that will simultaneously update data in 2 different tables?
Categories:
I have the same question (0)
All responses (
Answers (
