Skip to content

Commit 4d4dbdb

Browse files
authored
Live publish
2 parents 68bb9a4 + 09f65d2 commit 4d4dbdb

File tree

3 files changed

+39
-34
lines changed

3 files changed

+39
-34
lines changed

powerapps-docs/developer/data-platform/tools/devtools-install.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,6 +81,7 @@ You can find a few Power Platform Tools options in Visual Studio by choosing **T
8181

8282
### See Also
8383

84-
[Quickstart: Create a Power Platform Tools project](devtools-create-project.md)
84+
[Quickstart: Create a Power Platform Tools project](devtools-create-project.md)
85+
[Power Platform Tools on the Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=microsoft-IsvExpTools.PowerPlatformTools)
8586

8687
[!INCLUDE[footer-include](../../../includes/footer-banner.md)]

powerapps-docs/maker/TOC.yml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1965,7 +1965,7 @@
19651965
items:
19661966
- name: Portals Web API overview
19671967
href: ./portals/web-api-overview.md
1968-
- name: Perform Read operations (preview)
1968+
- name: Perform Read operations
19691969
displayName: Portals Web API read operations
19701970
href: ./portals/read-operations.md
19711971
- name: Perform Write, Update, Delete operations
@@ -1977,7 +1977,7 @@
19771977
- name: "Tutorial: Use the portals Web API"
19781978
displayName: Tutorial on how to use the portal Web API
19791979
href: ./portals/webapi-tutorial.md
1980-
- name: Code components (preview)
1980+
- name: Code components
19811981
items:
19821982
- name: Overview of code components in portals
19831983
href: ./portals/component-framework.md
@@ -2127,6 +2127,8 @@
21272127
href: ./data-platform/create-custom-entity.md
21282128
- name: Edit a table
21292129
href: ./data-platform/edit-entities.md
2130+
- name: Import or export data
2131+
href: ./data-platform/data-platform-import-export.md
21302132
- name: Create and edit virtual tables
21312133
href: ./data-platform/create-edit-virtual-entities.md
21322134
- name: Virtual table OData v4 data provider
@@ -2141,8 +2143,6 @@
21412143
href: ./data-platform/create-edit-entities-portal.md
21422144
- name: How to create tables using solution explorer
21432145
href: ./data-platform/create-edit-entities-solution-explorer.md
2144-
- name: How to import or export data
2145-
href: ./data-platform/data-platform-import-export.md
21462146
- name: How to open table data in Excel
21472147
href: ./data-platform/data-platform-excel-addin.md
21482148
- name: How to define alternate keys

powerapps-docs/maker/model-driven-apps/model-driven-app-glossary.md

Lines changed: 33 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: Mattp123
66
ms.service: powerapps
77
ms.topic: overview
88
ms.component: model
9-
ms.date: 07/20/2021
9+
ms.date: 02/03/2022
1010
ms.subservice: mda-maker
1111
ms.author: matp
1212
ms.reviewer: v-roryneary
@@ -30,7 +30,7 @@ Accessibility is a term that is used to refer to the extent to which people with
3030

3131
## Admin center
3232

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).
3434

3535
[Learn more about the Power Platform admin center](/power-platform/admin/admin-documentation)
3636

@@ -40,15 +40,15 @@ The Power Platform admin center is a unified portal for administrators to manage
4040

4141
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.
4242

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.
4444

4545
[A preview of the new app designer experience](../../maker/model-driven-apps/app-designer-overview.md)
4646

4747
[We can use the classic app designer when we build or edit our apps](../../maker/model-driven-apps/build-first-model-driven-app.md)
4848

4949
## App navigation experience
5050

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)
5252

5353
## Application lifecycle management
5454

@@ -62,11 +62,15 @@ The way in which we manage the lifecycle of an application from conception to en
6262

6363
[App navigation in model-driven apps](app-navigation.md)
6464

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+
6569
## Business process flow
6670

6771
Logic built into a given table to ensure that users complete records by updating fields in the correct order.
6872

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.
7074

7175
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.
7276

@@ -100,25 +104,25 @@ A visual representation of a table of data. These can take the form of line, bar
100104

101105
## Classic
102106

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.
104108

105109
The classic interface has been replaced over time by the web-based method of app authoring known as the unified interface.
106110

107111
[About Unified Interface for model-driven apps in Power Apps](/power-platform/admin/about-unified-interface)
108112

109113
## Classic app designer
110114

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.
112116

113117
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.
114118

115119
## Column
116120

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.
118122

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.
120124

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).
122126

123127
[How to create and edit columns](../../maker/data-platform/create-edit-fields.md)
124128

@@ -144,7 +148,7 @@ Components can be split into data (tables, relationships, columns) UI (site map,
144148

145149
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.
146150

147-
Connections exist within the environment to enable other elements of the Power Platform to operate correctly. Notably, Power Apps canvas apps and Power Automate flows 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.
148152

149153
## Control
150154

@@ -164,27 +168,27 @@ A dashboard allows charts, Power BI reports, and views of tables to be presented
164168

165169
## Data model
166170

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.
168172

169173
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.
170174

171175
## Database
172176

173-
The collective term for all the tables in Dataverse.
177+
The collective term for all the tables in [Dataverse](#dataverse).
174178

175179
## Dataverse
176180

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.
178182

179183
Model-driven apps require a Dataverse database.
180184

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 automate flows.
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).
182186

183187
[Find out more about Dataverse here](../../maker/data-platform/data-platform-intro.md)
184188

185189
## Dependency
186190

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.
188192

189193
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.
190194

@@ -208,7 +212,7 @@ An environment is a space to store, manage, and share your organization's busine
208212

209213
You can package up the various elements as solutions, and these solutions can be exported from one environment to another.
210214

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.
212216

213217
Often multiple environments are used to enable application lifecycle management. For example you might have development, test, and production environments.
214218

@@ -218,7 +222,7 @@ Environments exist within a geographical region and can be a means of ensuring t
218222

219223
## Flow
220224

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.
222226

223227
[Cloud flows](/power-automate/flow-types#cloud-flows)
224228

@@ -252,7 +256,7 @@ This refers to features that have either been deprecated, or the way in which th
252256

253257
## Lookup
254258

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.
256260

257261
- [Learn more about the lookup field user experience](../../user/lookup-field.md)
258262
- [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
265269

266270
## Monitor
267271

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).
269273

270274
- [Learn how to use the app monitor](../../maker/monitor-modelapps.md)
271275
- [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
274278

275279
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.
276280

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.
278282

279283
- [Working with custom pages](model-app-page-overview.md)
280284
- [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
285289

286290
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.
287291

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).
289293

290294
[Learn more about Power Automate](/power-automate/getting-started)
291295

292296
## Power BI
293297

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.
295299

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.
297301

298302
- [Use Power BI within a model driven app](use-power-bi.md)
299303
- [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
310314

311315
## Record
312316

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.
314318

315319
## Relationship
316320

@@ -395,7 +399,7 @@ Subareas (tables) and pages appear under the group that they're configured withi
395399

396400
## Subgrid
397401

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.
399403

400404
While subgrids are displayed in a model-driven app, they are a property of the form.
401405

@@ -412,7 +416,7 @@ From a site map perspective a tab is a "group" when using the site map designer
412416

413417
## Table
414418

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).
416420

417421
Tables, in the context of model-driven apps, only exist within a [Dataverse](model-driven-app-glossary.md#dataverse) database.
418422

@@ -450,7 +454,7 @@ The process by which an app maker confirms if the model-driven app has all the c
450454

451455
## View
452456

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.
454458

455459
Views can be pre-filtered and it is possible to define the specific views that a model-driven app will make available to users.
456460

@@ -462,6 +466,6 @@ Tables can have multiple views associated with them and you can define the table
462466

463467
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.
464468

465-
In many cases classic workflows should be replaced by Power Automate flows.
469+
In many cases classic workflows should be replaced by [Power Automate](#power-automate) [flows](#flow).
466470

467471
[!INCLUDE[footer-include](../../includes/footer-banner.md)]

0 commit comments

Comments
 (0)