BeyondERP.Newsletter
Menu

Setup step on the Delete forecasts page · Project management and accounting

Delete forecast transactions safely

Remove part of a forecast before re-forecasting.

Business process
Plan projects
Menu item
action:ProjForecastBudgetDelete
Setup steps
1 on this page
Show what matters for
SETUP GUIDEHow to set it up8 sections. Choose a role to highlight what matters to you.
Everyone

1What it is and why

What it isA periodic job that permanently deletes forecast transactions from a forecast model, limited to the transaction types and dates you choose.
What you do hereUse it to remove a forecast, or part of one, before you re-forecast. It can't be undone, so copy the model first if you may need the lines again.
ExampleBEAT re-forecasts the second half of 2026. The project manager first copies FC-2026 to FC-2026-ARCH, then deletes the hour and expense forecast transactions dated 07/01/2026 to 12/31/2026 from FC-2026, removing 620.00 forecast hours on PRJ-0042.
Delete forecasts page in Dynamics 365
The page in Dynamics 365. page title tab to open what to set or check
Functional consultant · Solution architect

2Where it fits

Business processPlan projects
Menu pathProject management and accounting › Periodic › Forecasts › Delete forecasts
Set up firstCopy forecasts (archive first) Microsoft Learn
Used next byAll project forecasts Microsoft Learn
Related pagesCopy forecasts to ledger Microsoft Learn Forecast models Microsoft Learn
In this process Copy a forecast model · Transfer the project forecast to a ledger budget
End user · Functional consultant

3How to do it

About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.

When to run it

When to run itWhen a forecast, or part of it, is no longer valid and must be removed before you re-forecast.
How oftenOn demand, when a forecast model is replaced or revised.
Batch settingsRun in the background only for large models; check the selection first.
What the output showsThe forecast transactions of the chosen types and dates are removed from the model. Lines outside the range or of other types stay.

Source: Microsoft Learn

Setup steps on this page

Delete forecast transactions safely

Remove part of a forecast before re-forecasting.

Steps from Microsoft

  1. Go to Project management and accounting > Periodic > Forecasts > Delete forecasts.
  2. If you may need the lines again, first run Copy forecasts into an archive model, because deleted lines can't be restored.
  3. Under Include transactions, select only the transaction types to delete, and enter the From date and To date.
  4. In Forecast model, select the model; don't pick a model that budgets, cost control or the cash flow forecast still read.
  5. Run the job and open Transactions > All project forecasts for that model to check that only the chosen types and dates are gone.

Source: Microsoft Learn

Fields on the page

FieldWhat it meansExample
Include transactionsThe transaction types to delete from the forecast model.Microsoft Learn Hour and Expense
From dateWith To date, the date range of the forecast transactions to delete.Microsoft Learn 07/01/2026 to 12/31/2026
Forecast modelThe forecast model that the transactions are deleted from.Microsoft Learn FC-2026

Common errors and fixes

MessageWhat to do
Forecast lines outside the intended range or of other types are missing.The dates or Include transactions were wider than intended. Load the lines back from the archive model with Copy forecasts; without an archive, they must be entered again. Microsoft Learn

Test checklist

  1. Copy FC-2026 to FC-2026-ARCH.
  2. Delete hours dated 07/01/2026 to 12/31/2026 from FC-2026.
  3. Total the hour forecast of PRJ-0042 in FC-2026 for that range: 0.00.
  4. Total the first half of 2026: unchanged.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Delete forecast transactions safelyArchive the model with Copy forecasts first, then delete by transaction type and date range.The delete can't be undone; the archive is the only way back.What happens to a forecast before it is replaced?Deleting from the model that budgets or reports still read, so their figures drop without warning.Test: Delete half a year of hour forecasts

Feature management and licence

Licence or add-inOn the live system, Project manager, Project accountant and Project assistant use this page.

Checked in Dynamics 365

Solution architect

5Design impact

Shared or per companyPer company: the job deletes forecast transactions of the legal entity you run it in. Microsoft data model
Can it be undoneIrreversible: Deleted forecast lines can't be restored.
If you change it laterDeletes forecast transactions permanently. Reports, cost control and forecast reduction that use the model change at once, and amounts already transferred to a ledger budget aren't removed. Microsoft Learn
Technical architect

6Technical

Menu itemaction:ProjForecastBudgetDelete Checked in Dynamics 365
FormDialog Checked in Dynamics 365
Roles to set it up and use itTo use itProject manager ProjProjectManagerProject accountant ProjProjectAccountantProject assistant ProjProjectClerkGive people one of these roles. On this system, 3 roles can run this page.Checked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=action:ProjForecastBudgetDelete
Data migrationLoad order: Delete forecasts has no data entity in Data management: it is a periodic job and keeps no records of its own. Load forecasts with the forecast entities (for example ProjForecastEmplEntity) and clean them up in the target system.Load first: ProjForecastEmplEntityMicrosoft data model
Everyone

8Sources

To cite this step: PM-JOB-040, Delete forecast transactions safely. Beyond ERP Atlas Hub, 2026-11-11. https://www.beyonderp.cloud/atlas/step/PM-JOB-040