Make field/column in table required when editable

💬 Feature Requests
1

I have adding a new record to the table and bulk update all working with one exception. I would like to be able to set certain columns (fields) to be required. I do get an error back from the database when Not Null fields are not filled in, but it is gibberish to the users.

I suppose I could add Failure Conditions to the query to parse the error and translate it for the user.

Or I could fire a JS query to validate the record before triggering the insert/update queries.

Is there a cleaner way to do it?

2 Likes
2

I can’t think of a cleaner way to accomplish this at the moment, adding a “required” option to the column settings would be an awesome feature here.

Another hacky option to add ontop of this in the meantime would be some CSS to disable the save changes button based on evaluating some of the values in table.recordUpdates like this:

https://downloads.intercomcdn.com/i/o/313561273/0e99c04125fd8d2034f1009b/Mar-18-2021+18-57-22.gif?expires=1618711200&signature=0efdefc11221703b22e416c763750d6d749099a17daa70a0053f697e5e7cb9a4(image larger than 4096KB)
CSS here:

<style>
  {{ table1.recordUpdates.map(row=>row.sales).filter(Boolean).length?  
``: `#retool-widget-table1 > div > div.WidgetBoundingBox__widget > div._retool-table1 > div > div > div > div > div:nth-child(2) > div > div.-left > button.ant-btn.ant-btn-primary {
    pointer-events: none;
    background-color: grey;
    color: lightgrey;
  }`
  }}
</style>
3

I’m going to go ahead and move this to the feature request section for the moment, this does seem like something that should be supported as a column setting.

2 Likes
4

+1 here. Also, it would be great if the users could see which field is mandatory before triggering the update. Like in some MySQL clients showing * beside the name of not null columns.

5

Noted, thank you!

6

Has this feature been added?

7

Hey @rgupta! Not yet, but I added your +1 to the internal feature request and will keep this thread updated with any changes :slight_smile:

8

Hi, @victoria is there an ETA on this?
Thanks

9

@Dataland I've surfaced internally that there's additional interest in this!

In the meantime, something that could potentially get you closer to creating a required field/column functionality:
This topic was originally about the legacy Table component, before Table was revamped a bit over a year ago. The new Table has an option to add logic to disable the save button dynamically. One workaround could be to write some custom javascript to disallow saving changes when certain info is missing:
image

We'll update this topic here if building this into the product in a more integrated way is prioritized for the near term by our product team!