Cost management › Manufacturing accounting › Clean up › Clean up the costing sheet cache
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 it
When the costing sheet cache has grown large, for example after many BOM calculations or price calculations.
How often
On demand, or on a recurring batch schedule that suits how often you run price calculations.
Batch settings
A recurring batch job outside business hours keeps the cache small without manual work.
What the output shows
Costing sheet cache records of the specified age or older are removed. Costing sheets are generated again when needed, so a slower first display afterwards is normal.
No, but the cache is rebuilt: Deleted cache records can't be restored, but they are temporary data that the system recreates when a costing sheet is needed. Microsoft Learn
If you change it later
Deletes old records from the CostSheetCache table; costing sheets are rebuilt on demand. Microsoft Learn
Technical architect
5Technical
Menu item
action:CostSheetCachePurgeJob
Roles to set it up and use it
To use itInventory accountant InventCostAccountantGive people one of these roles. On this system, 1 role can run this page.Checked in Dynamics 365