provide parameter translation for data pages without forcing whole-app migration
As it stands, only whole-app migration (export and import) brings parameters across as parameters. This is essential when using parameters to store page-keys, which is essential for page-to-page movement based on user actions and button clicks etc.
If we export selected pages only, then the parameters get resolved into static values, and that too the values as relevant to the source instance, which renders pointless the whole purpose of parameters because they are all wrong in the destination instance.
-
Bethany J. commented
I agree, this drives me nuts as well. It makes developing small changes much more difficult when you can't just export/import only the changed DataPages without losing the parameters.