How Should the Table Field Evolve? Your Call! 🚀

Prismic Administrative Support Features
1

Hey Crafters!

We're exploring ways to make the Table Field in Prismic even more useful and intuitive for you. If you've got specific needs, cool ideas, or suggestions, we'd absolutely love to hear them! :rocket:

Whether it's new functionalities you're dreaming of or improvements to the current Table Field, your feedback will shape the next steps.

Note: If you are encountering a bug, please contact support instead.

Here's a handy template to structure your suggestions:

Feature Name:
Give it a short, clear name.

Description:
Quickly explain what the feature does.

Impact/Benefit:
Share how this feature would improve your workflow or benefit other users.

Can't wait to read your suggestions! Let's make this happen together. :sparkles:

Cheers,
Ben

1 Like
2

Hey @benjamin.martin, we urgently need a table with more than 50 rows. Anything we can do about this?

3

Hey @kris1,

May I ask, what’s your use case? We explicitly put this limit in order to avoid performance issues on the Page Builder.

4

Hey @benjamin.martin, it’s just a roadmap table and the company has more than 50 rows within that table

5

Hey @kris1,

Thanks for the clarification.

In our current architecture, tables above 50 rows create noticeable performance issues in the Page Builder, and that’s the main reason this limit exists. Lifting it globally would impact all users, not just this use case.

For now, the best option is still to split the data into smaller logical tables, even if that’s not ideal for your setup. We’re keeping an eye on this constraint, but there’s no safe way to raise the limit today without degrading the experience elsewhere.

Happy to log your request so we can reassess once we work on the next iteration of the Table feature.

6

Thanks @benjamin.martin for the reply - I totally understand. I was able to find a workaround for now.