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
List Instance FieldRef for Title Column missing from Site Template
Expected behavior
ListInstance/FieldRef element should be in template for Title column that is renamed at list level
Actual behavior
No FieldRef for Title in ListInstance definition, so column display name is "Title" in a site provisioned from template, rather than display name from source site
Steps to reproduce behavior
Create Site Content Type that includes a Title site column (from Item content type)
Add Content Type to a List Instance
Rename Title on List Instance Content Type to change Display Name of Title column for that list
Run Get-PnPSiteTemplate and examine FieldRefs for ListInstance
What is the version of the Cmdlet module you are running?
1.5.0
Which operating system/environment are you running PnP PowerShell on?
Windows
PowerShell Core 7.1.3
Workaround
Manually add a FieldRef for the Title column to the ListInstance in the template file with the required DisplayName attribute
The text was updated successfully, but these errors were encountered:
Reporting an Issue or Missing Feature
List Instance FieldRef for Title Column missing from Site Template
Expected behavior
ListInstance/FieldRef element should be in template for Title column that is renamed at list level
Actual behavior
No FieldRef for Title in ListInstance definition, so column display name is "Title" in a site provisioned from template, rather than display name from source site
Steps to reproduce behavior
Get-PnPSiteTemplate
and examine FieldRefs for ListInstanceWhat is the version of the Cmdlet module you are running?
1.5.0
Which operating system/environment are you running PnP PowerShell on?
Workaround
Manually add a FieldRef for the Title column to the ListInstance in the template file with the required DisplayName attribute
The text was updated successfully, but these errors were encountered: