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/developer/component-framework/import-custom-controls.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ This topic describes how to import code components into Common Data Service. Aft
17
17
18
18
To create and import a solution file:
19
19
20
-
1. Create a new folder inside the folder that has the `cdsproj` file and name it as **Solutions** (or any name of your choice) using the command `mkdir Solutions`. Navigate into the directory using the command `cd Solutions`.
20
+
1. Create a new folder inside the folder that has the `pcfproj` file and name it as **Solutions** (or any name of your choice) using the command `mkdir Solutions`. Navigate into the directory using the command `cd Solutions`.
21
21
22
22
2. Create a new solutions project using the following command. The solution project is used for bundling the code component into a solution zip file that is used for importing into Common Data Service.
|`description-key`|Defines the description of the component that will be seen on the UI.|`string`|No|Model-driven apps and canvas apps (public preview) |
35
35
|`display-name-key`|Defines the name of the control that is displayed on the UI.|`string`|Yes|Model-driven apps and canvas apps (public preview) |
36
36
|`preview-image`|Image that will be used on the customization screens to show a preview of the component.|`string`|No|Model-driven apps|
37
-
|`version`|Defines the version of the component defined in [Semantic Versioning](https://semver.org)|`string`|Yes|Model-driven apps and canvas apps (public preview) (public preview)|
38
37
|`version`|Defines the version of the component defined in [Semantic Versioning](https://semver.org)|`string`|Yes|Model-driven apps and canvas apps (public preview) |
39
38
<!--|`hidden`|Defines whether the component should be hidden or not|[!INCLUDE [booleantype-description](includes/booleantype-description.md)]| No|Model-driven apps|-->
This sample shows how to create a dataset component for canvas apps. The dataset component also showcases how to use the dataset API methods to get column metadata, record data, page through data, and handle navigation.
19
19
20
-
You can download the sample component from [here](https://github.com/microsoft/PowerApps-Samples/tree/master/component-framework/TS_PropertSetyTableControl).
20
+
You can download the sample component from [here](https://github.com/microsoft/PowerApps-Samples/tree/master/component-framework/TS_PropertySetTableControl).
21
21
22
22
> [!div class="mx-imgBorder"]
23
23
> 
Copy file name to clipboardExpand all lines: powerapps-docs/maker/model-driven-apps/share-model-driven-app.md
+5-2Lines changed: 5 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ ms.service: powerapps
10
10
ms.devlang: na
11
11
ms.topic: conceptual
12
12
ms.component: model
13
-
ms.date: 12/17/2019
13
+
ms.date: 2/28/2020
14
14
ms.author: matp
15
15
search.audienceType:
16
16
- maker
@@ -84,6 +84,9 @@ For more information about access and scope privileges, see [Security roles](htt
84
84
85
85
8. Select the **Customization** tab, and then in the privileges list select the **Read** privilege next to **Model-driven App** so that organization scope  is selected.
86
86
87
+
> [!div class="mx-imgBorder"]
88
+
> 
89
+
87
90
9. Select **Save and Close**.
88
91
89
92
10. On the security role designer, in the **Role Name** box enter *Pet Grooming Schedulers*.
@@ -133,7 +136,7 @@ One or more security roles need to be assigned to the app. Users will have acces
133
136
134
137
135
138
> [!IMPORTANT]
136
-
> Users granted **Create** or**Write** to the **Model-driven App** privilege have access to all apps in the environment, even when they're not part of any role that has access to the app.
139
+
> Users granted **Read**, **Create**, and**Write** to the **Model-driven App** privilege have access to all apps in the environment, even when they're not part of any role that has access to the app.
137
140
> 
title: Collaborate using SharePoint | Microsoft Docs
3
3
description: Learn how to collaborate using SharePoint within a model-driven app
4
4
documentationcenter: ''
5
-
author: Mattp123
5
+
author: mduelae
6
6
manager: kvivek
7
7
editor: ''
8
8
tags: ''
9
9
ms.service: powerapps
10
10
ms.devlang: na
11
11
ms.topic: conceptual
12
12
ms.component: model
13
-
ms.date: 11/20/2019
13
+
ms.date: 03/02/2020
14
14
ms.author: matp
15
15
search.audienceType:
16
16
- maker
@@ -21,69 +21,124 @@ search.app:
21
21
22
22
# Collaborate using SharePoint
23
23
24
-
Manage common document types, such as Word, Excel, and PowerPoint and create folders to save and manage those documents that are seamlessly stored in SharePoint from within a model-driven app.
24
+
With Common Data Service, you can store your documents on SharePoint and manage them from within your app. The documents that you create in your app are stored on SharePoint, and are automatically synced to your desktop and mobile devices.
25
25
26
-
> [!NOTE]
27
-
> This feature requires that your system administrator has enabled SharePoint document management. More information: [Manage your documents using SharePoint](/power-platform/admin/manage-documents-using-sharepoint)
26
+
Before you can use SharePoint to store documents, it must be enabled by your system administrator. More information:
28
27
29
-
For account and contact records, a default document ___location folder is automatically created on SharePoint the first time you go to the **Files** tab. For other standard or custom entity records, go to the **Related** > **Documents** tab. The name of the document ___location is in this format: <record_name>_<record_id>.
28
+
-[Find your administrator or support person](find-admin.md)
30
29
31
-
By default, the ___location is set to Documents on Default Site 1.
30
+
-[Manage your documents using SharePoint](https://docs.microsoft.com/power-platform/admin/manage-documents-using-sharepoint)
32
31
33
-
## Add a document
34
-
1. Open an account or contact record and select the **Files** tab. For other standard or custom entities that are enabled for document management, select the **Related** tab, and then select **Documents**.
35
-
2. Choose from the following options.
36
-
- To create a new document, select **New**, select the document type you want, such as Word, Excel, or OneNote, and then enter a name. Select **Save**. The blank document opens in a new tab.
37
-
- To add an existing document, select **Upload**, select **Choose File**, browse to and select the file you want, and then select **Open**. Select **OK**.
32
+
## Where do you access the documents from?
38
33
39
-
The document file appears in the **Document Associated Grid** view.
34
+
1. For record types that support document management, open the record, select the **Related** tab, and then select **Documents**.
40
35
41
-
> [!div class="mx-imgBorder"]
42
-
> ![](media/add-doc-sharepoint.png"Add document to SharePoint")
36
+
> [!div class="mx-imgBorder"]
37
+
> ![Open the Documents tab in a record ](media/onedrive_nav.png"Open the Documents tab in a record")
43
38
44
-
The document also appears on the SharePoint site folder ___location.
39
+
2. Select **Document Location** > **Documents on Default Site 1**. When SharePoint is enabled, the ___location is set to **Documents on Default Site 1** by default.
45
40
46
-
> [!div class="mx-imgBorder"]
47
-
> ![](media/doc-on-sharepoint.png"Document on SharePoint")
3. The display name, parent site, and folder name are automatically populated. Change the details if required, and then select **Save**.
71
131
72
132
## Files tab FAQ
133
+
73
134
*Why was the ___location to access documents moved?*
74
135
- We moved the command to make documents easier to find with fewer clicks.
75
136
76
137
*Has the Documents tab gone away?*
77
-
- No, it hasn’t gone away. Users can still access the documents associated with the record in question the old way, simply by clicking the Related menu and then the Documents link.
138
+
- No, it hasn’t gone away. Users can still access the documents associated with the record in question the old way, simply by selecting the **Related** menu and then the **Documents** link.
78
139
79
140
*With the change, will subfolders in SharePoint still be created automatically?*
80
-
- Yes. The behavior is similar to that of the **Documents** link under the **Related** menu. When a user selects the **Files** tab for the first time, the corresponding SharePoint sub-folder is created by the system.
81
-
82
-
*Is there a way to add the Files tab to other entities or remove it?*
83
-
- Yes. To add or remove the File tab, follow the steps in this article. [Add the SharePoint documents tab to the main form for an entity](../maker/model-driven-apps/add-documents-tab-entity-main-form.md)
84
-
85
-
*Where can I send my feedback about this change?*
86
-
- You can send your feedback to the Dynamics 365 Sales Office and Teams Integration team at this email address: [email protected]
141
+
- Yes. The behavior is similar to that of the **Documents** link under the **Related** menu. When a user selects the **Files** tab for the first time, the corresponding SharePoint subfolder is created by the system.
87
142
88
-
### See also
89
-
[SharePoint, OneNote, and OneDrive integration with Common Data Service](../maker/common-data-service/sharepoint-onedrive-onenote-intro.md)
143
+
*Is there a way to add the Files tab to other entities, or remove it?*
144
+
- Yes. To add or remove the **Files** tab, follow the steps in this article: [Add the SharePoint documents tab to the main form for an entity](../maker/model-driven-apps/add-documents-tab-entity-main-form.md)
0 commit comments