Skip to content

Commit 8d336a9

Browse files
authored
Merge pull request #3677 from MicrosoftDocs/matp-2050011-and-2049723
Matp 2050011 and 2049723
2 parents 951bf23 + 45b3122 commit 8d336a9

File tree

3 files changed

+55
-5
lines changed

3 files changed

+55
-5
lines changed

powerapps-docs/maker/TOC.yml

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1219,7 +1219,11 @@
12191219
- name: Validate and publish an app
12201220
href: ./model-driven-apps/validate-app.md
12211221
- name: Share an app
1222-
href: ./model-driven-apps/share-model-driven-app.md
1222+
items:
1223+
- name: Share a model-driven app
1224+
href: ./model-driven-apps/share-model-driven-app.md
1225+
- name: Privileges to view and access apps
1226+
href: ./model-driven-apps/app-visibility-privileges.md
12231227
- name: Manage an app
12241228
items:
12251229
- name: Manage app properties

powerapps-docs/maker/common-data-service/import-update-export-solutions.md

Lines changed: 13 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "Import solutions | MicrosoftDocs"
33
description: "Learn how to import a solution in Power Apps"
44
ms.custom: ""
5-
ms.date: 08/27/2020
5+
ms.date: 10/22/2020
66
ms.reviewer: ""
77
ms.service: powerapps
88
ms.topic: "article"
@@ -49,7 +49,7 @@ To import a solution:
4949

5050
1. Information about the solution is displayed. By default, in the **Advanced settings** section, if SDK messages and flows exist in the solution, they will be imported. Clear the **Enable SDK messages and flows included in the solution** option if you want them to import in an inactive state.
5151

52-
1. If your solution contains [connection references](create-connection-reference.md), you’ll be prompted to select the connections you want. If a connection does not already exist, create a new one. Click **Next**.
52+
1. If your solution contains [connection references](create-connection-reference.md), you’ll be prompted to select the connections you want. If a connection does not already exist, create a new one. Select **Next**.
5353

5454
1. If your solution contains [environment variables](EnvironmentVariables.md), you will be prompted to enter values. You will not see this screen if value(s) are already present in your solution or the target environment.
5555

@@ -78,16 +78,25 @@ During export of unmanaged solutions, some forms that aren't modified get export
7878

7979
### *Microsoft.Crm.CrmInvalidOperationException: full formXml is expected to create a form <formid>* message during solution import
8080

81-
This error can occur when the form you are importing doesn’t exist in the target environment and the form is imported for the first time. The solution you are importing has only form changes (diff) in the form XML when it should have the full form XML. A solution should only import a diff form XML when the form is already present in the environment and you’re importing the changes. To verify, open your solution’s customizations.xml file and search for the FormXml node using the form id that appears in the error message. If the form XML contains an attribute named `solutionaction`, then the form XML is a diff. To resolve this scenario the form XML must be a full form XML (should not contain the solutionaction attribute) and can be obtained from the instance this form was originally created in as unmanaged.
81+
This error can occur when the form you are importing doesn’t exist in the target environment and the form is imported for the first time. The solution you are importing has only form changes (diff) in the form XML when it should have the full form XML. A solution should only import a diff form XML when the form is already present in the environment and you’re importing the changes. To verify, open your solution’s customizations.xml file and search for the FormXml node using the form ID that appears in the error message. If the form XML contains an attribute named `solutionaction`, then the form XML is a diff. To resolve this scenario the form XML must be a full form XML (should not contain the solutionaction attribute) and can be obtained from the instance this form was originally created in as unmanaged.
8282

8383
### *Microsoft.Crm.CrmException: You cannot delete this form because it is the only fallback form of type main for the 'Entity' entity. Each entity must have at least one fallback form for each form type* message during solution upgrade or uninstall
8484

85-
This error occurs when a solution upgrade or uninstall attempts to delete the last remaining form for an entity. This behavior is by design. Each entity must be able to display a form for any valid user. Therefore, at least one form must be designated as a fallback form. A fallback form is available to users whose security roles do not have any forms explicitly assigned to them. To workaround this issue, create a temporary form configured as the fallback form for the entity, and then try the upgrade or uninstall again. More information: [Set the fallback form for an entity](../model-driven-apps/control-access-forms.md#set-the-fallback-form-for-an-entity)
85+
This error occurs when a solution upgrade or uninstall attempts to delete the last remaining form for an entity. This behavior is by design. Each entity must be able to display a form for any valid user. Therefore, at least one form must be designated as a fallback form. A fallback form is available to users whose security roles do not have any forms explicitly assigned to them. To work around this issue, create a temporary form configured as the fallback form for the entity, and then try the upgrade or uninstall again. More information: [Set the fallback form for an entity](../model-driven-apps/control-access-forms.md#set-the-fallback-form-for-an-entity)
8686

8787
### *Solution cannot be deleted due to dependencies from other components in the system* message when uninstalling a solution
8888

8989
This issue can occur when the solution contains components that are referenced by other solutions on top of it in the layer stack. To resolve this issue, either delete the component or remove the dependency from the solution you’re trying to uninstall. More information: [Removing dependencies](/power-platform/alm/removing-dependencies)
9090

91+
### Newly added components don’t appear in the app after importing an update to the app
92+
93+
A model-driven app change that uses **All** when selecting a component, such as a view, aren’t reflected after importing an update to the app in the target environment. This can happen when the following are true:
94+
95+
1. You didn’t initially select **All** in the app designer but selected the components individually. For example, you select two views, and then export the app in a managed solution from your development environment and imported it to your test (target) environment.
96+
2. Then you created another solution with the same app in the development environment. You selected **All** to select all views in the app designer. The solution is then exported as managed from your development environment and imported into your test (target) environment.
97+
98+
To work around this behavior, select each component individually, such as the newly added views described in step 2, rather than select All.
99+
91100
### See also
92101

93102
[Update solutions](update-solutions.md) <br />
Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
title: Privileges required to view apps in Power Apps | Microsoft Docs
3+
description: Learn about the privileges required to view and access apps in Power Apps.
4+
documentationcenter: ''
5+
author: Mattp123
6+
manager: kvivek
7+
editor: ''
8+
tags: ''
9+
ms.service: powerapps
10+
ms.topic: conceptual
11+
ms.component: model
12+
ms.date: 10/22/2020
13+
ms.author: matp
14+
search.audienceType:
15+
- maker
16+
search.app:
17+
- PowerApps
18+
- D365CE
19+
---
20+
21+
# Privileges required to view and access apps
22+
23+
Apps can be viewed by valid users with appropriate privileges who sign into Power Apps, the Power Apps mobile app, or Dynamics 365 home page. For a user to view and access apps in an environment, the following privileges, security role, or team membership are required:
24+
25+
- A user who has the write or create privilege on the Model-driven App entity makes the user a maker persona. That user can view and access all apps in the environment.
26+
- A user who has only the read privilege on the Model-driven App entity, must also have the associated security role(s) that are assigned to the app (or equivalent).
27+
28+
Note that read, create, and write privileges can be granted to a user by the security roles assigned to the user or granted through team membership.
29+
30+
By default, users who have only the Common Data Service User security role can only access model-driven apps that have that security role assigned to the app. This is because the Common Data Service User security role only has read privileges on the Model-driven App entity.
31+
32+
However, users who have the Environment Maker, System Administrator, or System Customizer security role can access and edit all model-driven apps within the environment. This is because these security roles have create, read, and write privileges on the Model-driven App entity. More information: [Share a model-driven app using Power Apps](share-model-driven-app.md)
33+
34+
### See also
35+
36+
[Manage teams](/power-platform/admin/manage-teams) <br />
37+
[Security roles and privileges](/power-platform/admin/security-roles-privileges)

0 commit comments

Comments
 (0)