In database view when using a table within an attribute - whether in a gift record, constiuent record etc. If the attribute you're using contains a table you are able to type in a new entry and when you click away it will ask if you want to add that new value to the table. This is so convenient. In webview you have to exit the the page you're working on, go to settings >table>find the table > add the new entry, and then go back to your attribute and scroll down and find it. I know it seems like something small but it is little things like this that make database more intuitive. I am suprised this wasnt considered when moving tables into Webview
I completely agree with this request. Adding a new table value on the fly—right when you realize you need it—is a small but meaningful efficiency in Database View that keeps data entry moving. Having to leave the record, go to Settings, find the table, add the value, and then return creates unnecessary friction for back‑office users.
WebView really needs parity here, with appropriate security controls so only the right users can add new values. That way we keep the workflow efficient without compromising table integrity or introducing accidental clutter.
I didn't realize that webview didn't already have this feature. This is such a critical piece of functionality for data entry. This is functionality we use constantly in database view for table values and I highly encourage you to allow parity to database view for this. This is yet another example of webview's UX creating extra steps and extra clicks for back-office users. Please streamline this so that it works the same in database view and webview.