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/canvas-apps/ai-overview.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: mduelae
5
5
ms.topic: conceptual
6
6
ms.custom: canvas
7
7
ms.reviewer:
8
-
ms.date: 06/11/2024
8
+
ms.date: 08/08/2024
9
9
ms.subservice: canvas-maker
10
10
ms.author: tapanm
11
11
search.audienceType:
@@ -55,7 +55,7 @@ Learn how to use Copilot features in Power Apps.
55
55
> [!IMPORTANT]
56
56
>
57
57
> - Preview features aren't meant for production use and may have restricted functionality. These features are available before an official release so that customers can get early access and provide feedback.
58
-
> - For more information, go to the [preview terms](https://go.microsoft.com/fwlink/?linkid=2189520).
58
+
> - For more information, go to the [preview terms](https://go.microsoft.com/fwlink/?linkid=2173149).
59
59
> - This capability is powered by [Azure OpenAI Service](/azure/cognitive-services/openai/overview).
60
60
> - This capability is in the process of rolling out, and may not be available in your region yet.
61
61
> - This capability may be subject to usage limits or capacity throttling.
Copy file name to clipboardExpand all lines: powerapps-docs/maker/data-platform/create-solution.md
+18-25Lines changed: 18 additions & 25 deletions
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: "Create a solution in Power Apps | MicrosoftDocs"
3
3
description: "Learn how to create a solution in Power Apps"
4
4
ms.custom: ""
5
-
ms.date: 06/14/2023
5
+
ms.date: 08/08/2024
6
6
ms.reviewer: ""
7
7
ms.topic: "how-to"
8
8
author: "Mattp123"
@@ -29,29 +29,29 @@ To create a solution:
29
29
|-----------|-----------------|
30
30
|**Display Name**|The name shown in the list of solutions. You can change this later.|
31
31
|**Name**|The unique name of the solution. This is generated using the value you enter in the Display Name column. You can edit this before you save the solution, but after you save the solution, you can’t change it.|
32
-
|**Publisher**|You can select the default publisher or create a new publisher. We recommend that you create a publisher for your organization to use consistently across your environments where you will use the solution. See [Solution publisher](#solution-publisher) later in this article. |
33
-
|**Version**|Enter a number for the version of your solution. This is only important if you export your solution. The version number will be included in the file name when you export the solution.|
32
+
|**Publisher**|You can select the default publisher or create a new publisher. We recommend that you create a publisher for your organization to use consistently across your environments where you'll use the solution. See [Solution publisher](#solution-publisher) later in this article. |
33
+
|**Version**|Enter a number for the version of your solution. This is only important if you export your solution. The version number is included in the file name when you export the solution.|
34
34
35
35
3. Select **Save**.
36
36
37
-
After you save the solution, you may wish to add information to columns that aren’t required. These steps are optional. Use the **Description** column to describe the solution and choose an HTML web resource as a **Configuration Page** for the solution. The configuration page is typically used by ISVs who distribute solutions. When this is set, a new **Configuration** node appears below the **Information** node to display this web resource. Developers will use this page to include instructions or controls to allow you to set configuration data or launch their solution.
37
+
After you save the solution, you might wish to add information to columns that aren’t required. These steps are optional. Use the **Description** column to describe the solution and choose an HTML web resource as a **Configuration Page** for the solution. The configuration page is typically used by ISVs who distribute solutions. When this is set, a new **Configuration** node appears below the **Information** node to display this web resource. Developers use this page to include instructions or controls to allow you to set configuration data or launch their solution.
38
38
39
39
<aname="BKMK_AddSolutionComponents"></a>
40
40
41
41
## Add solution components
42
42
43
-
After you’ve created your solution, it won’t contain any solution components. You can create new components to be added to the solution or add existing components to your new solution.
43
+
After you’ve created your solution, it won’t contain any solution components. You can create new components to be added to the solution or add existing components to your new solution.
44
44
45
-
### Create components in a solution
45
+
### Create components in a solution
46
46
47
-
You can use the **New** command to create different types of components. This takes you to a different create experience depending on the component type that you choose. After you finish creating the component, it will be added to the solution.
47
+
You can use the **New** command to create different types of components. This takes you to a different create experience depending on the component type that you choose. After you finish creating the component, it will be added to the solution.
48
48
49
49
> [!div class="mx-imgBorder"]
50
50
> 
51
51
52
-
### Add an existing component to a solution
52
+
### Add an existing component to a solution
53
53
54
-
With solutions that are unmanaged and not the default one, you can use the **Add existing** command to bring in components that aren’t already in the solution.
54
+
With solutions that are unmanaged and not the default one, you can use the **Add existing** command to bring in components that aren’t already in the solution.
55
55
56
56
> [!div class="mx-imgBorder"]
57
57
> 
@@ -61,22 +61,11 @@ To create a solution:
61
61
62
62
When you add an existing table, rather than select **Include all components** or **Include table metadata**, use the **Select components** option to only add the table components that have been updated. With solution segmentation, you export solution updates with selected table assets, such as table columns, forms, and views, rather than entire tables with all the assets. [Create a segmented solution with table assets](#create-a-segmented-solution-with-table-assets)
63
63
64
-
Many of the customizations you’ll want to do will involve tables. You can use the **table** filter to show a list of all the tables in the current solution that can be customized in some way. Once you drill into a table, you can see the components that are part of the table as shown with the account table in the following screenshot.
64
+
Many of the customizations you’ll want to do involve tables. You can use the **table** filter to show a list of all the tables in the current solution that can be customized in some way. Once you drill into a table, you can see the components that are part of the table as shown with the account table in the following screenshot.
This dialog alerts you that the solution component has dependencies on other solution components. If you select **No, do not include required components**, the solution may fail if you import it into another organization where all those required components do not exist. If the solution import succeeds, the behavior in the other solution may not be identical as the original organization because the components are configured differently than those in the source solution.
75
-
76
-
When you select table components, we recommend that you use solution segmentation so that you only include table components that are new or updated when you distribute solution updates. With solution segmentation, you work in a solution with selected table assets, such as table columns, forms, and views, rather than entire tables with all the assets. More information: [Use segmented solutions](use-segmented-solutions-patches-simplify-updates.md)
77
-
78
-
If you don’t intend to export the solution, or if you only intend to export it as an unmanaged solution and import it back into the same organization, it isn’t necessary to include required components. If you ever export the solution you’ll see another warning indicating that some required components are missing. If you are only going to import this solution back into the same organization, it is OK to disregard this warning. The steps to edit application navigation or the ribbon without using a third-party editing tool expect that you’ll export the solution back into the same organization.-->
79
-
80
69
## Publish changes
81
70
82
71
When you make unmanaged changes in an environment, some components, such as forms, tables, model-driven apps, site maps, and views are saved in an unpublished state. The publish action promotes these changes to an active state and makes them available to end users and for export.
@@ -95,6 +84,7 @@ When you make unmanaged changes in an environment, some components, such as form
95
84
> Preparing customizations may take some time. If you see a message that the browser page has become unresponsive, wait for the page to become responsive, and don't close it.
96
85
97
86
## Solution publisher
87
+
98
88
Every app you create or customization you make is part of a solution. Every solution has a publisher. You specify the publisher when you create a solution.
99
89
100
90
The solution publisher indicates who developed the app. For this reason, you should create a solution publisher that is meaningful. You can view the solution publisher for a solution by selecting **Settings** from the **Solutions** area in Power Apps. For more information about the solution publisher, see [Solution publisher](/power-platform/alm/solution-concepts-alm#solution-publisher) in the Power Platform ALM guide.
@@ -117,7 +107,7 @@ The solution publisher indicates who developed the app. For this reason, you sho
117
107
4. Select **Save and Close**.
118
108
119
109
> [!NOTE]
120
-
> Do not use _upgrade as part of the solution name. _upgrade is an internal reserved word for the solution [upgrade process](/power-apps/maker/data-platform/update-solutions#apply-the-upgrade-or-update-in-the-target-environment).
110
+
> Don't use _upgrade as part of the solution name. _upgrade is an internal reserved word for the solution [upgrade process](/power-apps/maker/data-platform/update-solutions#apply-the-upgrade-or-update-in-the-target-environment).
121
111
122
112
### Change a solution publisher
123
113
@@ -134,7 +124,7 @@ Use solution segmentation so that you only include table components that are upd
134
124
135
125
### Create a segmented solution with table assets
136
126
137
-
To create a segmented solution, start with creating an unmanaged solution and add only the components that you've updated. The wizard-like setup takes you step by step through the process of adding table assets.
127
+
To create a segmented solution, start with creating an unmanaged solution and add only the components that you've updated. The wizard-like setup takes you step by step through the process of adding table assets.
138
128
139
129
For example, imagine that you've created a new custom table that doesn't exist in any other environment named *Custom table* and also added a new column named *topten* for the account table. To create a segmented solution, follow these steps.
140
130
@@ -162,7 +152,8 @@ For example, imagine that you've created a new custom table that doesn't exist i
162
152
163
153
7. Select **Add** to add the components to the solution.
164
154
165
-
### Create a segmented solution using solution explorer
155
+
### Create a segmented solution using solution explorer
156
+
166
157
The following illustrations provide an example of creating a segmented solution by choosing table assets from the `Account`, `Case`, and `Contact` tables.
167
158
168
159
> [!NOTE]
@@ -177,7 +168,7 @@ Start by opening an unmanaged solution you created. Choose the **table** compone
@@ -124,10 +124,7 @@ Use decimals when you need to provide reports that require very accurate calcula
124
124
125
125
Use floating point numbers when you store data that represents fractions or values that you'll typically query comparing to another value using greater than or less than operators. In most cases, the difference between decimal and float isn't noticeable. Unless you require the most accurate possible calculations, floating point numbers should work for you.
126
126
127
-
Big Integers (or BigInt) are large numbers with a max value of 9,223,372,036,854,775,807. It's used to store very large numbers that exceed the capabilities of Whole Number and Decimal. Some uses for this include storage of time stamp values and as unique IDs, as well as numbers larger than 100 billion.
128
-
129
-
> [!NOTE]
130
-
> BigInt is currently only available for use through API. This includes data creation and data management.
127
+
Big integers (Big or BigInt) are large numbers with a max value of 9,223,372,036,854,775,807. It's used to store very large numbers that exceed the capabilities of Whole Number and Decimal. Some uses for this include storage of time stamp values and as unique IDs, as well as numbers larger than 100 billion.
Copy file name to clipboardExpand all lines: powerapps-docs/maker/data-platform/view-entity-data-power-bi.md
+6-9Lines changed: 6 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: "View table data in Power BI Desktop | MicrosoftDocs"
3
3
description: "Learn how to access and view table data in Power BI Desktop"
4
4
ms.custom: ""
5
-
ms.date: 05/06/2024
5
+
ms.date: 08/08/2024
6
6
ms.topic: how-to
7
7
ms.reviewer: "matp"
8
8
author: "Mattp123"
@@ -14,27 +14,24 @@ search.audienceType:
14
14
---
15
15
# View table data in Power BI Desktop
16
16
17
-
You can use Power BI Desktop to view tables in Microsoft Dataverse. The table
18
-
row data that you can access from your environment is read-only. Data access
19
-
uses the Dataverse security model that is the same used to access
20
-
table row data using a Power Apps app.
17
+
Use Power BI Desktop to view tables in Microsoft Dataverse. The table row data that you can access from your environment is read-only. Data access uses the Dataverse security model that is the same used to access table row data using a Power Apps app.
21
18
22
19
## Prerequisites
23
20
24
21
* Enable the Tabular Data Stream (TDS) endpoint (on by default). More information: [Manage feature settings](/power-platform/admin/settings-features).
25
22
* Power BI Desktop. [Get it now](https://powerbi.microsoft.com/downloads/)
26
-
23
+
27
24
## View table data
28
25
29
26
1. Sign into [Power Apps](https://make.powerapps.com/), and then select the
30
27
appropriate environment from the top-right corner.
31
28
1. On the left navigation pane select **Tables**. [!INCLUDE [left-navigation-pane](../../includes/left-navigation-pane.md)]
32
-
1. Select **Analyze in Power BI** on the command bar.
29
+
1. Select **Analyze** > **Analyze in Power BI** on the command bar.
33
30
34
31
The pbids file for your environment is downloaded to your browser’s default download folder.
35
32
36
-
> [!NOTE]
37
-
> To be able to download the file, you must have read access to the analysis component (msdyn_analysiscomponent) custom table privilege in Dataverse. Users with the environment maker security role have full access to this privilege.
33
+
> [!NOTE]
34
+
> To be able to download the file, you must have read access to the analysis component (msdyn_analysiscomponent) custom table privilege in Dataverse. Users with the environment maker security role have full access to this privilege.
38
35
39
36
1. Open the .pbids file to access it in Power BI Desktop.
Copy file name to clipboardExpand all lines: powerapps-docs/maker/model-driven-apps/additional-controls-for-dynamics-365-for-phones-and-tablets.md
+1-13Lines changed: 1 addition & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: "List of controls available for model-driven apps | MicrosoftDocs"
3
3
description: "A list of controls available for use with Power Apps model-driven apps for web, phones, and tablets"
4
4
ms.custom: ""
5
-
ms.date: 12/01/2022
5
+
ms.date: 08/08/2024
6
6
ms.reviewer: "matp"
7
7
ms.suite: ""
8
8
ms.tgt_pltfrm: ""
@@ -208,18 +208,6 @@ Use the Power BI report control to add a Power BI report on the form. More infor
208
208
209
209
Some components aren't displayed in the default **Components** list in the form designer but can be added to the list by selecting [Get more components](add-move-configure-or-delete-components-on-form.md#get-more-components).
210
210
211
-
### Input mask
212
-
213
-
With the input mask control, you set the formatting for a column like phone number or credit card to prevent entering invalid data. For example, if you want users to enter a United States phone number in the format +1-222-555-1011, use the input mask +1-000-000-0000.
214
-
215
-
> [!NOTE]
216
-
> This only sets formatting to a single line text column. It does not contain virtual actions like phone calling. If these actions are required, continue to use the default control.
217
-
218
-
|Property|Description|
219
-
|--------------|-----------------|
220
-
|Mask|Enter the mask to use for validating data as users enter it. You can use a combination of the following characters for the mask:<br /><br /> 0 – Digit<br /><br /> 9 – Digit or space<br /><br /> # – Digit, sign, or space<br /><br /> L – Letter<br /><br /> I – Letter or space<br /><br /> A – Alphanumeric<br /><br /> A – Alphanumeric or space<br /><br /> < – Converts characters that follow to lower case<br /><br /> > – Converts characters that follow to upper case<br /><br /> | – Disables case conversion<br /><br /> \ – Escapes any character, turning it into a literal<br /><br /> All others – Literals|
221
-
|Column|Shows the column the control is mapped to.|
222
-
223
211
### Form component
224
212
225
213
The form component control lets users edit information of a related table record directly from another table’s form. For example, here's the form component on a separate tab on the main account form, which lets the user edit a contact record without leaving the account form. More information: [Edit related table records directly from another table’s main form](form-component-control.md)
0 commit comments