| Tables (Entities) are an item with properties that you track. | They contain rows and columns of data and are stored within the Dataverse database for your environment. They can have relationships with other tables. Tables also store other items such as forms, views, business rules, and charts. You access these tables from make.powerapps.com under the Data heading and then Tables. |
| Relationships define how two tables are related to each other. | Within the table, there is a Relationships tab where you can add a custom relationship. You can define one-to-many or many-to-one relationships. |
| Columns (Fields). Data in table are stored within Columns. | Each column has a data type such as text, whole number, currency, choice, etc. Columns have both a display name and an internal name (which will have your publisher prefix if you create new columns). Every table needs a primary name column which is the field that gets a hyperlink to click on to bring up the details form. The system creates a unique ID field for you. Columns can also be calculated or rollup values if you are working with number columns, for example, you could have a calculated column for cost variance that would subtract the projected cost from the budget cost. A lookup column can be created where you lookup values from another table. For example, you could have a Project Sponsor field that do a lookup of the built-in Users table. Each column has a Description area which can be useful to provide tooltips to users on a form on what kind of information is desired to be filled out. |
| Choice Fields (Option Sets) give the user a predetermined list of options. | Each option has a label and numeric value. The numeric value is set automatically and is only visible at the moment from the Classic Editor. Sometimes this numeric value is needed if using in within code or using a Power Automate flow. There is a separate data type to allow multiple items to be selected called Choices. There is no ability for the user to add their own value so you might want to include an option for None or Not Applicable. Choice fields can be either global or local. A global choice option can be used by a column in any table. A local choice field can only be used by that column where you created it from. Important: It is best to determine if this choice can be used across columns and if so, create it first as a global choice field. If you delete a choice, all existing items with that choice revert to a blank. If you rename a choice value, all existing items with that choice will change to the renamed value. |
Disclaimer: The instructional video contained herein is an excerpt from a recorded live virtual instructor-led training session. Some images contained therein may appear different from (or not available) in your organization’s Sensei IQ instance due to specific custom configurations and/or continuous solution updates. Ensure that you are already an enabled user in the Sensei.IQ for Project application and check out the What’s New page. Contact your system administrator for any assistance.