# \#NATE

**URL:** https://community.nextw.com/tag/nate/20.md

[Latest](https://community.nextw.com/latest.md) · [Categories](https://community.nextw.com/categories.md) · [Tags](https://community.nextw.com/tags.md)

---

## [Large Data Background Save Example](https://community.nextw.com/t/large-data-background-save-example/1711)

<div class="topic-metadata">

**Author:** [@keiko.kasho](https://community.nextw.com/u/keiko.kasho)\
**Replies:** 5\
**Last updated:** [February 12, 2026, 4:23pm UTC](https://community.nextw.com/t/large-data-background-save-example/1711 "2026-02-12T16:23:04Z")

</div>

Hello, can someone please provide an example where we have an app that uses large data background save and explain why we use it for that use case?

---

## [Sequence of logic block executions on multi-step table transactions](https://community.nextw.com/t/sequence-of-logic-block-executions-on-multi-step-table-transactions/253)

<div class="topic-metadata">

**Author:** [@tyler.pham](https://community.nextw.com/u/tyler.pham)\
**Replies:** 1\
**Last updated:** [May 12, 2025, 3:05pm UTC](https://community.nextw.com/t/sequence-of-logic-block-executions-on-multi-step-table-transactions/253 "2025-05-12T15:05:41Z")

</div>

We have this topic in NW help that outlines the order of operations for actions blocks and triggers for standalone tables and HD tables. In general, the order goes Action Block \> Pre Trigger \> table insert/update/delete \>…