# Do arithmetic for items from # selection

**URL:** <https://forum.bubble.io/t/do-arithmetic-for-items-from-selection/39547>\
**Category:** Need help\
**Created:** [October 9, 2018, 12:42am UTC](https://forum.bubble.io/t/do-arithmetic-for-items-from-selection/39547 "2018-10-09T00:42:55Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![keith](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/keith/32/56020_2.png) [@keith](https://forum.bubble.io/u/keith)\
**Post date:** [October 9, 2018, 2:24am UTC](https://forum.bubble.io/t/do-arithmetic-for-items-from-selection/39547/4 "2018-10-09T02:24:48Z")

</div>

Ah! Ummm… I think I accidentally stumbled upon a workaround for that recently. (But I need to research to re-uncover what that was…)

However, the “non-hacky” workaround is this:

Presumably, API Workflows don’t _need_ custom states as they have the database (perma-storage). So, in the workflow, you can create a new thing (of whatever type you need) and reference its unique ID (via “results of”) to delete it when done with it.

Obviously this slows things down over temporary (in-memory) storage, but it seems Bubble guarantees us no bits in an API Workflow…

Apologies for the vagueness of this answer, but I did stumble across a potential solution (it may have related to unused optional arguments OR “return data from an API”… but I feel like there’s a way to (perhaps unintentionally) set, store and retrieve a value in API Workflows using Results of… a previous step.).

If that’s so, it may be fragile (subject to being fixed as a bug), but currently extant.

---

_[View the full topic](https://forum.bubble.io/t/do-arithmetic-for-items-from-selection/39547)._
