Auto populate/display/update field value based on another field using table data

[nunick]

Is it possible to auto populate/display/update a value of a field based on the contents of another when they share the same row in a table? For example, say I enter in my name into a name field and then the email field below automatically populates/displays my email from a table where both values are stores.

EDIT: I can get a Headline field to auto populate to the same value as selected in an Option Picker on the screen using something like: {{ Form.Fields.Option }} or similar. However, I'd like it to be the email associated with the user, not the user. And instead of an Option Picker and Header, it'd be useful to be able to type any string into one field and then have it populate another.

[mjashanks]

Hi @nunick you can use the Default Value field to do this...

My binding in this image is {{ Form.Fields.Name }} - {{ Form.Fields.Company }}.

So, when I complete the Name and Company fields in the form below, the Description is auto-populated. You can of course override this.

[nunick]

@Deluzionist in my example I'm taking things from Table A (serial number table) that the user filters with a field, add a few new details in a summary field, and then have a save button to save the info from all fields into the form to Table B (maintenance report). This is how I've set up my button:

That being said, I haven't set it up to "update" the cells in Table B if needs, but that's probably best for a different screen to handle.

[Deluzionist]

@nunick Thanks for elucidating. I have tried using just one form as you have done but when I use the handlebar expression {{ dataprovider.Rows.0.columnname }} it will only pull up values if the dataprovider matches the schema chosen for the form.

[mjashanks]

Does this help?

Test.-.5.February.2022.mp4

[Deluzionist]

@mjashanks Thank you! The JS works great however I still can't get the Data Provider filtering to work the way you had implemented the binding {{ Fields.Code }} via Define Filters. The only way I was able to get the filtering to work was by binding the data source query itself the way nunick had implemented via the where column = handlebar expression.
I had even replicated the filtering from https://docs.budibase.com/guides/add-a-dropdown-filter-to-a-table exactly. Any idea what I could be doing wrong?

[mjashanks]

Happy to take a look at your app, if you want to send to support@budibase.com

[melohagan]

Using the default value is the old approach. Default values only apply on load of the screen.

If you want to update one field with the value of another, look at the On Change event in combination with the Update Field Value action