Skip to content

Commit 292b6bb

Browse files
authored
Live publish
2 parents a5e07fb + 2b007c1 commit 292b6bb

File tree

170 files changed

+455
-373
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

170 files changed

+455
-373
lines changed

powerapps-docs/developer/component-framework/implementing-controls-using-typescript.md

Lines changed: 78 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -76,10 +76,6 @@ To create a new project:
7676
> [!NOTE]
7777
> If you receive the error `The term 'npm' is not recognized as the name of a cmdlet, function, script file, or operable program.`, make sure you have installed [node.js](https://nodejs.org/en/download/) (LTS version is recommended) and all other prerequisites.
7878
79-
1. After npm install, you will need to generate ManifestDesignTypes.d.ts file in this directory using the below command."
80-
```
81-
npm run refreshTypes
82-
```
8379

8480

8581
## Implementing manifest
@@ -98,56 +94,100 @@ Make changes to the predefined manifest file, as shown here:
9894
- **control-type**: The code component type. Only *standard* types of code components are supported.
9995

10096
```XML
101-
<?xml version="1.0" encoding="utf-8" ?>
102-
<manifest>
103-
<control namespace="SampleNamespace" constructor="LinearInputControl" version="1.1.0" display-name-key="LinearInputControl_Display_Key" description-key="LinearInputControl_Desc_Key" control-type="standard">
97+
<?xml version="1.0" encoding="utf-8" ?>
98+
<manifest>
99+
<control namespace="SampleNamespace"
100+
constructor="LinearInputControl"
101+
version="1.1.0"
102+
display-name-key="LinearInputControl_Display_Key"
103+
description-key="LinearInputControl_Desc_Key"
104+
control-type="standard">
105+
<!-- TODO: Add type-group, property, and resources elements here -->
106+
</control>
107+
</manifest>
108+
```
109+
110+
1. Add the definition of a [type-group](manifest-schema-reference/type-group.md) element named `numbers` in the `control` element. This element specifies the component value and can contain whole, currency, floating point, or decimal values.
111+
112+
```XML
113+
<type-group name="numbers">
114+
<type>Whole.None</type>
115+
<type>Currency</type>
116+
<type>FP</type>
117+
<type>Decimal</type>
118+
</type-group>
104119
```
105120

106-
2. The [property](manifest-schema-reference/property.md) node defines the properties of the code component like defining the data type of the column. The property node is specified as the child element under the `control` element. Define the [property](manifest-schema-reference/property.md) node as shown here:
121+
1. Add the [property](manifest-schema-reference/property.md) element within the `control` element. This element defines the properties of the code component like defining the data type of the column. Define the [property](manifest-schema-reference/property.md) node as shown here:
107122

108123
- **name**: Name of the property.
109124
- **display-name-key**: Display name of the property that is displayed on the UI.
110-
- **description-name-key**: Description of the property that is displayed on the UI.
111-
- **of-type-group**: The [of-type-group](manifest-schema-reference/type-group.md) is used when you want to have more than two data type columns. Add the [of-type-group](manifest-schema-reference/type-group.md) element as a sibling to the `property` element in the manifest. The `of-type-group` specifies the component value and can contain whole, currency, floating point, or decimal values.
125+
- **description-name-key**: Description of the property that is displayed on the UI.
126+
- **of-type-group**: Use the `of-type-group` attribute when you want refer to the name of a specific type group. Here, we are referring to the `type-group` named `numbers` created in the previous step.
112127
- **usage**: Has two properties, *bound* and *input*. Bound properties are bound only to the value of the column. Input properties are either bound to a column or allow a static value.
113128
- **required**: Defines whether the property is required.
114129

115130
```XML
116-
<property name="controlValue" display-name-key="controlValue_Display_Key" description-key="controlValue_Desc_Key" of-type-group="numbers" usage="bound" required="true" />
131+
<property name="controlValue"
132+
display-name-key="controlValue_Display_Key"
133+
description-key="controlValue_Desc_Key"
134+
of-type-group="numbers"
135+
usage="bound"
136+
required="true" />
117137
```
118138

119-
3. The [resources](manifest-schema-reference/resources.md) node defines the visualization of the code component. It contains all the resources that build the visualization and styling of the code component. The [code](manifest-schema-reference/code.md) is specified as a child element under the resources element. Define the [resources](manifest-schema-reference/resources.md) as shown here:
139+
1. The [resources](manifest-schema-reference/resources.md) node defines the visualization of the code component. It contains all the resources that build the visualization and styling of the code component. The [code](manifest-schema-reference/code.md) is specified as a child element under the resources element. Define the [resources](manifest-schema-reference/resources.md) as shown here:
120140

121141
- **code**: Refers to the path where all the resource files are located.
122142

123143
```XML
124144
<resources>
125-
<code path="index.ts" order="1" />
126-
<css path="css/LinearInputControl.css" order="1" />
145+
<code path="index.ts"
146+
order="1" />
147+
<css path="css/LinearInputControl.css"
148+
order="1" />
127149
</resources>
128150
```
129-
The overall manifest file should look something like this:
151+
152+
The completed manifest file should look like this:
130153

131154
```XML
132-
<?xml version="1.0" encoding="utf-8" ?>
133-
<manifest>
134-
<control namespace="SampleNamespace" constructor="LinearInputControl" version="1.1.0" display-name-key="LinearInputControl_Display_Key" description-key="LinearInputControl_Desc_Key" control-type="standard">
135-
<type-group name="numbers">
136-
<type>Whole.None</type>
137-
<type>Currency</type>
138-
<type>FP</type>
139-
<type>Decimal</type>
140-
</type-group>
141-
<property name="controlValue" display-name-key="controlValue_Display_Key" description-key="controlValue_Desc_Key" of-type-group="numbers" usage="bound" required="true" />
142-
<resources>
143-
<code path="index.ts" order="1" />
144-
<css path="css/LinearInputControl.css" order="1" />
145-
</resources>
146-
</control>
147-
</manifest>
155+
<?xml version="1.0" encoding="utf-8" ?>
156+
<manifest>
157+
<control namespace="SampleNamespace"
158+
constructor="LinearInputControl"
159+
version="1.1.0"
160+
display-name-key="LinearInputControl_Display_Key"
161+
description-key="LinearInputControl_Desc_Key"
162+
control-type="standard">
163+
<type-group name="numbers">
164+
<type>Whole.None</type>
165+
<type>Currency</type>
166+
<type>FP</type>
167+
<type>Decimal</type>
168+
</type-group>
169+
<property name="controlValue"
170+
display-name-key="controlValue_Display_Key"
171+
description-key="controlValue_Desc_Key"
172+
of-type-group="numbers"
173+
usage="bound"
174+
required="true" />
175+
<resources>
176+
<code path="index.ts"
177+
order="1" />
178+
<css path="css/LinearInputControl.css"
179+
order="1" />
180+
</resources>
181+
</control>
182+
</manifest>
148183
```
149184

150-
4. Save the changes to the `ControlManifest.Input.xml` file.
185+
1. Save the changes to the `ControlManifest.Input.xml` file.
186+
1. After making changes to the manifest, you will need to generate ManifestDesignTypes.d.ts file in this directory using the below command."
187+
188+
```
189+
npm run refreshTypes
190+
```
151191
152192
## Implementing component logic
153193
@@ -341,7 +381,12 @@ npm start watch
341381

342382
Follow these steps to create and import a [solution](../../maker/data-platform/solutions-overview.md) file:
343383

344-
1. Create a new folder **Solutions** inside the **LinearInputControl** folder and navigate into the folder.
384+
1. Create a new folder named **Solutions** inside the **LinearInputControl** folder and navigate into the folder.
385+
386+
```CLI
387+
mkdir Solutions
388+
cd Solutions
389+
```
345390

346391
2. Create a new solution project in the **LinearInputControl** folder using the [pac solution init](/power-platform/developer/cli/reference/solution#pac-solution-init) command:
347392

powerapps-docs/developer/component-framework/manifest-schema-reference/includes/type-table.md

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
|Value |Description |
22
|--|--|
3-
|Currency|Monetary values between -922,337,203,685,477 and 922,337,203,685,477 can be in this column. You can set a level of precision or choose to base the precision on a specific currency or a single standard precision used by the organization.|
3+
|Currency|Monetary values between -922,337,203,685,477 and 922,337,203,685,477 can be in this column.|
44
|DateAndTime.DateAndTime|Displays date and time.|
55
|DateAndTime.DateOnly|Displays date only.|
6-
|Decimal|Up to 10 decimal points of precision can be used for values between -100,000,000,000 and -100,000,000,000 can be in this column. You can specify the level of precision and the maximum and minimum values.|
6+
|Decimal|Up to 10 decimal points of precision can be used for values between -100,000,000,000 and -100,000,000,000 can be in this column.|
77
|Enum|Enumerated data type.|
8-
|FP|Up to 5 decimal points of precision can be used for values between -100,000,000,000 and -100,000,000,000 can be in this column. You can specify the level of precision and the maximum and minimum values. |
8+
|FP|Up to 5 decimal points of precision can be used for values between -100,000,000,000 and -100,000,000,000 can be in this column.|
99
|Lookup.Simple|Allows for a single reference to a specific table. All custom lookups are this type.|
10-
|Multiple|This column can contain up to 1,048,576 text characters. You can set the maximum length to be less than this. When you add this column to a form, you can specify the size of the column.|
10+
|Multiple|This column can contain up to 1,048,576 text characters.|
1111
|MultiSelectOptionSet|You can customize forms (main, quick create, and quick view) and email templates by adding choices columns. When you add choices column, you can specify multiple values that will be available for users to select. When users fill out the form they can select one, multiple, or all the values displayed in a drop-down list.|
1212
|Object|Object data type. Can only be used with output properties. |
1313
|OptionSet|This column provides a set of options. Each option has a number value and label. When added to a form, this column displays a control for users to select only one option. |
@@ -16,7 +16,7 @@
1616
|SingleLine.Text|This option simply displays text.|
1717
|SingleLine.TextArea|This format option can be used to display multiple lines of text. But with a limit of 4000 characters, the Multiple Lines of Text column is a better choice if large amounts of text are expected.|
1818
|SingleLine.Ticker|This stores the string time in the format valid for Ticker. Out-of-the-box Unified Interface controls automatically make them clickable links.|
19-
|SingleLine.___URL|The text expected to provides a hyperlink to open the page specified. Out-of-the-box Unified Interface controls automatically prepend https:// to input values that does not begin with a valid protocol . Only HTTP, HTTPS, FTP , FTPS, OneNote and TEL protocols are expected in this column. |
19+
|SingleLine.___URL|The text expected to provides a hyperlink to open the page specified. Out-of-the-box Unified Interface controls automatically prepend "https://" to input values that does not begin with a valid protocol . Only HTTP, HTTPS, FTP , FTPS, OneNote and TEL protocols are expected in this column. |
2020
|TwoOptions|This column provides two options. Each option has a number value of 0 or 1 corresponding to a false or true value. Each option also has a label so that true or false values can be represented as "Yes" and "No", "Hot" and "Cold", "On" and "Off" or any pair of labels you want to display.|
2121
|Whole.None|This option simply displays a number.|
2222

@@ -38,3 +38,6 @@ Following `of-type` property values are not supported currently:
3838
|Lookup.Regarding|Allows for a single reference to multiple tables. These lookups are found in the regarding column used in activities.|
3939
|Status|A system column that has options that generally correspond to active and inactive status. Some system columns have additional options, but all custom columns have only Active and Inactive status options.|
4040
|Status Reason|A system column that has options that provide additional detail about the Status column. Each option is associated with one of the available Status options. You can add and edit the options.|
41+
42+
> [!NOTE]
43+
> At this time File columns are not supported. More information: [File columns](../../../../maker/data-platform/types-of-fields.md#file-columns)

powerapps-docs/developer/model-driven-apps/actions-dashboards.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,9 +3,9 @@ title: "Actions on dashboards (model-driven apps) | Microsoft Docs" # Intent and
33
description: "Learn about performing actions such as create, retrieve, update, or delete, on organization-owned and user-owned dashboards." # 115-145 characters including spaces. This abstract displays in the search result."
44
ms.date: 04/01/2022
55
ms.topic: article
6-
author: mspilde # GitHub ID
6+
author: sriharibs-msft
77
ms.subservice: mda-developer
8-
ms.author: mspilde # MSFT alias of Microsoft employees only
8+
ms.author: srihas
99
ms.reviewer:
1010
search.audienceType:
1111
- developer

powerapps-docs/developer/model-driven-apps/actions-visualizations-charts.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
22
title: "Actions on visualizations (charts) (model-driven apps) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces"
33
description: "Using the Microsoft Dataverse web services, you can perform the following actions on the visualization tables." # 115-145 characters including spaces. This abstract displays in the search result."
4-
author: mspilde
5-
ms.author: mspilde
4+
author: sriharibs-msft
5+
ms.author: srihas
66
ms.date: 04/01/2022
77
ms.reviewer: jdaly
88
ms.topic: article

powerapps-docs/developer/model-driven-apps/analyze-data-with-dashboards.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
22
title: "Analyze data with dashboards (model-driven apps) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces"
33
description: "The dashboard tables in Microsoft Dataverse enable you to present data from various charts, grids, IFRAMES, or web resources simultaneously. Dashboards allow you to compare and analyze various pieces of customer information, and give you data snapshots." # 115-145 characters including spaces. This abstract displays in the search result."
4-
author: mspilde
5-
ms.author: mspilde
4+
author: sriharibs-msft
5+
ms.author: srihas
66
ms.date: 04/01/2022
77
ms.reviewer: jdaly
88
ms.topic: article

powerapps-docs/developer/model-driven-apps/best-practices/business-logic/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,8 @@
22
title: "Developers: Best practices and guidance of client side scripting for model-driven apps | Microsoft Docs"
33
description: Best practices and guidance of client side scripting for developers of model-driven apps in Power Apps.
44
suite: powerapps
5-
author: HemantGaur
6-
ms.author: hemantg
5+
author: adrianorth
6+
ms.author: aorth
77

88
ms.date: 04/01/2022
99
ms.reviewer: jdaly

powerapps-docs/developer/model-driven-apps/best-practices/business-logic/remove-deactivated-disabled-configurations.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,12 +2,12 @@
22
title: "Remove deactivated or disabled customizations | MicrosoftDocs"
33
description: "Deactivated or disabled customizations should be removed from a solution to improve solution management and to decrease the risk of utilizing or managing an outdated component."
44
suite: powerapps
5-
author: jowells
5+
author: shmcarth
66

77
ms.topic: article
88
ms.date: 1/15/2019
99
ms.subservice: mda-developer
10-
ms.author: jowells
10+
ms.author: shmcarth
1111
search.audienceType:
1212
- developer
1313
search.app:

powerapps-docs/developer/model-driven-apps/best-practices/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,11 @@
22
title: "Developers: Best practices and guidance for model-driven apps | Microsoft Docs"
33
description: Best practices and guidance for developers of model-driven apps in Power Apps.
44
suite: powerapps
5-
author: jowells
5+
author: JimDaly
66
ms.topic: article
77
ms.date: 04/14/2021
88
ms.subservice: mda-developer
9-
ms.author: jowells
9+
ms.author: jdaly
1010
search.audienceType:
1111
- developer
1212
search.app:

powerapps-docs/developer/model-driven-apps/clientapi/clientapi-execution-context.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
22
title: "Client API execution context in model-driven apps| MicrosoftDocs"
33
description: "Explains the client api execution context"
4-
author: HemantGaur
5-
ms.author: hemantg
4+
author: adrianorth
5+
ms.author: aorth
66

77
ms.date: 04/01/2022
88
ms.reviewer: jdaly

powerapps-docs/developer/model-driven-apps/clientapi/clientapi-grid-context.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
22
title: "Client API grid context in model-driven apps| MicrosoftDocs"
33
description: "Describes the client api grid context"
4-
author: HemantGaur
5-
ms.author: hemantg
4+
author: jasongre
5+
ms.author: jasongre
66

77
ms.date: 04/01/2022
88
ms.reviewer: jdaly

0 commit comments

Comments
 (0)