Support Tokens in Page Mapping

[pkbullock]

Category

[ ] Bug
[X] Enhancement

Problem Area

[ ] Page Transformation: Error during the setup/use of the Page Transformation UI solution (did you check our troubleshooting guide?)
[X] Page Transformation: Error during the use of page transformation from PnP PowerShell
[ ] Page Transformation: Error during the use of page transformation from .Net
[ ] Page Transformation: Page is not looking correct after transformation
[ ] Modernization Scanner: something went wrong...

Expected or Desired Behavior

Consider adding tokenization to the mapping file to populate properties like Header type in PowerShell before passing the mapping file into ConvertTo-PnPClientSidePage.

A mechanism much like the properties you can pass to PnP Provisioning that replace values prior to processing the file.

This would reduce the number of duplicate mapping files for variants of a transformation based on criteria, see ref pnp/modernization#459 for details of a recent scenario example.

[jansenbe]

@pkbullock , @mbice,

Simple token support (non nested simple tokens in webpartmapping.xml and your page layout mapping files) in combination with having an option to pass them along on the PS commandline shouldn't be hard to build. I'm OOF until April 20th, but will assign this to the May release for now.

[pkbullock]

I will be starting this one next, sorry missed June release.

[mbice]

Hi,

Curious if this is something that is still in the roadmap and whether there would be a time frame available on it yet?

@jansenbe @pkbullock

Thanks!