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/cards/make-a-card/designer-overview.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,7 @@ Legend:
42
42
43
43
### Main menu
44
44
45
-
Use the main menu to switch between the tools available in the card designer:
45
+
Use the main menu to switch between the tools available in the card designer.
46
46
47
47
-**Tree View**: View card elements as a hierarchy and view the relationships between elements
48
48
-**Insert**: Add controls
@@ -75,16 +75,16 @@ Each element also has advanced properties, such as:
75
75
76
76
-**Repeat for every**: Trigger whether or when an element should be repeated
77
77
-**Show when**: Trigger when to show the element
78
-
-**Requires**: Make the element dependent on certain features, with a corresponding minimum version
78
+
-**Requires**: Make the element dependent on certain features with a corresponding minimum version
79
79
80
80
You can also enter Power Fx expressions in some properties, creating low-code solutions that make your card more powerful.
81
81
82
82
### Formula bar and Power Fx editor
83
83
84
-
Use the formula bar to enter a Power Fx expression as a property of the selected control; for example, to calculate a value when a button is clicked. The formula bar even assists you as you're writing an expression. [Learn more about Power FX](../make-a-card/power-fx/intro-to-pfx.md) and the [functions and formulas you can use in an expression](/powerapps/maker/canvas-apps/formula-reference).
84
+
Use the formula bar to enter a Power Fx expression as a property of the selected control (for example, to calculate a value when a button is clicked). The formula bar even assists you as you're writing an expression. [Learn more about Power FX](../make-a-card/power-fx/intro-to-pfx.md) and the [functions and formulas you can use in an expression](/powerapps/maker/canvas-apps/formula-reference).
85
85
86
86
> [!NOTE]
87
-
> Some expressions that are supported in Power Apps aren't available for cards. For more information, see[Power Fx and cards overview](../make-a-card/power-fx/intro-to-pfx.md).
87
+
> Some expressions that are supported in Power Apps aren't available for cards. For more information, go to[Power Fx and cards overview](../make-a-card/power-fx/intro-to-pfx.md).
Copy file name to clipboardExpand all lines: powerapps-docs/cards/make-a-card/variables/variables.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ As an example, you've created a card that counts how many times the user presses
41
41
42
42
You can't change the name or type of a variable. If you need to change them, create a new variable.
43
43
44
-
You can also customize sender options and, under **Additional variable information**, the **Title** and **Description** of the variable. This information may be helpful for testing and debugging and using your variable with Power Automate flows and Power Virtual Agents bots.
44
+
You can also customize sender options and, under **Additional variable information**, the **Title** and **Description** of the variable. This information may be helpful for testing, debugging, and using your variable with Power Automate flows and Power Virtual Agents bots.
45
45
46
46
:::image type="content" source="../../media/variables/new-variable.png" alt-text="Screenshot of the New variable window in the card designer.":::
Copy file name to clipboardExpand all lines: powerapps-docs/cards/manage-cards/manage-cards.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ This section shows you how to manage cards using security roles.
26
26
27
27
Cards are stored as rows in Dataverse within the **Card** table. Administrators can use [security roles to control who can create, read, and update cards](/power-platform/admin/wp-security-cds#tablerecord-ownership).
28
28
29
-
For example, if the user is only assigned to a security role that does not have permission to create rows in the **Card** table, then the user will not be able to create cards.
29
+
For example, if the user is only assigned to a security role that does not have permission to create rows in the **Card** table, then the user won't be able to create cards.
30
30
31
31
Note that a user will still be able to receive and use cards sent in Teams, regardless of the security role assigned to the user, as those cards are accessed by the Cards for Power Apps service.
32
32
@@ -57,4 +57,4 @@ This section shows you how to delete a card.
57
57
58
58
### Delete a card as the administrator
59
59
60
-
If the owner of an app is unavailable, it is currently not possible for an administrator, such as Global admin, Azure Active Directory Global admin, or Dynamics 365 admin to delete a card. We are working on enabling this capability.
60
+
If the owner of an app is unavailable, it is currently not possible for an administrator, such as Global admin, Azure Active Directory Global admin, or Dynamics 365 admin to delete a card. We're working on enabling this capability.
Copy file name to clipboardExpand all lines: powerapps-docs/developer/component-framework/implementing-controls-using-typescript.md
+80-35Lines changed: 80 additions & 35 deletions
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: "Create your first component using Power Apps Component Framework in Micr
3
3
description: "Learn how to implement code components using Power Apps component framework"
4
4
ms.author: noazarur
5
5
author: noazarur-microsoft
6
-
ms.date: 05/27/2022
6
+
ms.date: 12/15/2022
7
7
ms.reviewer: jdaly
8
8
ms.topic: article
9
9
ms.subservice: pcf
@@ -65,7 +65,7 @@ To create a new project:
65
65
1. At the terminal prompt, create a new component project by passing basic parameters using the [pac pcf init](/power-platform/developer/cli/reference/pcf#pac-pcf-init) command.
66
66
67
67
```CLI
68
-
pac pcf init --namespace SampleNamespace --name LinearInputControl --template field
68
+
pac pcf init --namespace SampleNamespace --name LinearInputControl --template field --run-npm-install
69
69
```
70
70
71
71
1. The above command also runs the `npm install` command for you to setup the project build tools.
@@ -76,10 +76,6 @@ To create a new project:
76
76
> [!NOTE]
77
77
> 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.
78
78
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
-
```
83
79
84
80
85
81
## Implementing manifest
@@ -98,56 +94,100 @@ Make changes to the predefined manifest file, as shown here:
98
94
-**control-type**: The code component type. Only *standard* types of code components are supported.
<!-- 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-groupname="numbers">
114
+
<type>Whole.None</type>
115
+
<type>Currency</type>
116
+
<type>FP</type>
117
+
<type>Decimal</type>
118
+
</type-group>
104
119
```
105
120
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:
107
122
108
123
- **name**: Name of the property.
109
124
- **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.
112
127
- **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.
113
128
- **required**: Defines whether the property is required.
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:
120
140
121
141
- **code**: Refers to the path where all the resource files are located.
122
142
123
143
```XML
124
144
<resources>
125
-
<codepath="index.ts"order="1" />
126
-
<csspath="css/LinearInputControl.css"order="1" />
145
+
<codepath="index.ts"
146
+
order="1" />
147
+
<csspath="css/LinearInputControl.css"
148
+
order="1" />
127
149
</resources>
128
150
```
129
-
The overall manifest file should look something like this:
151
+
152
+
The completed manifest file should look like this:
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
+
```
151
191
152
192
## Implementing component logic
153
193
@@ -341,7 +381,12 @@ npm start watch
341
381
342
382
Follow these steps to create and import a [solution](../../maker/data-platform/solutions-overview.md) file:
343
383
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
+
```
345
390
346
391
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:
Copy file name to clipboardExpand all lines: powerapps-docs/developer/component-framework/manifest-schema-reference/includes/type-table.md
+8-5Lines changed: 8 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,13 @@
1
1
|Value |Description |
2
2
|--|--|
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.|
4
4
|DateAndTime.DateAndTime|Displays date and time.|
5
5
|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.|
7
7
|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.|
9
9
|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.|
11
11
|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.|
12
12
|Object|Object data type. Can only be used with output properties. |
13
13
|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. |
|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.|
18
18
|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. |
20
20
|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.|
21
21
|Whole.None|This option simply displays a number.|
22
22
@@ -38,3 +38,6 @@ Following `of-type` property values are not supported currently:
38
38
|Lookup.Regarding|Allows for a single reference to multiple tables. These lookups are found in the regarding column used in activities.|
39
39
|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.|
40
40
|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)
0 commit comments