You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: powerapps-docs/maker/model-driven-apps/model-driven-app-glossary.md
+33-29Lines changed: 33 additions & 29 deletions
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: Mattp123
6
6
ms.service: powerapps
7
7
ms.topic: overview
8
8
ms.component: model
9
-
ms.date: 07/20/2021
9
+
ms.date: 02/03/2022
10
10
ms.subservice: mda-maker
11
11
ms.author: matp
12
12
ms.reviewer: v-roryneary
@@ -30,7 +30,7 @@ Accessibility is a term that is used to refer to the extent to which people with
30
30
31
31
## Admin center
32
32
33
-
The Power Platform admin center is a unified portal for administrators to manage environments and settings for Power Apps, Power Automate, and Dynamics 365 apps. Power Platform admin center doesn't cover administration settings and features associated with Power BI.
33
+
The Power Platform admin center is a unified portal for administrators to manage environments and settings for Power Apps, [Power Automate](#power-automate), and [Dynamics 365](#dynamics-365) apps. Power Platform admin center doesn't cover administration settings and features associated with [Power BI](#power-bi).
34
34
35
35
[Learn more about the Power Platform admin center](/power-platform/admin/admin-documentation)
36
36
@@ -40,15 +40,15 @@ The Power Platform admin center is a unified portal for administrators to manage
40
40
41
41
The tool that is used to create and edit model-driven apps. As the modern app designer experience matures, it will replace the classic experience.
42
42
43
-
Use it to configure the navigation site map, tables, forms, and views relevant to your app.
43
+
Use it to configure the navigation [site map](#site-map), [tables](#table), [forms](#form), and [views](#view) relevant to your app.
44
44
45
45
[A preview of the new app designer experience](../../maker/model-driven-apps/app-designer-overview.md)
46
46
47
47
[We can use the classic app designer when we build or edit our apps](../../maker/model-driven-apps/build-first-model-driven-app.md)
48
48
49
49
## App navigation experience
50
50
51
-
The way in which areas, groups, and sub-groups are presented in a model-driven app. It is also known as the [site map](../model-driven-apps/model-driven-app-glossary.md#site-map)
51
+
The way in which [areas](#area), [groups](#group), and [subarea](#subarea) are presented in a model-driven app. It is also known as the [site map](../model-driven-apps/model-driven-app-glossary.md#site-map)
52
52
53
53
## Application lifecycle management
54
54
@@ -62,11 +62,15 @@ The way in which we manage the lifecycle of an application from conception to en
62
62
63
63
[App navigation in model-driven apps](app-navigation.md)
64
64
65
+
## Attribute
66
+
67
+
An attribute is another name for a [column](#column) and is a term commonly used by Power Apps developers. Each [table](#table) in Power Apps corresponds to a database table and each table column in Power Apps corresponds to a column in the database table.
68
+
65
69
## Business process flow
66
70
67
71
Logic built into a given table to ensure that users complete records by updating fields in the correct order.
68
72
69
-
While these are authored initially using the Power Automate experience, business process flows are experienced within model-driven app as a change in the user interface.
73
+
While these are authored initially using the [Power Automate](#power-automate) experience, business process flows are experienced within model-driven app as a change in the user interface.
70
74
71
75
A business process flow is arranged into stages. Each stage defines the columns (fields) that must be completed typically before moving on to the next stage. For example, the default business process flow for the opportunity table has four stages: qualify > develop > propose > close. The current stage in a business process flow is indicated with a dot next to the stage in the sequence of stages from left to right in the flow.
72
76
@@ -100,25 +104,25 @@ A visual representation of a table of data. These can take the form of line, bar
100
104
101
105
## Classic
102
106
103
-
The classic interface represents the method in which app makers make changes to features within their Microsoft Dataverse environment.
107
+
The classic interface represents the method in which app makers make changes to features within their Microsoft [Dataverse](#dataverse) environment.
104
108
105
109
The classic interface has been replaced over time by the web-based method of app authoring known as the unified interface.
106
110
107
111
[About Unified Interface for model-driven apps in Power Apps](/power-platform/admin/about-unified-interface)
108
112
109
113
## Classic app designer
110
114
111
-
The modern app designer lets you create model-driven apps and create canvas apps using custom pages.
115
+
The modern app designer lets you create model-driven apps and create [canvas apps](#canvas-app) using custom pages.
112
116
113
117
The modern app designer will soon be the default designer for model-driven apps. Currently, you can still create model-driven apps using the classic app designer.
114
118
115
119
## Column
116
120
117
-
A field within a Dataverse table (formerly called an entity). Columns are similar to fields in databases and have different data types such as text, number, date, as well as data types less familiar to databases such as phone, email, file, and image.
121
+
A column (formerly called a field), is a field within a Dataverse table (formerly called an entity). Columns are similar to fields in databases and have different data types such as text, number, date, as well as data types less familiar to databases such as phone, email, file, and image.
118
122
119
-
The field type defines the kind of data required by the column and also the controls, such as date picker or text box, that will be available when using the control.
123
+
The column type defines the kind of data required by the column and also the controls, such as date picker or text box, that will be available when using the control.
120
124
121
-
Columns also appear when creating forms. Form tabs also have columns, and this defines where you can put sections. Additionally, form sections have columns, and these define where you can place table columns (fields in this case).
125
+
Columns also appear when creating forms. Form tabs also have columns, and this defines where you can put sections. Additionally, form sections have columns, and these define where you can place table columns (form fields in this case).
122
126
123
127
[How to create and edit columns](../../maker/data-platform/create-edit-fields.md)
124
128
@@ -144,7 +148,7 @@ Components can be split into data (tables, relationships, columns) UI (site map,
144
148
145
149
A model-driven app is only connected to the data tables that reside in the same environment. This connection can be considered native because it never has to be set up within the environment.
146
150
147
-
Connections exist within the environment to enable other elements of the Power Platform to operate correctly. Notably, Power Apps canvas apps and Power Automateflows have the ability to make use of multiple connections.
151
+
Connections exist within the environment to enable other elements of the Power Platform to operate correctly. Notably, Power Apps [canvas apps](#canvas-app) and [Power Automate](#power-automate)[flows](#flow) have the ability to make use of multiple connections.
148
152
149
153
## Control
150
154
@@ -164,27 +168,27 @@ A dashboard allows charts, Power BI reports, and views of tables to be presented
164
168
165
169
## Data model
166
170
167
-
A collection of related [tables](model-driven-app-glossary.md#table). In the context of model-driven apps, these are held within the Dataverse database.
171
+
A collection of related [tables](model-driven-app-glossary.md#table). In the context of model-driven apps, these are held within the [Dataverse](#dataverse) database.
168
172
169
173
In a custom [solution](model-driven-app-glossary.md#solution), the data model is often the set of related tables built with the purpose of delivering the overall business application.
170
174
171
175
## Database
172
176
173
-
The collective term for all the tables in Dataverse.
177
+
The collective term for all the tables in [Dataverse](#dataverse).
174
178
175
179
## Dataverse
176
180
177
-
Microsoft Dataverse is the collective term for the tables, workflows, business process flows, and related functionality that are provisioned within an environment when a database is created.
181
+
Microsoft Dataverse is the collective term for the [tables](#table), [workflows](#workflow), [business process flows](#business-process-flow), and related functionality that are provisioned within an environment when a database is created.
178
182
179
183
Model-driven apps require a Dataverse database.
180
184
181
-
A Dataverse database contains data structures most closely associated with databases in addition to being able to hold model-driven apps, canvas apps, and power automateflows.
185
+
A Dataverse database contains data structures most closely associated with databases in addition to being able to hold model-driven apps, [canvas apps](#canvas-app), and [Power Automate](#power-automate)[flows](#flow).
182
186
183
187
[Find out more about Dataverse here](../../maker/data-platform/data-platform-intro.md)
184
188
185
189
## Dependency
186
190
187
-
Dependencies are created when elements of components are reliant on each other for them to work. For example, if a column is used within a view then the view requires the column to exist for it to be able to function. There are many examples of dependencies throughout Dataverse. Another example is a model-driven app being dependent on a table if that table is used within the app.
191
+
Dependencies are created when elements of components are reliant on each other for them to work. For example, if a column is used within a view then the view requires the column to exist for it to be able to function. There are many examples of dependencies throughout [Dataverse](#dataverse). Another example is a model-driven app being dependent on a table if that table is used within the app.
188
192
189
193
Dependencies manifest themselves in numerous ways including when a model-driven app is validated. They also become apparent in the most problematic fashion when trying to delete an aspect of a table, form, view or dashboard. When this occurs, the dependencies can be viewed by selecting the item to be deleted, and then selecting "show dependencies" on the command bar.
190
194
@@ -208,7 +212,7 @@ An environment is a space to store, manage, and share your organization's busine
208
212
209
213
You can package up the various elements as solutions, and these solutions can be exported from one environment to another.
210
214
211
-
An environment can only ever have one Dataverse database and all your model-driven apps in the environment use this database.
215
+
An environment can only ever have one [Dataverse](#dataverse) database and all your model-driven apps in the environment use this database.
212
216
213
217
Often multiple environments are used to enable application lifecycle management. For example you might have development, test, and production environments.
214
218
@@ -218,7 +222,7 @@ Environments exist within a geographical region and can be a means of ensuring t
218
222
219
223
## Flow
220
224
221
-
Cloud flows are functionality offered by Power Automate that allow automation of tasks to take place based upon triggering of conditions such as recurrence, adding or updating of records or simply selection of buttons by users. Flows can be run with or without the introduction of new parameters.
225
+
Cloud flows are functionality offered by [Power Automate](#power-automate) that allow automation of tasks to take place based upon triggering of conditions such as recurrence, adding or updating of records or simply selection of buttons by users. Flows can be run with or without the introduction of new parameters.
@@ -252,7 +256,7 @@ This refers to features that have either been deprecated, or the way in which th
252
256
253
257
## Lookup
254
258
255
-
A lookup is a field type that exists when two tables are related. Lookups can be seen in table views on the many side of a one-to-many relationship. They are generally populated using a form on the many side of the relationship.
259
+
A lookup is a field type that exists when two tables are related. Lookups can be seen in table views on the many side of a [one-to-many relationship](#relationship). They are generally populated using a form on the many side of the relationship.
256
260
257
261
-[Learn more about the lookup field user experience](../../user/lookup-field.md)
258
262
-[How to configure a lookup](../../maker/model-driven-apps/form-designer-add-configure-lookup.md)
@@ -265,7 +269,7 @@ Every table has at least one main form. The main form represents the primary met
265
269
266
270
## Monitor
267
271
268
-
Also know as the app monitor. It lets you understand aspects of the performance of a model-driven app. App monitor can an also be used to monitor canvas apps.
272
+
Also know as the app monitor. It lets you understand aspects of the performance of a model-driven app. App monitor can an also be used to monitor [canvas apps](#canvas-app).
269
273
270
274
-[Learn how to use the app monitor](../../maker/monitor-modelapps.md)
271
275
-[Use Monitor to understand form performance](monitor-form-checker.md)
@@ -274,7 +278,7 @@ Also know as the app monitor. It lets you understand aspects of the performance
274
278
275
279
Modern apps have the concept of pages, which can be either model-driven apps or a canvas-based page using a custom pages. Custom pages allow flexible layout, low-code Power Fx functions, and Power Apps connector data.
276
280
277
-
It is a tool for enabling model-driven apps and canvas apps to exist together.
281
+
It is a tool for enabling model-driven apps and [canvas apps](#canvas-app) to exist together.
278
282
279
283
-[Working with custom pages](model-app-page-overview.md)
280
284
-[Learn about creating modern apps](app-designer-overview.md)
@@ -285,15 +289,15 @@ A Power Platform service that allows users to streamline repetitive tasks. Typic
285
289
286
290
Model-driven app [business process flows](model-driven-app-glossary.md#business-process-flow) that direct users to complete table records in a specific fashion, are authored within Power Automate.
287
291
288
-
Power Automate flows exist within an environment and can also exist within Power Apps [solutions](model-driven-app-glossary.md#solution).
292
+
[Power Automate flows](#flow) exist within an environment and can also exist within Power Apps [solutions](model-driven-app-glossary.md#solution).
289
293
290
294
[Learn more about Power Automate](/power-automate/getting-started)
291
295
292
296
## Power BI
293
297
294
-
A data visualization tool that has the capacity to be embedded within model-driven apps or to live completely independently of them. Power BI can connect to a very wide range of data sources, of which Dataverse is just one.
298
+
A data visualization tool that has the capacity to be embedded within model-driven apps or to live completely independently of them. Power BI can connect to a very wide range of data sources, of which [Dataverse](#dataverse) is just one.
295
299
296
-
Power BI Reports don't exist within Dataverse environments or inside solutions.
300
+
Power BI Reports don't exist within [Dataverse](#dataverse) environments or inside solutions.
297
301
298
302
-[Use Power BI within a model driven app](use-power-bi.md)
299
303
-[Learn more about Power BI](/power-bi/fundamentals/power-bi-overview)
@@ -310,7 +314,7 @@ Every solution has a publisher. You specify the publisher when you create a solu
310
314
311
315
## Record
312
316
313
-
A record contains one or more columns of information about a person, a place, or a thing. For example, a record might contain the name, the email address, and the phone number of a single customer. Other tools refer to a record as a "row" or an "item". Records exist within Dataverse tables.
317
+
A record contains one or more columns of information about a person, a place, or a thing. For example, a record might contain the name, the email address, and the phone number of a single customer. Other tools refer to a record as a "row" or an "item". Records exist within [Dataverse](#dataverse) tables.
314
318
315
319
## Relationship
316
320
@@ -395,7 +399,7 @@ Subareas (tables) and pages appear under the group that they're configured withi
395
399
396
400
## Subgrid
397
401
398
-
Subgrids are areas of main forms that display a list of records from a Dataverse table, while remaining on the form. Typically, a subgrid is used to display child records that relate to the parent record currently under review. For example, books written by an author.
402
+
Subgrids are areas of main forms that display a list of records from a [Dataverse](#dataverse) table, while remaining on the form. Typically, a subgrid is used to display child records that relate to the parent record currently under review. For example, books written by an author.
399
403
400
404
While subgrids are displayed in a model-driven app, they are a property of the form.
401
405
@@ -412,7 +416,7 @@ From a site map perspective a tab is a "group" when using the site map designer
412
416
413
417
## Table
414
418
415
-
A table is a method of storing data in columns (or fields) within Dataverse. Tables where formerly called [entities](model-driven-app-glossary.md#entity).
419
+
A table is a method of storing data in columns (or fields) within [Dataverse](#dataverse). Tables where formerly called [entities](model-driven-app-glossary.md#entity).
416
420
417
421
Tables, in the context of model-driven apps, only exist within a [Dataverse](model-driven-app-glossary.md#dataverse) database.
418
422
@@ -450,7 +454,7 @@ The process by which an app maker confirms if the model-driven app has all the c
450
454
451
455
## View
452
456
453
-
A tabular representation of records in a Dataverse table. Tables can have multiple views.
457
+
A tabular representation of records in a [Dataverse](#dataverse) table. Tables can have multiple views.
454
458
455
459
Views can be pre-filtered and it is possible to define the specific views that a model-driven app will make available to users.
456
460
@@ -462,6 +466,6 @@ Tables can have multiple views associated with them and you can define the table
462
466
463
467
A classic workflow is a series of functions or methods, called steps, that are performed sequentially and apply to data contained within tables. The workflow can change the processing direction by using conditionals, referred to as conditional branches.
464
468
465
-
In many cases classic workflows should be replaced by Power Automateflows.
469
+
In many cases classic workflows should be replaced by [Power Automate](#power-automate)[flows](#flow).
0 commit comments