Skip to content

Commit 3241136

Browse files
committed
Committing updates
1 parent 8d69d61 commit 3241136

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

powerapps-docs/maker/common-data-service/solution-layers.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -77,16 +77,18 @@ There are additional tabs available for specific component solution layers.
7777
|AttributePicklistValues (optionset attribute) | When selected for an optionset attribute, displays the values for the attribute. | Added, Updated, Removed, Unchanged |
7878

7979
<!--## Remove an unmanaged layer
80-
Unmanaged customizations reside at the top layer for a component and subsequently define the runtime behavior of the component. In most situations you don't want unmanaged customizations determining the behavior of your components. To remove the the unmanaged layer for a component, follow these steps:
80+
Unmanaged customizations reside at the top layer for a component and subsequently define the runtime behavior of the component. In most situations you don't want unmanaged customizations determining the behavior of your components. To remove the unmanaged layer for a component, follow these steps:
81+
82+
[!IMPORTANT]
83+
> Removing active unmanaged customizations can't be reversed or undone. All data associated with the unmanaged customization may be lost.
8184
8285
1. Open the solution you want, select **...** next to a component, such as **Account**, and then select **See solution layers**.
8386
2. If an unmanaged layer is detected, a message appears indicating the layer. On the left **Properties** pane, select **Remove unmanaged layer**.
8487
> [!div class="mx-imgBorder"]
8588
> ![Remove unmanaged layer](media/remove-unmanaged-layer.png)
8689
3. Save and publish to fully remove the unmanaged layer.
8790
88-
[!IMPORTANT]
89-
>Please be sure you want to make this change as this will impact your active unmanaged customizations and can not be reversed or undone. This may impact data and entities when the solution is removed.
91+
9092
-->
9193

9294
### See also

0 commit comments

Comments
 (0)