# Passing Received Filter/Received Selection Passing to Application

**URL:** <https://community.nextw.com/t/passing-received-filter-received-selection-passing-to-application/1302>\
**Category:** Nextworld Platform\
**Created:** [October 6, 2025, 9:05am UTC](https://community.nextw.com/t/passing-received-filter-received-selection-passing-to-application/1302 "2025-10-06T09:05:28Z")\
**Posts on this page:** 4\
**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:** [October 6, 2025, 9:05am UTC](https://community.nextw.com/t/passing-received-filter-received-selection-passing-to-application/1302/1 "2025-10-06T09:05:28Z")

</div>

Is there any way, currently, of passing a filter / row selection to an application? And if not, is there an idea for such functionality in the pipeline?

Example would be a user selects 5 rows/filters in an advanced list and clicks a row action which navigates to a mini app/another application which loads the selection based on the filter /selection passed in and where they can fill in missing fields - maybe a field is empty on one or two of the lines selected. They can fill it in and proceed.

---

<div class="post-metadata">

**Author:** ![deb.shupe](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/deb.shupe/32/142_2.png) [@deb.shupe](https://community.nextw.com/u/deb.shupe)\
**Post date:** [October 6, 2025, 3:38pm UTC](https://community.nextw.com/t/passing-received-filter-received-selection-passing-to-application/1302/2 "2025-10-06T15:38:31Z")

</div>

I believe you can achieve that using a Lock Block. User selects up to 50 rows OR filters the list to only the rows they need, then on a FORM action, you can use either the received selection OR the received filter in the Logic Block and then queue an app link to the app mini app that you want to navigate to.

---

<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:** [October 7, 2025, 6:09am UTC](https://community.nextw.com/t/passing-received-filter-received-selection-passing-to-application/1302/3 "2025-10-07T06:09:38Z")

</div>

@deb.shupe This sounds great! Will investigate further on the suggestion. Thank you!

---

<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:** [October 8, 2025, 12:09pm UTC](https://community.nextw.com/t/passing-received-filter-received-selection-passing-to-application/1302/4 "2025-10-08T12:09:54Z")

</div>

@deb.shupe The queue app links works perfectly, thank you.

The logic block can see the selection (this part works fine), but how does the selected/filtered results get to the application being queued/navigated to to be loaded/referenced there?