# Create a dynamic document

**URL:** <https://community.fibery.io/t/create-a-dynamic-document/10332>\
**Category:** Get Help\
**Created:** [February 2, 2026, 6:23pm UTC](https://community.fibery.io/t/create-a-dynamic-document/10332 "2026-02-02T18:23:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![manuelwill](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/manuelwill/32/13602_2.png) [@manuelwill](https://community.fibery.io/u/manuelwill)\
**Post date:** [February 2, 2026, 6:23pm UTC](https://community.fibery.io/t/create-a-dynamic-document/10332/1 "2026-02-02T18:23:32Z")

</div>

I have a database consisting of multiple entities which all have a description.

Is there a way to create a dynamic document which only takes a field as a heading then the description of the entity and puts all of in one single long document?

Use Case:

- In some meetings its easier to go through the descriptions with clients without switching entities on a Board.

**Wait a minute** - just figured out there is a Feeds view. I’m almost there. Its basically what I see there, only without the card look.

Man, so much to unpack in Fibery. Am i missing what I’m requesting here?

---

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [February 2, 2026, 8:28pm UTC](https://community.fibery.io/t/create-a-dynamic-document/10332/2 "2026-02-02T20:28:14Z")

</div>

Hey Manuel!

I think Feed View is the closest to what you’re looking for without getting complicated.

If you need it to be in one document, you can make a “Meeting Type” or “Client” database which have a to-many relation to your “Meeting” database. Then have an automation that get triggered when a meeting is linked to the client/meeting type which has a Script action that updates the description to be a consolidation of all the meetings descriptions into one description.

I’m not a big fan of this though because users might try to edit/comment the client/meeting type description, which will just get overwritten once a new meeting is added/linked.

Let me know if that makes sense or if you have questions!