[FEATURE] The output of Export-PnPPage should include Field values (`<pnp:FieldValues/>`)
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.
When using Export-PnPPage a nice PnP Template is generated with a <pnp:ClientSidePages></pnp:ClientSidePages> node.
The node includes the page Header and the Sections, but it does not include another interesting part of a page: its metadata. In our scenario we have pages with a lot of metadata, which is being used in an intranet to show these pages in several places. When exporting the page, I'd like these fields to be included as this makes it easy to apply these templates elsewhere without doing additional work.
Describe the solution you'd like
The <pnp:FieldValues></pnp:FieldValues> node is included in the exported page xml.
Describe alternatives you've considered
The workaround is injecting the values yourself, or updating the pages afterwards.
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 with the Export-PnPPage command and inspect how it generates the PnP template's ClientSidePages node. The change is complete when exported page XML includes a pnp:FieldValues node containing the page metadata values; verify the generated output against a page with metadata.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100