If we have a process which needs to delete a large number of records, what is the best approach to follow (performance wise) e.g. Chunk Fetch and delete in a new transaction, do it in batches in new transactions, fetch and delete, background task, etc?

I would recommend configuring a Data Purge Definition for this purpose. Are you invoking this manually or is it happening via logic?

[image] ian.p: Are you able to invoke this manually or is it happening via logic? @ian.p At the moment, it would be kicked off in some cases with a row action/form action or via a logic block when certain conditions are met.

It’s fine to execute a Data Purge by calling the same logic block that is available on the Data Purge Definition app as a row action or from a logic block directly from elsewhere. However, do the purge criteria change dynamically or can a static purge definition be set up once and then repeatedly in…

It would be dynamic, @ian.p and not something we can standardise/define once off.

Best Logic Approach for Mass Deletes

Nextworld Platform

brendan.b September 26, 2025, 2:10pm 6

See guidance posted here.

Topic		Replies	Views
Handling Large Scale Deletions Nextworld Platform	4	39	March 26, 2026
How well does NW handle deletion of HD entries where a particular header has a very large amount of detail lines Nextworld Platform	1	37	December 2, 2025
Best Practice for Batch Processing of 200K Customer Records Nextworld Platform	11	76	September 10, 2025
Flat Report Data Purge Group Questions Nextworld Platform	1	12	January 22, 2026
Deleting a record in a subtable while loop the subtable records Nextworld Platform	2	41	October 17, 2025

Best Logic Approach for Mass Deletes

Related topics