# Flat Report Data Purge Group Questions

**URL:** <https://community.nextw.com/t/flat-report-data-purge-group-questions/1628>\
**Category:** Nextworld Platform\
**Created:** [January 22, 2026, 4:17am UTC](https://community.nextw.com/t/flat-report-data-purge-group-questions/1628 "2026-01-22T04:17:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![claire.minnaar](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/claire.minnaar/32/199_2.png) [@claire.minnaar](https://community.nextw.com/u/claire.minnaar)\
**Post date:** [January 22, 2026, 4:17am UTC](https://community.nextw.com/t/flat-report-data-purge-group-questions/1628/1 "2026-01-22T04:17:37Z")

</div>

If one was to define a table as being part of the _Flat Report Data_ purge group, please could you let me know the following:

- Must the table form part of a report execution or can it be a standalone table which just needs to be purged regularly?
- Can I confirm the purge runs every 72 hours still (basing this on this thread: [How long are report executions retained?](https://community.nextw.com/t/how-long-are-report-executions-retained/537))
- What is the criteria of the Flat Report Data group i.e what is the filter to determine which records will be purged (if any)? When the purge runs, does it clear the entire table or based on the age of the record?
- I didn’t see the Flat Report Data purge group in the list of Purge Configuration Setup app - can I confirm it will still run as it’s a NW delivered group?

Thank you.

---

<div class="post-metadata">

**Author:** ![brendan.b](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/brendan.b/32/269_2.png) [@brendan.b](https://community.nextw.com/u/brendan.b)\
**Post date:** [January 22, 2026, 3:16pm UTC](https://community.nextw.com/t/flat-report-data-purge-group-questions/1628/2 "2026-01-22T15:16:18Z")

</div>

I _believe_ that what you’re suggesting will work, but as you’ve noticed, it’s very opaque and isn’t exactly how the purge group was intended to be used.

The recommended approach would be to use Data Purge instead. In the app “Data Purge Definitions”, you can set up instructions for purging your table. To make it run regularly, you can then set up a “Job Scheduler” to execute the logic block `DataPurgeExecutePurgeWrapper` against your data purge regularly. This way, you can control exactly when and how the data is purged.

Going forward, I expect this to be the recommendation for all purges, even ones that would have previously fallen into the “purge group” use case.