[FEATURE] Get-PnPSiteTemplate - add ability to exclude builtin fields
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 904
- Forks
- 407
- Avg merge
- 9h 16m
- Merged PRs (30d)
- 10
Description
Is your feature request related to a problem? Please describe.
It would be nice if there was an option to exclude built-in fields from provisioning template. I often need to declutter exported template with builtin fields, as all I really need are custom ones.
Describe the solution you'd like
Have either:
- a flag (ExcludeBuiltinFields)
or - a parameter allowing to specify only those field groups that should be exported (FieldGroups - similar to ContentTypeGroups).
added to Get-PnPSiteTemplate cmdlet
Describe alternatives you've considered
I did not find a way to do it using currently existing cmdlets.
Additional context
If this feature is approved, I'd be happy to implement this and provide a PR
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Get-PnPSiteTemplate cmdlet and inspect how its existing ContentTypeGroups parameter is handled. Compare the proposed ExcludeBuiltinFields flag with the FieldGroups alternative, then verify that exported provisioning templates omit built-in fields while retaining custom fields.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100