Error in binding data

Hey ,

One thing I can think of (I've done in the past as well) is that You're binding data in the Value section. That's the one that opens first so it's easy to asssume that's where the binding should be done.

Can you confirm in which section you're binding your data? Values or Input Destination?

Hello,  
Thank you for your reply

In Value I choose the field of table and in Input destination I choose the data that will be entered in table.

For instance, I have field Name and in JSON I write Name: "${my_name}",
So in value I choose name and in Input destination my_name

Not gonna lie, I'm having hard time visualizing Your setup through just a description but it sounds like you have your request body ready (JSON part). The confusing part is the data binding.

To POST you don't need to worry about the "Value" section. This is to select data that will be bound to your design elements (will replace your static content with the data from the database; useful for edit page for example)

So Input Destination is the one that You should be interested in. Can you make sure you're binding your data with this in mind:

• JSON is the only place where You mention Airtable column names:
  "Name": "${my_name}"
• Element binding (Input Destination) is where you select your design elements tagged as [input-something] and you tell Bravo to take what user input there and put it instead of the JSON variable:
  "Name": "${my_name}"

There could be a few other things that could go wrong but this should be a good start to figure it out.

Yup, everything is done in such way.
It worked 2 days ago, but now it throws an exception and doesn't work at all

Hmm... some maybe there really is a bug. I've noticed two other users having issues with setups that previously worked and now it doesn't (see here).

Can you mention me in this post when you figure it out or when it starts working again? (I'm curious about what could be an issue)

I solved the issue. It seems to be I tried to send the value in another container using the records, therefore the second container with inputs doesn't work...

Thank you! :)

Ah yes - I had this problem before (see here, point 3)

I think it should to be communicated better that forms need to be contained within one container. I don't think I've seen it anywhere in the docs.

Anyway - I'm glad You've solved it!