Skip to content

Latest commit

 

History

History
127 lines (90 loc) · 2.16 KB

Set-PnPWeb.md

File metadata and controls

127 lines (90 loc) · 2.16 KB
external help file applicable schema
SharePoint Server 2013, SharePoint Server 2016, SharePoint Online
2.0.0

Set-PnPWeb

SYNOPSIS

Sets properties on a web

SYNTAX

Set-PnPWeb [-SiteLogoUrl <String>]
           [-AlternateCssUrl <String>]
           [-Title <String>]
           [-Description <String>]
           [-MasterUrl <String>]
           [-CustomMasterUrl <String>]
           [-Web <WebPipeBind>]
           [-Connection <SPOnlineConnection>]

DESCRIPTION

Sets properties on a web

PARAMETERS

-AlternateCssUrl

Type: String
Parameter Sets: (All)

Required: False
Position: Named
Accept pipeline input: False

-CustomMasterUrl

Type: String
Parameter Sets: (All)

Required: False
Position: Named
Accept pipeline input: False

-Description

Type: String
Parameter Sets: (All)

Required: False
Position: Named
Accept pipeline input: False

-MasterUrl

Type: String
Parameter Sets: (All)

Required: False
Position: Named
Accept pipeline input: False

-SiteLogoUrl

Type: String
Parameter Sets: (All)

Required: False
Position: Named
Accept pipeline input: False

-Title

Type: String
Parameter Sets: (All)

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.

Type: SPOnlineConnection
Parameter Sets: (All)

Required: False
Position: Named
Accept pipeline input: False

-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.

Type: WebPipeBind
Parameter Sets: (All)

Required: False
Position: Named
Accept pipeline input: False

RELATED LINKS

SharePoint Developer Patterns and Practices