Skip to content
This repository has been archived by the owner on Jan 19, 2021. It is now read-only.

Built-in fields, field refs and content types are included when generating provisioning template #1871

Open
ChrisAV81 opened this issue Aug 1, 2018 · 2 comments

Comments

@ChrisAV81
Copy link

Category

[x] Bug
[ ] Enhancement

Environment

[x] Office 365 / SharePoint Online
[ ] SharePoint 2016
[ ] SharePoint 2013

Expected or Desired Behavior

Built in fields, field refs and content types are included in the provisioning template when running Get-PnPProvisioningTemplate on a communication site.

Observed Behavior

When exporting fields with the Get-PnPProvisioningTemplate command, the following built in fields are included in the resulting XML.

Site fields:
_OriginalSourceSiteId, _OriginalSourceUrl, _OriginalSourceItemId, _OriginalSourceListId, _OriginalSourceWebId, _AuthorByline

Fielf refs on custom lists:
_ComplianceFlags, _ComplianceTag, _ComplianceTagWrittenTime, _ComplianceTagUserId, _IsRecord, ComplianceAssetId

Content Type: Repost Page

Are these fields, field refs and the content type really expected to be included in the provisioning template? Should these be kept or removed in the XML template before applying the template to a new site?

Steps to Reproduce

Run Get-PnPProvisioningTemplate -Handlers Fields,ContentTypes,Lists

@gszdev
Copy link
Contributor

gszdev commented Aug 2, 2018

Maybe a Special handling for the "Repost Page" content type is necessary.
Please check also [Repost Page issue] (#1788).

@jansenbe
Copy link
Contributor

jansenbe commented Aug 7, 2018

Added comments to #1788

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants