Support Tokens in Page Mapping

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/sp-dev-modernization#459 for details of a recent scenario example.

Start at the ConvertTo-PnPClientSidePage entry point and trace how the mapping file is read before page transformation. Review the PnP Provisioning token mechanism for a comparable approach. Done means mapping values can be tokenized and populated before conversion, reducing duplicate mapping files for transformation variants.