# Filling the gap between (too) simple tables and structured database : "simple spreadsheets"

**URL:** <https://community.fibery.io/t/filling-the-gap-between-too-simple-tables-and-structured-database-simple-spreadsheets/1140>\
**Category:** Ideas & Features\
**Created:** [November 8, 2020, 10:32am UTC](https://community.fibery.io/t/filling-the-gap-between-too-simple-tables-and-structured-database-simple-spreadsheets/1140 "2020-11-08T10:32:12Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![c.game](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/c.game/32/565_2.png) [@c.game](https://community.fibery.io/u/c.game)\
**Post date:** [November 8, 2020, 10:32am UTC](https://community.fibery.io/t/filling-the-gap-between-too-simple-tables-and-structured-database-simple-spreadsheets/1140/1 "2020-11-08T10:32:12Z")

</div>

Hi,

Each time I’m trying to use the “table” feature which is in the Rich Text fields, to add pretty simple tables, I am either :

- switching back to google sheet because the row management and the lack of formatting (among other things) make it really tedious and limitating to use. So I finish by simply put a link to the google sheet but this is scattering the information, whereas I would love to have all that in Fibery, and 95% of the time I don’t really need advanced “spreadsheet” features like formulas and having multiple tabs.
- trying to limit myself with these features but waste really a lot of time  
=\> in both case, it is quite frustrating

It would be really great if there was a better way to add “non-structured” data in table format, either by :

- enabling to embed Google Sheets directly into Fibery, like Confluence did, and make that searchable of course (which would be one of the main benefits)
- improving a lot the current “table” feature, by adding the most essential “spreadsheet” features, and improving the row/column management (add/delete multiple etc.). I guess that would also mean to allow for larger tables with an horizontal scrolling.

With the unfair advantage in Fibery that this “table” object could also be referenced like any entity.  
Maybe this could even be a new “view” type like whiteboards.

I’m not sure how others do this, but I feel like there is a missing piece here in Fibery,

Thanks,  
Xavier

---

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [November 8, 2020, 3:00pm UTC](https://community.fibery.io/t/filling-the-gap-between-too-simple-tables-and-structured-database-simple-spreadsheets/1140/2 "2020-11-08T15:00:23Z")

</div>

I agree this is a need, and not just in Fibery, but Notion too, which I only mention because the lack of it in these two tools is interesting. So I’m anxious to see if there will be any movement to solve it. For Notion, their upcoming public API _may_ allow for that kind of interaction with Google Sheets that would give you tight enough integration, including search of Sheets content from within Notion. They already have a good embedding system.

For Fibery, given that developing and maintaining spreadsheet-like functionality is probably a bit of a pain (and once they do, it’s another semi-major feature that people will want _more_ features put into), I think I’d rather see them take their existing (and ever-improving) API/integration functionality, and connect to the whole G Suite of tools. This goes a little off-topic of your feature request for a moment, but I think integrating all of G Suite would be really excellent and help adoption and retention in a big way. You’d get:

- Embed G Sheet in Fibery and manipulate directly; ideally the ability to interact with the data in e.g. formula fields, too
- Create Fibery Entity from Gmail, open contents of source email from Fibery entity (e.g. for tasks)
- Attach and view G Drive files in Entities  
And more…

Much of this is already available in tools like ClickUp and it’s very useful indeed!

Combine that with [Embed Views in Rich Text](https://community.fibery.io/t/embed-views-in-rich-text/936) and you’d have a good solution, I think.

---

<div class="post-metadata">

**Author:** ![Ronan\_Le\_Gall](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronan_le_gall/32/1588_2.png) [@Ronan\_Le\_Gall](https://community.fibery.io/u/Ronan_Le_Gall)\
**Post date:** [March 11, 2021, 10:34am UTC](https://community.fibery.io/t/filling-the-gap-between-too-simple-tables-and-structured-database-simple-spreadsheets/1140/3 "2021-03-11T10:34:32Z")

</div>

I confirm that we really need this table object!

---

<div class="post-metadata">

**Author:** ![XLN](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/xln/32/948_2.png) [@XLN](https://community.fibery.io/u/XLN)\
**Post date:** [March 11, 2021, 10:44am UTC](https://community.fibery.io/t/filling-the-gap-between-too-simple-tables-and-structured-database-simple-spreadsheets/1140/4 "2021-03-11T10:44:54Z")

</div>

I agree this is a feature that we’re missing from Fibery right now.  
We tried to onboard our marketing departement, and they have to keep switching between their simple “follow-up tables” in google sheet, and Fibery, and as a consequence the adoption is not great and the content is not up to date.

Some light improvements on the current “table” feature would really help us cover much more usecases of Fibery, where we still have to switch between tables and Fibery.

Must-haves would be for us :

- very strong : ability to have a wider view of the table =\> if it has to be a whole view to obtain that, it’s not a problem
- strong : abity to bulk add/delete cells & rows
- medium : background color of cells

No need for formulas, sorting, filtering etc. But the above feature would already enable us to migrate much more content into Fibery, and smoothen the workflows.

Regarding GSheet (/Google integration), it is an interesting option indeed. However we would then miss the linking with other entities in Fibery, which makes it really less interesting for us.

---

<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:** [March 11, 2021, 11:09am UTC](https://community.fibery.io/t/filling-the-gap-between-too-simple-tables-and-structured-database-simple-spreadsheets/1140/5 "2021-03-11T11:09:40Z")

</div>

Is it important for most people that the functionality is present in

> [@c.game](#):
>
> the “table” feature which is in the Rich Text fields

or would a possible solution come from enhancements of the existing table view plus

> [@Oshyan](#):
>
> Combine that with [Embed Views in Rich Text](https://community.fibery.io/t/embed-views-in-rich-text/936)

?

Personally, I would love for the existing table view to have more ‘Excel-like’ functionality (editing/copy-pasting multiple cells, filtering/sorting using column headings, easier show/hide columns etc.)

---

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [March 11, 2021, 6:07pm UTC](https://community.fibery.io/t/filling-the-gap-between-too-simple-tables-and-structured-database-simple-spreadsheets/1140/6 "2021-03-11T18:07:59Z")

</div>

I wanted to highlight a few related requests out there already:

> [@\[APPROVED\] Wrap Cells & expand Column option in Table View](https://community.fibery.io/t/approved-wrap-cells-expand-column-option-in-table-view/820):
>
> I know we have some table updates with the “batch editing” coming up, very glad to hear about that! On the subject of tables, I wanted to suggest the option to “wrap” the table view. This is a big piece of Notion that I’ve always found very useful. [image] It’s very useful if you want to see your related entities as a small “list” in a table. With Fibery’s sophisticated many-to-one, many-to-many, and one-to-one visuals, this would really give Tables a leg up. Notion can’t benefit here as a…

which is approved, and

> [@Table view Description field / Rich Edit fields in Table View](https://community.fibery.io/t/planned-table-view-description-field-rich-edit-fields-in-table-view/383/5):
>
> +1 to this. Coda I think has it better implemented since the wrap text function can be set per column not entire table. Being able to do something like this will be amazing: [image] I think when the rich text fields will be able to be shown on boards and tables, wrapping can be set at field level.

I’d really like to be able to see the contents of Rich Text Fields in Tables. This is a big benefit of Coda. You can’t do it in Notion, but Notion, unlike Fibery, has good Rich Text formatting in its “simple text” fields, which can be viewed and expanded in Table view. So if Fibery added some Rich Text capability in its “text” simple text fields, that would help a lot, too. What I mean is being able to write bullets, and ideally mention other entities. That request is here:

> [@More "Rich Text" in simple Text Box](https://community.fibery.io/t/more-rich-text-in-simple-text-box/984):
>
> I am trying to set up one of the features of both Coda and Notion that I found very useful and would love to be able to do in Fibery - use a “join” entity to show deep info between other entities. Ideally I’d like to be able to type into this Entity within another, for example during meetings. While we are waiting on the visibility of Rich Text fields within Tables and Collections, from this post: I think it would be very helpful to have some more ability in the “Text Box” Field: Ability …

Thanks!

---

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [March 11, 2021, 6:09pm UTC](https://community.fibery.io/t/filling-the-gap-between-too-simple-tables-and-structured-database-simple-spreadsheets/1140/7 "2021-03-11T18:09:20Z")

</div>

> [@Chr1sG](#):
>
> have more ‘Excel-like’ functionality (editing/copy-pasting multiple cells, filtering/sorting using column headings, easier show/hide columns etc.)

This is great stuff. It’s a nice v.1 of Tables so far in Fibery. Would also like to be able to double-click on a column and have the column auto-scale to the content in the column, also ala Excel…

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [March 12, 2021, 7:31am UTC](https://community.fibery.io/t/filling-the-gap-between-too-simple-tables-and-structured-database-simple-spreadsheets/1140/8 "2021-03-12T07:31:27Z")

</div>

> [@XLN](#):
>
> We tried to onboard our marketing departement, and they have to keep switching between their simple “follow-up tables” in google sheet, and Fibery, and as a consequence the adoption is not great and the content is not up to date.

I think this “follow-up tables” has some structure and most likely they should be moved to some Type in Fibery. What exactly these tables contain?

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [March 12, 2021, 7:41am UTC](https://community.fibery.io/t/filling-the-gap-between-too-simple-tables-and-structured-database-simple-spreadsheets/1140/9 "2021-03-12T07:41:00Z")

</div>

We are not going to improve tables in rich edit views, they should be considered as basic markdown tables for text formatting, not data management.

In our plans we do have an idea to re-work Entity View completely and allow people to mix information better. Here is the hint from Fibery 2.0 vision doc:

 ![Paper.Journal.11 2](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/d/d5e0afe6e38a8928e5d3e7128b4709e66d71a8bb.jpeg)

Basically, every entity view will be just a dashboard for all kind of information: textual, table, diagram, etc.

Another thing that we are going to add is ad-hoc types. You can think about them as freestyle tables and work pretty similar to excel, but under the hood, these are just usual types well hidden from the user (you will not see them in the schema). Thus you will be able to work with Tables freely. We also have to improve the current Table View to make it more functional.

So the solution to your problem in Fibery demands many things:

1. Change Entity View to allow insert Table View and other Views as well
2. Add a possibility to add Table View ad-hoc without any existing Type and create like hidden Type under the hood
3. Improve Table View functionality.

It’s a long path, so please don’t expect it will be done in the next 6 months. But it shows the direction we are willing to move to.

---

<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:** [March 12, 2021, 7:58am UTC](https://community.fibery.io/t/filling-the-gap-between-too-simple-tables-and-structured-database-simple-spreadsheets/1140/10 "2021-03-12T07:58:08Z")

</div>

> [@mdubakov](#):
>
> In our plans we do have an idea to re-work Entity View completely and allow people to mix information better.

😄

> [@mdubakov](#):
>
> don’t expect it will be done in the next 6 months

☹

Seriously though, I’m excited about the possibilities, but I understand that you’re juggling a lot of tasks, and some of the other ones are just as exciting  
👏

---

<div class="post-metadata">

**Author:** ![XLN](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/xln/32/948_2.png) [@XLN](https://community.fibery.io/u/XLN)\
**Post date:** [March 12, 2021, 8:50am UTC](https://community.fibery.io/t/filling-the-gap-between-too-simple-tables-and-structured-database-simple-spreadsheets/1140/11 "2021-03-12T08:50:59Z")

</div>

@mdubakov : Thank you for the detailed answer.

I expected that you would answer that, and honestly I find this “solution set” more powerfull too, so it’s great if you want to go that way.

However, your question raises the main challenge linked to that :

> I think this “follow-up tables” has some structure and most likely they should be moved to some Type in Fibery. What exactly these tables contain?

=\> Yes in principle, but the profile of user here is not one who want to get into the complexity of defining types etc. just to make a table, that they would like to insert in some context (ex: an existing entity).  
So if you go the “hidden Type under the hood” way, this would have to be dead simple/intuitive to create & manage, if you don’t want to loose “basic” users along the way.

---

<div class="post-metadata">

**Author:** ![Lee\_Denny](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/lee_denny/32/8158_2.png) [@Lee\_Denny](https://community.fibery.io/u/Lee_Denny)\
**Post date:** [October 29, 2024, 1:56pm UTC](https://community.fibery.io/t/filling-the-gap-between-too-simple-tables-and-structured-database-simple-spreadsheets/1140/12 "2024-10-29T13:56:45Z")

</div>

I have a use case for this. I want to create a quick budget table to keep track of costs for a given entity. I dont want all the complexity of having to create new databases and formulas so i ended up using a google sheet which is now disconnected from where i want it.

Could there be a new ‘Sheet’ type in fibery that is like a ‘Doc’ and offers basic spreadsheet functionality that can be linked to any entities to allow this work to happen all inside fibery?

---

<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 29, 2024, 2:43pm UTC](https://community.fibery.io/t/filling-the-gap-between-too-simple-tables-and-structured-database-simple-spreadsheets/1140/13 "2024-10-29T14:43:04Z")

</div>

> [@Lee\_Denny](#):
>
> offers basic spreadsheet functionality

I wonder if different users have different ideas about what would qualify as ‘basic spreadsheet functionality’.

I could imagine that each user might only want a small percent of all the features in Excel, but the few percents of maybe not overlapping that much, meaning that Fibery would need to support a lot of stuff to keep a high % of users happy 🤔

What are your needs @Lee_Denny ?

Have you considered embedding an external spreadsheet, so things aren’t quite so disconnected?

---

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [October 29, 2024, 8:43pm UTC](https://community.fibery.io/t/filling-the-gap-between-too-simple-tables-and-structured-database-simple-spreadsheets/1140/14 "2024-10-29T20:43:41Z")

</div>

> [@mdubakov](#):
>
> Another thing that we are going to add is ad-hoc types. You can think about them as freestyle tables and work pretty similar to excel, but under the hood, these are just usual types well hidden from the user (you will not see them in the schema). Thus you will be able to work with Tables freely.

> [@mdubakov](#):
>
> - Add a possibility to add Table View ad-hoc without any existing Type and create like hidden Type under the hood

Was just reminded of this very exciting hint from… 3+ years ago! I guess plans changed? 😕 Is this still something the team hopes to implement at some point?

> [@Chr1sG](#):
>
> I wonder if different users have different ideas about what would qualify as ‘basic spreadsheet functionality’.

IMO the key question is really this: of the many people who have tried Fibery and then not adopted it over the years, how many of _them_ would have stayed if it had more spreadsheet-like functionality built-in? Perhaps a difficult question to answer, but you could start by asking people in the wider world, on Twitter, on Reddit subs, as well as in any kind of “lost customer” workflows/follow-ups you have going (abandoned workspace, deleted workspace, etc.).

And yes, of course the same concern may apply: that there isn’t enough overlap in what people want. But I don’t think that is likely to be true for the simple fact that Excel and its near-exact copies (Google Sheets, etc.) are considered to be _the_ universal, Swiss Army Knife tool of all computer work (aside from text/MS Word, of course). And you surely have to know, as I do, that \>80% of the people using it are complete non-experts in it; they just want “good structured table and number formatting” or “table + simple formulas”, etc. It’s not like most of them are trying to run Excel VB scripts, tallying multiple Sheets together, doing Pivot Tables, etc.

---

<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 29, 2024, 9:09pm UTC](https://community.fibery.io/t/filling-the-gap-between-too-simple-tables-and-structured-database-simple-spreadsheets/1140/15 "2024-10-29T21:09:18Z")

</div>

> [@Oshyan](#):
>
> they just want “good structured table and number formatting” or “table + simple formulas”, etc.

It’s the ‘simple formulas’ part that I think is the issue. Given that Excel has hundreds (maybe thousands?) of formulas, I would not be surprised to discover that the venn diagram of ‘simple formulas’ as defined by all Fibery users is quite a large area.  
Who knows?

FWIW Michael’s posts were from before my time at Fibery, so I can’t comment on why the suggested ideas never came to fruition.

> [@Oshyan](#):
>
> Perhaps a difficult question to answer, but you could start by asking people in the wider world, on Twitter, on Reddit subs, as well as in any kind of “lost customer” workflows/follow-ups you have going (abandoned workspace, deleted workspace, etc.).

We always contact users of abandoned workspaces and those who churn to find out their reasons, and this is not often mentioned (I can’t recall anyone naming it specifically during the 3+ years I’ve been working for Fibery).

---

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [October 29, 2024, 9:24pm UTC](https://community.fibery.io/t/filling-the-gap-between-too-simple-tables-and-structured-database-simple-spreadsheets/1140/16 "2024-10-29T21:24:38Z")

</div>

> [@Chr1sG](#):
>
> It’s the ‘simple formulas’ part that I think is the issue. Given that Excel has hundreds (maybe thousands?) of formulas, I would not be surprised to discover that the venn diagram of ‘simple formulas’ as defined by all Fibery users is quite a large area.

Ever the pessimist 😄 I may be foolish, but I would be willing to stake a decent chunk of money - let’s call it $1000 - that the total number of “functions” ~80% of people need in formulae is under 20. I wouldn’t be shocked if it were literally 10 or fewer. The biggies pull most of the weight: basic math (add/subtract/etc.), averaging of various kinds, date handling, etc. Fibery’s existing formula capabilities (that are of course not usable on-page) are far more than enough. Take out _all_ of the database interaction stuff (although it would be amazing to have that in-line, on-page, it’s _not_ a prerequisite for significant utility here IMO!), and maybe you start to see a better idea of a core set of functions.

> [@Chr1sG](#):
>
> We always contact users of abandoned workspaces and those who churn to find out their reasons, and this is not often mentioned (I can’t recall anyone naming it specifically during the 3+ years I’ve been working for Fibery).

I’m not surprised, but that doesn’t mean it wasn’t of interest or a factor. It’s also a very small sample size, which is why IMHO proactive data gathering from non-users is so potentially valuable.

---

<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 29, 2024, 10:20pm UTC](https://community.fibery.io/t/filling-the-gap-between-too-simple-tables-and-structured-database-simple-spreadsheets/1140/17 "2024-10-29T22:20:43Z")

</div>

> [@Oshyan](#):
>
> I’m not surprised, but that doesn’t mean it wasn’t of interest or a factor.

If it was a factor in their decision making, why would you think that they wouldn’t mention it?

> [@Oshyan](#):
>
> which is why IMHO proactive data gathering from non-users

How many people do you imagine would respond to a tweet/reddit post that said, “Please tell us if you would be more likely to use Fibery _(a tool you’ve never heard of)_ if the rich text fields supported Excel-like tables for simple formula calculations”?

> [@Oshyan](#):
>
> I would be willing to stake a decent chunk of money - let’s call it $1000 - that the total number of “functions” ~80% of people need in formulae is under 20. I wouldn’t be shocked if it were literally 10 or fewer.

Maybe you’re right, but why would Fibery develop support for this functionality (and take away developers from other features) when this topic has had 2 votes in 4 years, and almost zero churned customers have mentioned it as a reason for leaving?

> [@Oshyan](#):
>
> Ever the pessimist 😄

You got me!  
But I like being a pessimist - I’m either right, or pleasantly surprised.

---

<div class="post-metadata">

**Author:** ![Lee\_Denny](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/lee_denny/32/8158_2.png) [@Lee\_Denny](https://community.fibery.io/u/Lee_Denny)\
**Post date:** [October 30, 2024, 12:38pm UTC](https://community.fibery.io/t/filling-the-gap-between-too-simple-tables-and-structured-database-simple-spreadsheets/1140/18 "2024-10-30T12:38:45Z")

</div>

> [@Chr1sG](#):
>
> basic spreadsheet functionality

Basic maths only. My use case was creating a quick 10 line budget for an entity that could then be kept up to date as the entitiy progresses through its workflow.

> [@Chr1sG](#):
>
> embedding an external spreadsheet

Yes i did this in the end with a google sheet, but i think it can create some issues when the person viewing the entity doesnt have permission inside google. Could be solved by some kind of permissions alignment with google like when you share a doc in slack and it tells you if people dont have access and offers to update the permissions without too much work from the user.

---

<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 30, 2024, 3:54pm UTC](https://community.fibery.io/t/filling-the-gap-between-too-simple-tables-and-structured-database-simple-spreadsheets/1140/19 "2024-10-30T15:54:04Z")

</div>

> [@Lee\_Denny](#):
>
> Could be solved by some kind of permissions alignment with google like when you share a doc in slack and it tells you if people dont have access and offers to update the permissions without too much work from the user.

Not sure if/how that could work. I assume it would require Google Drive to know which users exist in your Fibery workspace, whenever you create a sharing link for an asset in GDrive.

---

<div class="post-metadata">

**Author:** ![Jonathan1](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jonathan1/32/10038_2.png) [@Jonathan1](https://community.fibery.io/u/Jonathan1)\
**Post date:** [November 16, 2024, 9:15am UTC](https://community.fibery.io/t/filling-the-gap-between-too-simple-tables-and-structured-database-simple-spreadsheets/1140/20 "2024-11-16T09:15:19Z")

</div>

Adding my vote here and related request.

> [@Enhance "Text Table" capabilities](https://community.fibery.io/t/enhance-text-table-capabilities/7804):
>
> Hi, I have some suggestions for improving the Text Table block. Be able to use Formulas inside the Text Table. Be able to link a field of the entity to a cell of this Text Table (Can be a Formula field). A use case could be an entity that describe the cost of an item. Then the result of this calculation is reported on a field of the identity. With that, I will be able to use this result on Formulas across the related entities.

[Next page](https://community.fibery.io/t/filling-the-gap-between-too-simple-tables-and-structured-database-simple-spreadsheets/1140.md?page=2)
