New v3 for Analytics Report

[jesusfer]

Title

Updated Analytics Report.

Type of Change

• New feature
• Bug fix
• Documentation update
• Refactoring
• Hotfix
• Security patch
• UI/UX improvement

Description

This PR aims to update the Analytics report and make it lighter in the Power BI service by:

• Reducing the number of tables loaded in the data model. Remove the unpivoted activities table from the model.
• Use query folding in Power BI to join tables in SQL rather than in Power Query.
• Add incremental refresh to the metrics tables.
• Use measures in the matrix and not an unpivoted table to help the engine work faster.

Breaking changes

Once this PR is merged:

• Profiling stored procedures will stop updating the profiling.ActivitiesWeekly table so previous versions of the report will be degraded.
• Customized reports should be updated to use the new data model provided measures and tables. Many will have been removed.

Related issue(s)

• N/A

Check list

• Related issue / work item is attached
• Changes are tested
• Tests are written (if applicable)
• Documentation is updated (if applicable)

Pending changes

• Update the report data model
  • 1. Activity metrics
  • 2. Usage metrics
  • 3. Example KPIs
• Update SQL stored procedures

[sambetts]

Triage note from #275.

Thanks for this report-model v3 work. Current state from GitHub:

• Draft PR, opened 2026-05-28 and last updated 2026-07-21.
• Targets dev and is currently mergeable, but blocked because it is still draft.
• Scope is additive: new Analytics_DataModel_v3_base.pbit, new dax_helpers.ipynb, and README updates.
• The PR body says the intended report model removes the unpivoted activities table, relies more on SQL/query folding, adds incremental refresh, and moves matrix logic into measures.
• It also says SQL stored-procedure updates are still pending and that older/custom reports may be affected because profiling.ActivitiesWeekly would stop being updated.

This looks potentially salvageable, but it should not land as-is while the SQL/profiling side is still marked pending. To revive it, I think it needs either:

1. a completed end-to-end PR with the required profiling SQL/report-model changes, refresh validation, and upgrade documentation; or
2. a narrower split where the PBIT/helpers/docs are kept as a non-breaking preview and the profiling change is handled separately.

Could you let us know whether you want to bring this up to date and mark it ready for review, or whether you would prefer to close it and reopen a smaller replacement later?