# Not possible to set selection based on Action Variable in app

**URL:** <https://community.appfarm.io/t/not-possible-to-set-selection-based-on-action-variable-in-app/2438>\
**Category:** Bug reports\
**Tags:** actions\
**Created:** [September 16, 2026, 11:25am UTC](https://community.appfarm.io/t/not-possible-to-set-selection-based-on-action-variable-in-app/2438 "2026-09-16T11:25:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lavrans](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/lavrans/32/1460_2.png) [@Lavrans](https://community.appfarm.io/u/Lavrans)\
**Post date:** [September 16, 2026, 11:25am UTC](https://community.appfarm.io/t/not-possible-to-set-selection-based-on-action-variable-in-app/2438/1 "2026-09-16T11:25:39Z")

</div>

I manage to read to datasource based on the same property

Logic agent seems to know this is not possible:

> Set Selection-noden filtrerer mot action-variabelen “Beginning of month” via ` __BUILTIN_ACTION_VARIABLES__ DS__`. Den datakilden finnes ikke i klientens data-lag når Set Selection evaluerer filteret, derfor `undefined.getSingleObject()`. Bruk en App Variable med samme dato – eller dropp filteret, siden Read Objects allerede har begrenset [Sales (temp)](https://community.appfarm.io/zen/apps/3wJCPs/data/vTzwLk).

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/appfarm/original/2X/b/bdfe96b05e2f30123d5768f8d4147a852cfe69ee.png)

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/appfarm/original/2X/4/4b2cbfe8b3c1fc742b5bdcd95f73b23bcc5ed632.png)

---

<div class="post-metadata">

**Author:** ![Malin](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/malin/32/1634_2.png) [@Malin](https://community.appfarm.io/u/Malin)\
**Post date:** [September 21, 2026, 4:33pm UTC](https://community.appfarm.io/t/not-possible-to-set-selection-based-on-action-variable-in-app/2438/2 "2026-09-21T16:33:27Z")

</div>

Hi Lavrans,

Thanks for reporting this. I managed to reproduce it, and I’ve now logged a challenge on this.

In the meantime, the workaround holds: copy the value into an App Variable and filter Set Selection on that instead.

Malin