Update per user form data export

[sheralim012]

• Update headings
• Add page id column

[istride]

@cbunicef How concerned should we be about automatic processing that might be happening on these data exports? If we insert a new column at the beginning of each row and rename other columns, will that cause problems?

If it might, we can make this change in a less destructive way by:

• appending the new column (page id) at the end of the row
• renaming existing columns, but also duplicating them with their original name at the end of the row (for backwards compatibility, in case they are being referred to by name)
• allow a grace period
• remove the duplicated columns in a future release

[cbunicef]

It's possible that it could, we use Power BI quite often and M is super fragile in my experience. Even appending new columns can cause issues.

Could we set a date to change the data export format, and add a text to the page eg "The format for data exports will be changing on X day, please see here for more information." - and we can link to a page on cms-manual. Is that possible?

We would want to also consider incorporating these issues into any change we are making to the data export format:

• In Form Data, replace "localhost" in URL with actual domain #815
• Quiz results export need some reflection of whether an answer in correct or not #1222
• Including more information about where surveys/polls/quizzes "were taken" in data export #696

We can talk about how important these are vs the effort required.

[cbunicef]

Well build in a period where both formats are supported, add the warning text, and then remove the old format after eg 3 months.

We will put this behind a feature flag while it's in development.