Sometimes you add or change reporting mappings after projects are already running — or finished. This feature lets you apply those reporting updates to historical project and task data in one controlled action, instead of opening projects one by one. You preview what will change first, then apply, so there are no surprises.
When to use
You added reporting mappings to a project template after projects had already launched.
Dashboards or exports look incomplete because older tasks never reported their data.
You're preparing for an audit and need historical records aligned with current reporting rules.
Apply reporting fields retroactively
Open the project template where you want to update reporting fields.
Confirm each relevant task has reporting configured — a resource target, and a date field key where required.
Open the template's options menu and click the retroactive reporting action (for example, Report completions retroactively).
Run the preview (a dry-run scan). You should see: a. Counts of records already aligned (reported/synced). b. Counts of records that still need updates. c. A split by project state (active vs. completed) where applicable.
Review the scope. Confirm the counts match your expectations and cover the intended resource targets: Project, Client, Plan, and Plan Year.
Click the confirm action (for example, Yes, Report). CX updates the records that weren't yet aligned.
Verify the result. You should see success feedback and updated counts showing few or zero remaining unreported records. New task completions keep reporting normally going forward.
You're all set! Your historical data now matches your current reporting configuration.
Options explained
Resource target — where the reported value is written: the Project, Client, Plan, or Plan Year record.
Date field key — the field that stores the completion date. Use date fields for completion-time reporting to avoid field-type mismatches.
Preview (dry run) — counts what would change without changing anything. Run it before every apply.
Best practices
Always preview and validate counts before applying.
Run large historical updates during quieter hours.
Note the before/after counts for your audit trail.
If mappings change again later, re-run the preview before applying another update.
Troubleshooting
I don't see the retroactive update option. Make sure at least one task has valid reporting configuration (resource target, plus a date field key where required). Refresh and reopen the options menu.
Preview shows no records, but I expected some. Confirm you're in the correct template and that the task mappings match the projects you expect to update.
Some records still show as not synced after the update. Re-run the preview to see which resource targets are missing mappings. Fix the configuration, then apply again.
New completions aren't reporting after the run. Check the task's reporting mapping (resource target and field key type), then test by completing a new task. If it persists, contact support with an example project.
Related articles
Advanced Settings
Users and Groups Overview