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/copresence-power-apps-studio.md
+45-22Lines changed: 45 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: mkaur
5
5
ms.topic: conceptual
6
6
ms.custom: canvas
7
7
ms.reviewer: mkaur
8
-
ms.date: 06/09/2023
8
+
ms.date: 06/27/2024
9
9
ms.subservice: canvas-maker
10
10
ms.author: mkaur
11
11
search.audienceType:
@@ -41,42 +41,65 @@ You might be working on the app, or you're inactive, but once someone else saves
41
41
42
42
## Inactive during editing
43
43
44
-
When you're editing an app and become inactive for two hours, a **Continue editing** dialog box is displayed, asking if you want to continue editing the app or switch to read-only. If you don't respond, the system informs you that you were inactive and puts you in read-only mode, so other readers can to become the editor.
44
+
When you're editing an app and become inactive for two hours, a **Continue editing** dialog box is displayed, asking if you want to continue editing the app or switch to read-only. If you don't respond, the system informs you that you were inactive and puts you in read-only mode, so other readers can become the editor.
45
45
46
46
If auto save is turned on, your changes are automatically saved. If auto save isn't turned on, a **You're no longer editing** dialog box appears that lets you save a copy of your changes.
47
47
48
48
49
-
## Live updates (experimental)
49
+
## Coauthoring (preview)
50
50
51
51
[This section is pre-release documentation and is subject to change.]
52
52
53
-
> [!IMPORTANT]
54
-
> - This is an experimental feature.
55
-
> - Experimental 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.
56
-
> - This feature is in the process of rolling out, and might not be available in your region yet.
53
+
Coauthoring allows multiple makers to edit a canvas app at the same time. When more than one person is editing an app, you'll see presences indicators showing where another maker is working on the app and see their changes in real time.
54
+
57
55
56
+
> [!div class="mx-imgBorder"]
57
+
> 
58
58
59
-
Live updates is a new experimental feature that works similarly to copresence. The user who opens the app first has the editing privileges. When another user attempts to open the app, a notification is displayed, informing them that someone else is currently editing the app and they're limited to read-only access. The benefit of live updates is that you can see in real-time the changes that are being made by the maker editing the app without the need to refresh the app.
60
59
61
-
### Enable live updates
60
+
Legend
62
61
63
-
To use live updates, it must be turned on for each individual app. Once live updates is enabled, it takes precedence over the copresence feature.
62
+
1. The command bar shows that you're in **Editing** mode. When there's multiple editors, you'll see their avatar.
63
+
1. The area that's being edited by another maker is highlighted and shows their initials.
64
+
1. The left-hand navigation pane in Power Apps Studio displays the app's structure, indicating which part of the app is being edited by another maker.
64
65
65
-
1. To enable live updates, open your app for editing in Power Apps Studio.
66
-
2. Go to **Settings** > **Upcoming features** > **Experimental**.
67
-
3. Set the toggle for **Enable live updates** to **On**.
66
+
> [!NOTE]
67
+
> Since multiple users can select and edit the same control at the same time, you may overwrite each other’s edits.
68
68
69
69
70
-
### Limitations of live updates
70
+
> [!IMPORTANT]
71
+
> - This is a preview feature.
72
+
> - This feature is in the process of rolling out, and might not be available in your region yet.
73
+
74
+
### Enable coauthoring
75
+
76
+
To use coauthoring, it must be turned on for each individual app. Once coauthoring is enabled, it takes precedence over the copresence feature.
77
+
78
+
1. To enable live updates, open your app for editing in Power Apps Studio.
79
+
2. Go to **Settings** > **Updates** > **Preview**.
80
+
3. Set the toggle for **Coauthoring** to **On**.
81
+
82
+
83
+
### Limitations
84
+
85
+
- The following options are disabled when there's more than one user editing the app:
86
+
- Search
87
+
- Save as
88
+
- Open another or new app
89
+
- Undo and redo
90
+
- Switch authoring versions
91
+
- The maximum number of coauthors allowed is 10, either in one session or across a total of 10 tabs, depending on which limit is reached first. Any additional coauthors or tabs beyond 10 will be in copresence and will not have the ability to edit the app or receive real-time updates.
92
+
- The app language is locked to the locale of the first user that opens the app for editing.
93
+
- Cut is disabled.
94
+
- Coauthoring is disabled in the Monitor tool.
95
+
- Problems might occur with the following actions:
96
+
- When you rename a control
97
+
- When you add AI Builder components
98
+
- When you add geospatial controls
99
+
- When one author adds a flow and another coauthor tries to run the flow without first refreshing the app
100
+
- Some errors from one author's actions are visible to all other coauthors
101
+
- When you copy and paste
71
102
72
-
The maker editing the app and those accessing it in read-only mode are unable to perform or have disabled access to these options:
73
103
74
-
- Undo or redo changes
75
-
- Switch authoring version
76
-
- Open a new app from data, app from template, new app from blank, and edit app
77
-
- Use **Save as** option or save the app locally
78
-
-[Monitor tool](../monitor-overview.md)
79
-
- Search pane
80
-
- Makers accessing the app in read-only mode can't make any changes
More information: [Use FetchXml to retrieve data](/power-apps/developer/data-platform/fetchxml/retrieve-data?tabs=sdk)
56
+
42
57
## View retained data using a flow
43
58
44
59
Create a Power Automate cloud flow to create an Excel file of the retained data from a FetchXML query and send as an email attachment. More information: [Create a cloud flow to view Dataverse long term retained data](/power-automate/dataverse/data-retention-flow)
The currency, whole number, and choice (formerly option sets) data types aren't currently supported.
144
+
The currency, and choice (formerly option sets) data types aren't currently supported.
143
145
144
146
## Function types
145
147
@@ -367,6 +369,36 @@ You can use the following scalar functions in a formula column:
367
369
|---------|---------|
368
370
|Retrieve a date value. |`DateAdd(UTCNow(),-1,TimeUnit.Years)`|
369
371
372
+
## Create a decimal formula column
373
+
374
+
Create a formula column that returns a decimal number.
375
+
376
+
1. When you create a column, enter the following information:
377
+
- A **Display name** for the column.
378
+
- Optionally, enter a **Description** of the column.
379
+
1. For **Data type** select ***fx* Formula**.
380
+
1. Enter a formula that returns a numeric value in the **Formula** bar.
381
+
This example creates a formula column called *Total Amount*. The *Price Per Unit* column is of decimal data type.
382
+
:::image type="content" source="media/formula-columns-decimal-fd.png" alt-text="Screenshot of a create a new formula column pane for use with a decimal number.":::
383
+
1. Expand **Advanced options**, select **Decimal** as the **Formula data type**, and then set the required number of decimal places.
384
+
:::image type="content" source="media/formula-columns-decimal-adv-options.png" alt-text="Screenshot of a decimal formula column definition.":::
385
+
1. Select **Save**.
386
+
387
+
## Create a whole number formula column
388
+
389
+
Create a formula column that returns a whole number.
390
+
391
+
1. When you create a column, enter the following information:
392
+
- A **Display name** for the column.
393
+
- Optionally, enter a **Description** of the column.
394
+
1. For **Data type** select ***fx* Formula**.
395
+
1. Enter a formula that returns a numeric value in the **Formula** bar.
396
+
This example creates a formula column called *Number of Units*. *Total Price* and *Price Per Unit* columns are of decimal data type.
397
+
:::image type="content" source="media/formula-columns-wholenum-fd.png" alt-text="Screenshot of a create a new formula column pane for use with a whole number..":::
398
+
1. Expand **Advanced options**, and select **Whole number** as the **Formula data type** and set the required format for whole number column.
399
+
:::image type="content" source="media/formula-columns-wholenum-adv-options.png" alt-text="Screenshot of a whole number formula column definition.":::
400
+
1. Select **Save**.
401
+
370
402
## Guidelines and limitations
371
403
372
404
This section describes guidelines and the known limitations with formula columns in Dataverse.
@@ -442,6 +474,8 @@ This section describes guidelines and the known limitations with formula columns
442
474
- Duplicate detection rules aren't triggered on formula columns.
443
475
- The `Now` function can be used with formula columns. `Now()` has user local behavior and `UTCNow()` has time zone independent behavior.
444
476
- You can set the precision property for decimal columns.
477
+
- Default formula data type value is set to **Decimal** for numeric value returning formulas.
478
+
- Updating whole number formula column's format isn't supported.
445
479
446
480
### Power Fx functions not currently supported
447
481
@@ -453,7 +487,6 @@ This section describes guidelines and the known limitations with formula columns
453
487
454
488
### Formula columns of data types that can't be produced
Copy file name to clipboardExpand all lines: powerapps-docs/maker/model-driven-apps/share-model-driven-app.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ editor: ''
6
6
tags: ''
7
7
ms.topic: how-to
8
8
ms.component: model
9
-
ms.date: 10/18/2023
9
+
ms.date: 06/28/2024
10
10
ms.subservice: mda-maker
11
11
ms.author: matp
12
12
search.audienceType:
@@ -155,7 +155,7 @@ There are a few key environment and licensing prerequisites required when sharin
155
155
- A Microsoft 365 user with Power Platform administrator rights or global admin rights must exist within the organization. [Learn how to assign Power Platform Administrator rights](/power-platform/admin/use-service-admin-role-manage-tenant). This provides the user with administrator rights over all environments.
156
156
- The app sharer must have admin privileges to the specific environment (or be a Power Platform administrator). The app sharer must have a [security role](/power-platform/admin/security-roles-privileges) with equal or greater privileges than the security role they're assigning to the app and to other users. Usually, this takes the form of the app sharer having the Dataverse **System Administrator** or **System Customizer** security role. These roles can be assigned by Power Platform administrators (who have rights over all Dataverse environments). The system administrator and system customizer security roles are standard roles that exist within all Dataverse environments.
157
157
- The user must exist as a user within the environment. It isn't enough to only be a Microsoft 365 user. This is because all users in an environment are accounted for and described within tables in the environment. [Learn how to add a user to an environment](/power-platform/admin/add-users-to-environment)
158
-
- Users must have the correct [license](/power-platform/admin/pricing-billing-skus) to be able to use the app. Users can [request a license themselves](../../user/request-license.md), or a [maker can request licenses for their app users](../common/request-licenses-for-users.md). Also, the license must be assigned in the tenant hosting the app. The exception to this prerequisite is when an app is hosted in a Microsoft Dataverse for Teams environment.
158
+
- Users must have the correct [license](/power-platform/admin/pricing-billing-skus) to be able to use the app. Users can [request a license themselves](../../user/request-license.md), or a [maker can request licenses for their app users](../common/request-licenses-for-users.md). Also, the license must be assigned in either the users home tenant or the tenant hosting the app.
159
159
160
160
## About predefined security roles
161
161
@@ -184,4 +184,4 @@ Administrators can use their organization's Microsoft Entra groups to manage acc
184
184
185
185
[Run a model-driven app on a mobile device](/dynamics365/customerengagement/on-premises/basics/dynamics-365-phones-tablets-users-guide-onprem)
0 commit comments