Merge pull request MicrosoftDocs#143 from erwinvanhunen/master

SharePoint PnP PowerShell Documentation updates

Author: VesaJuvonen

sharepoint/docs-conceptual/sharepoint-pnp/sharepoint-pnp-cmdlets.md

@@ -10,8 +10,19 @@ Add/uploads an available app to the app catalog
 
 ## SYNTAX 
 
+### Add only
 ```powershell
 Add-PnPApp -Path <String>
+           [-Overwrite [<SwitchParameter>]]
+           [-Connection <SPOnlineConnection>]
+```
+
+### Add and Publish
+```powershell
+Add-PnPApp -Publish [<SwitchParameter>]
+           -Path <String>
+           [-SkipFeatureDeployment [<SwitchParameter>]]
+           [-Overwrite [<SwitchParameter>]]
            [-Connection <SPOnlineConnection>]
 ```
 
@@ -24,20 +35,63 @@ PS:> Add-PnPApp -Path ./myapp.sppkg
 
 This will upload the specified app package to the app catalog
 
+### ------------------EXAMPLE 2------------------
+```powershell
+PS:> Add-PnPApp -Path ./myapp.sppkg -Publish
+```
+
+This will upload the specified app package to the app catalog and deploy/trust it at the same time.
+
 ## PARAMETERS
 
+### -Overwrite
+Overwrites the existing app package if it already exists
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+
+Required: False
+Position: Named
+Accept pipeline input: False
+```
+
 ### -Path
 Specifies the Id or an actual app metadata instance
 
 ```yaml
 Type: String
-Parameter Sets: (All)
+Parameter Sets: Add only
 
 Required: True
 Position: 0
 Accept pipeline input: True
 ```
 
+### -Publish
+This will deploy/trust an app into the app catalog
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: Add and Publish
+
+Required: True
+Position: Named
+Accept pipeline input: False
+```
+
+### -SkipFeatureDeployment
+
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: Add and Publish
+
+Required: False
+Position: Named
+Accept pipeline input: False
+```
+
 ### -Connection
 Optional connection to be used by cmdlet. Retrieve the value for this parameter by eiter specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection.
 

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPApp.md

@@ -124,7 +124,7 @@ Accept pipeline input: False
 ```
 
 ### -Web
-The GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
+This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
 
 ```yaml
 Type: WebPipeBind

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPClientSidePage.md

@@ -93,7 +93,7 @@ Accept pipeline input: False
 ```
 
 ### -Web
-The GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
+This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
 
 ```yaml
 Type: WebPipeBind

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPClientSidePageSection.md

@@ -117,7 +117,7 @@ Accept pipeline input: False
 ```
 
 ### -Web
-The GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
+This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
 
 ```yaml
 Type: WebPipeBind

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPClientSideText.md

@@ -179,7 +179,7 @@ Accept pipeline input: False
 ```
 
 ### -Web
-The GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
+This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
 
 ```yaml
 Type: WebPipeBind

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPClientSideWebPart.md

@@ -104,7 +104,7 @@ Accept pipeline input: False
 ```
 
 ### -Web
-The GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
+This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
 
 ```yaml
 Type: WebPipeBind

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPContentType.md

@@ -29,7 +29,7 @@ This will add the content type called 'Test CT' to the document set called ''Tes
 ### ------------------EXAMPLE 2------------------
 ```powershell
 PS:> $docset = Get-PnPDocumentSetTemplate -Identity "Test Document Set"
-PS:> $ct = Get-SPOContentType -Identity "Test CT"
+PS:> $ct = Get-PnPContentType -Identity "Test CT"
 PS:> Add-PnPContentTypeToDocumentSet -ContentType $ct -DocumentSet $docset
 ```
 
@@ -81,7 +81,7 @@ Accept pipeline input: False
 ```
 
 ### -Web
-The GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
+This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
 
 ```yaml
 Type: WebPipeBind

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPContentTypeToDocumentSet.md

@@ -78,7 +78,7 @@ Accept pipeline input: False
 ```
 
 ### -Web
-The GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
+This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
 
 ```yaml
 Type: WebPipeBind

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPContentTypeToList.md

@@ -252,7 +252,7 @@ Accept pipeline input: False
 ```
 
 ### -Web
-The GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
+This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
 
 ```yaml
 Type: WebPipeBind

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPCustomAction.md

@@ -124,7 +124,7 @@ Accept pipeline input: False
 ```
 
 ### -Web
-The GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
+This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
 
 ```yaml
 Type: WebPipeBind

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPDataRowsToProvisioningTemplate.md

@@ -78,7 +78,7 @@ Accept pipeline input: False
 ```
 
 ### -Web
-The GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
+This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
 
 ```yaml
 Type: WebPipeBind

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPDocumentSet.md

@@ -139,7 +139,7 @@ Accept pipeline input: False
 ```
 
 ### -Web
-The GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
+This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
 
 ```yaml
 Type: WebPipeBind

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPEventReceiver.md

@@ -235,7 +235,7 @@ Accept pipeline input: False
 ```
 
 ### -Web
-The GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
+This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
 
 ```yaml
 Type: WebPipeBind

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPField.md

@@ -74,7 +74,7 @@ Accept pipeline input: False
 ```
 
 ### -Web
-The GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
+This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
 
 ```yaml
 Type: WebPipeBind

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPFieldFromXml.md

@@ -91,7 +91,7 @@ Accept pipeline input: False
 ```
 
 ### -Web
-The GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
+This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
 
 ```yaml
 Type: WebPipeBind

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPFieldToContentType.md

@@ -236,7 +236,45 @@ Accept pipeline input: False
 ```
 
 ### -Values
-Use the internal names of the fields when specifying field names
+Use the internal names of the fields when specifying field names.
+
+Single line of text: -Values @{"Title" = "Title New"}
+
+Multiple lines of text: -Values @{"MultiText" = "New text\n\nMore text"}
+
+Rich text: -Values @{"MultiText" = "<strong>New</strong> text"}
+
+Choice: -Values @{"Choice" = "Value 1"}
+
+Number: -Values @{"Number" = "10"}
+
+Currency: -Values @{"Number" = "10"}
+
+Currency: -Values @{"Currency" = "10"}
+
+Date and Time: -Values @{"DateAndTime" = "03/10/2015 14:16"}
+
+Lookup (id of lookup value): -Values @{"Lookup" = "2"}
+
+Multi value lookup (id of lookup values as array 1): -Values @{"MultiLookupField" = "1","2"}
+
+Multi value lookup (id of lookup values as array 2): -Values @{"MultiLookupField" = 1,2}
+
+Multi value lookup (id of lookup values as string): -Values @{"MultiLookupField" = "1,2"}
+
+Yes/No: -Values @{"YesNo" = $false}
+
+Person/Group (id of user/group in Site User Info List or email of the user, seperate multiple values with a comma): -Values @{"Person" = "[email protected]","21"}
+
+Managed Metadata (single value with path to term): -Values @{"MetadataField" = "CORPORATE|DEPARTMENTS|FINANCE"}
+
+Managed Metadata (single value with id of term): -Values @{"MetadataField" = "fe40a95b-2144-4fa2-b82a-0b3d0299d818"} with Id of term
+
+Managed Metadata (multiple values with paths to terms): -Values @{"MetadataField" = "CORPORATE|DEPARTMENTS|FINANCE","CORPORATE|DEPARTMENTS|HR"}
+
+Managed Metadata (multiple values with ids of terms): -Values @{"MetadataField" = "fe40a95b-2144-4fa2-b82a-0b3d0299d818","52d88107-c2a8-4bf0-adfa-04bc2305b593"}
+
+Hyperlink or Picture: -Values @{"Hyperlink" = "https://github.com/OfficeDev/, OfficePnp"}
 
 ```yaml
 Type: Hashtable
@@ -260,7 +298,7 @@ Accept pipeline input: False
 ```
 
 ### -Web
-The GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
+This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
 
 ```yaml
 Type: WebPipeBind

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPFile.md

@@ -15,7 +15,9 @@ Add-PnPFileToProvisioningTemplate -Path <String>
                                   -Source <String>
                                   -Folder <String>
                                   [-Container <String>]
+                                  [-FileLevel <FileLevel>]
                                   [-TemplateProviderExtensions <ITemplateProviderExtension[]>]
+                                  [-FileOverwrite [<SwitchParameter>]]
 ```
 
 ## EXAMPLES
@@ -25,14 +27,28 @@ Add-PnPFileToProvisioningTemplate -Path <String>
 PS:> Add-PnPFileToProvisioningTemplate -Path template.pnp -Source $sourceFilePath -Folder $targetFolder
 ```
 
-Adds a file to an in-memory PnP Provisioning Template
+Adds a file to a PnP Provisioning Template
 
 ### ------------------EXAMPLE 2------------------
 ```powershell
+PS:> Add-PnPFileToProvisioningTemplate -Path template.xml -Source $sourceFilePath -Folder $targetFolder
+```
+
+Adds a file reference to a PnP Provisioning XML Template
+
+### ------------------EXAMPLE 3------------------
+```powershell
+PS:> Add-PnPFileToProvisioningTemplate -Path template.pnp -Source "./myfile.png" -Folder "folderinsite" -FileLevel Published -FileOverwrite:$false
+```
+
+Adds a file to a PnP Provisioning Template, specifies the level as Published and defines to not overwrite the file if it exists in the site.
+
+### ------------------EXAMPLE 4------------------
+```powershell
 PS:> Add-PnPFileToProvisioningTemplate -Path template.pnp -Source $sourceFilePath -Folder $targetFolder -Container $container
 ```
 
-Adds a file to an in-memory PnP Provisioning Template with a custom container for the file
+Adds a file to a PnP Provisioning Template with a custom container for the file
 
 ## PARAMETERS
 
@@ -48,6 +64,30 @@ Position: 3
 Accept pipeline input: False
 ```
 
+### -FileLevel
+The level of the files to add. Defaults to Published
+
+```yaml
+Type: FileLevel
+Parameter Sets: (All)
+
+Required: False
+Position: 4
+Accept pipeline input: False
+```
+
+### -FileOverwrite
+Set to overwrite in site, Defaults to true
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+
+Required: False
+Position: 5
+Accept pipeline input: False
+```
+
 ### -Folder
 The target Folder for the file to add to the in-memory template.
 

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPFileToProvisioningTemplate.md

@@ -65,7 +65,7 @@ Accept pipeline input: False
 ```
 
 ### -Web
-The GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
+This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
 
 ```yaml
 Type: WebPipeBind

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPFolder.md

@@ -104,7 +104,7 @@ Accept pipeline input: False
 ```
 
 ### -Web
-The GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
+This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
 
 ```yaml
 Type: WebPipeBind

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPHtmlPublishingPageLayout.md

@@ -43,7 +43,7 @@ Accept pipeline input: False
 ```
 
 ### -Web
-The GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
+This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
 
 ```yaml
 Type: WebPipeBind

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPIndexedProperty.md

@@ -102,7 +102,7 @@ Accept pipeline input: False
 ```
 
 ### -Web
-The GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
+This parameter allows you to optionally apply the cmdlet action to a subweb within the current web. In most situations this parameter is not required and you can connect to the subweb using Connect-PnPOnline instead. Specify the GUID, server relative url (i.e. /sites/team1) or web instance of the web to apply the command to. Omit this parameter to use the current web.
 
 ```yaml
 Type: WebPipeBind