New in Docs: smarter data entry & validation

Happy Friday!

We’re wrapping up several weeks of QoL improvements for Tables, with new features focused on smarter data entry and validation. We hope these will reduce friction, prevent incomplete entries, and cut out manual workarounds.

Here’s what’s new:

1. Reaction vote limits

Set a maximum number of reactions per person on a reaction column. Once someone hits the limit, the reaction is automatically disabled for them… no more custom formulas to do this manually!

Now, just choose “User reaches their reaction limit” from the Disable if setting and pick a number. Everyone gets that many votes to spend across the column.

2. Better date pickers

Jump straight to any month or year from a dropdown, instead of clicking through one month at a time.

No more clicking the arrow over and over to reach a date that’s months away, or hunting for the X to clear a field.

3. Button confirmation modal

Add a confirmation step to any button so collaborators can give an explicit go-ahead before it runs.

You can customize the confirmation message and the cancel/continue button copy, and preview the modal before publishing. Note: the confirmation applies only to direct clicks and won’t appear when an automation pushes the button or when one button triggers another.

4. People columns default to the creator

Default a people column to “Created by,” or pick a specific person, right from the Default value dropdown.

Before, there was no built-in way to default to the row creator, and now it’s a single dropdown pick.

5. Add row as form

Configure the new row button to open a form, so rows are added only when someone explicitly clicks Save. Make sure no more half-filled entries are left behind.

Note: dismissing requires hitting Cancel, not just clicking away.


We hope these updates over the last several weeks make building in Docs feel a little more polished and a lot less manual.

Go try these out and let us know what you think in the comments!

29 Likes

Awesome QoL updates! :clap:

6 Likes

How many of these changes are still human-made? You’re showing an incredible pace these days — congrats!

5 Likes

We had a big list of things we wanted to do for a while, and were so pleased to get to ship around 26 features (so far!) over the last 5 weeks or so. Hoping you’re loving them.

11 Likes
  1. is massive! Can we have it for “Add new row” buttons on the tables too?

The rest are great too! Keep them coming :slight_smile:

3 Likes

Really great stuff, huge!

2 Likes

You guys have been KILLING IT with QOL lately… gone are the days of helper tables for button modals. Well, maybe, I have yet to try it. But I’m guessing so. Thanks team!

3 Likes

Now we are seeing some real pain point breakers. Awesome! And thank you!

For feature 5 (Open in form), it seems to be possible only with the table top button. It would be great to be able to do it with the canvas button using the Activate(AddRow()) formula.

In my case, I always hide the table top and button new row buttons and only create Canvas buttons, because I can make them bigger, centred, and use more advanced formulas with prefilled fields, etc.

8 Likes

I appreciate the date picker update!

1 Like

Thank you - really love seeing all these QoL improvements recently. The small things really do add up to make a difference.

2 Likes

3. is one of those didn’t know it was needed until we saw it. Now its there that’s such a good change for workflow confirmations, approvals and more.

Regarding 2. Great change. If I may as well while on the subject of date entry QoL - one thing I have noticed for new users expected behaviour vs actual behaviour.

Behaviour: User clicks into a date column to select a date, brings up the date picker, but then doesn’t select a date (clicks away)

Expected behaviour - no date should be entered because the user didn’t “select” the date.
Actual behaviour - simply bringing up the date picker automatically enters the current date - even if the user doesn’t actually “select it”.

Seen this catch a few people out - including me (user over many years) and can contribute to bad data quality - so thought I would flag just in case.

4 Likes

Great improvements overall. One question @Ruggy-Joesten : is the expected behavior that Add row as form only works for table views?

The same option does not appear if I’m in, for example, Calendar view:

Cheers

4 Likes

We started with Table views, but I’ll share that request with the team!

4 Likes

Some of these are so great that I have to find the time to go use them everywhere :slight_smile:

1 Like

The amount of non-AI related updates recently has been amazing.

3 Likes

Feature 5 (“Open in form”) isn’t working for me. I configure it and fill out the form, but the new row isn’t created. Is anyone else having this problem?

The datail view also misses the form… Would be very nice to have, at least, validation features in a detail view layout…

1 Like

Thank you for the new improvements :slight_smile:

I think #5 should have been the default all along, as many of my users create empty rows almost daily. But currently it is missing the option to select which layout to use! It took me a while to figure out that changing the “add new” layout uses the current detail layout, which unfortunately breaks some flows as often we start with a minimal data set for new rows and then fill in missing data later. In the current setup if I want a minimal “new” form the “edit” view is also minimal.

Tl;DR please make the new form and edit layouts separate.

4 Likes

This would be awesome to be able to add to a formula. Also the ability to prefill the form would be really helpful.

1 Like

Building on this — why not define validation at the column level once and for all? That way, data entry quality control would be enforced consistently regardless of how the table is being viewed: grid, detail view, form, or a card layout. Right now the rules seem tied to the entry surface rather than to the data itself, which means the same column can accept invalid values depending on where you happen to type it. Column-level validation would solve the detail view gap mentioned above, plus every other view, in one go.

6 Likes