# Create and Manipulate Collection in Formula

**URL:** <https://community.fibery.io/t/create-and-manipulate-collection-in-formula/5277>\
**Category:** Get Help\
**Created:** [October 11, 2023, 4:52am UTC](https://community.fibery.io/t/create-and-manipulate-collection-in-formula/5277 "2023-10-11T04:52:18Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![njyo](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/njyo/32/923_2.png) [@njyo](https://community.fibery.io/u/njyo)\
**Post date:** [October 11, 2023, 4:52am UTC](https://community.fibery.io/t/create-and-manipulate-collection-in-formula/5277/1 "2023-10-11T04:52:18Z")

</div>

As far as I can see, I am not able to manipulate and output Collections in formulae. They seem to always have to be converted into strings with a `Join()` function? I would like to calculate connections through a formula ~~rather than an Automation~~ :

So I am modelling my component library in Fibery. It consists of:

1. Products (e.g. Mobile App, Web App, etc.)
2. View Templates (e.g. Mobile Base, Mobile Login, etc.), which belong to a Product
3. Views (e.g. Login, Dashboard, etc.) using a View Template
4. Components (e.g. Navigation, Listing, List Item) which can be nested

A Component can be placed inside another Component, a View or a View Template. I would like a Component to display in which Products it is used, hence a formula that does kinda the following (pseudocode):

```auto
Products = [View Templates].Products + [Views].[View Templates].Products
Products += [Parent Components].Products // Note: yeah, simplified the nesting recursion here
Products.FilterUnique()

```

Is there any plans adding Collection manipulation in formulae?  
Thanks!

Edit: Automation actually cannot solve my problem either.

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [October 11, 2023, 7:50am UTC](https://community.fibery.io/t/create-and-manipulate-collection-in-formula/5277/2 "2023-10-11T07:50:58Z")

</div>

It sounds like you would like a [‘union’ function](https://community.fibery.io/t/how-to-union-two-list-fields-in-the-same-database/2467), for combining collections. It’s not yet possible, but we have the feature in the backlog

---

<div class="post-metadata">

**Author:** ![njyo](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/njyo/32/923_2.png) [@njyo](https://community.fibery.io/u/njyo)\
**Post date:** [October 11, 2023, 8:17am UTC](https://community.fibery.io/t/create-and-manipulate-collection-in-formula/5277/3 "2023-10-11T08:17:12Z")

</div>

Thanks @Chr1sG, yes, hadn’t found that thread. Added my comment there.

---

<div class="post-metadata">

**Author:** ![Jan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jan/32/14975_2.png) [@Jan](https://community.fibery.io/u/Jan)\
**Post date:** [October 2, 2026, 10:15am UTC](https://community.fibery.io/t/create-and-manipulate-collection-in-formula/5277/4 "2026-10-02T10:15:21Z")

</div>

@Chr1sG I’m wondering, is this feature still on the backlog? We’re running an automation to autopromote tasks from the backlog if they were forgotten (unironically this is our use case); tasks that are still in state “Backlog” get a label “Needs Refinement” attached when being promoted. This is where union on collections, or in general adding to a collection comes into play. At the moment our workaround is a script, but given how simple the task actually is I’d prefer using just a Fibery formula.

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [October 2, 2026, 11:10am UTC](https://community.fibery.io/t/create-and-manipulate-collection-in-formula/5277/5 "2026-10-02T11:10:52Z")

</div>

> [@Jan](#):
>
> is this feature still on the backlog

Still in the backlog, but also still no ETA, sorry