Skip to main content
← Data, API & Backend
Data, API & Backend Solved November 17, 2022 · 4 replies

Post Request Binding does only work for 4/5 variables

Archived from the Bravo community forum (2021–2026). Some answers may refer to older versions of Bravo.

Hi guys,

within the last two days I got stuck with the data binding. I proceeded the post request process as shown in the docs and everything worked out well - so far so good. But at the final step, the binding, one variable was, and still is, missing. Since everything is set up identically, I have no clue where the mistake is.

This is the Adobe XD file with the post requests for:

  1.  #teamname (works)

  2. #kaufpreis (works)

  3. #anzahl (works)

  4. #gültig bis (works)

  5. #user (does not work)

    Bildschirmfoto 2022-11-17 um 12.55.23.png

    Since I can display the correct options for the input-select, but only can not choose the user for the input destination. When I open the app in Bravo Vision, I also can select the correct User, but only the post to the API won´t be performed.

    1.  #teamname = team (works)

    2. #kaufpreis = preisproaktie (works)

    3. #anzahl = anzahl (works)

    4. #gültig bis = datum (works)

    5. #user = verkäufer (not shown below)

      Bildschirmfoto 2022-11-17 um 13.04.44.png

      The body JSON from the post request looks like this:
      {
        "records": [
          {
            "fields": {
              "Team": "${team}",
              " Preis / Aktie": "${preisproaktie}",
              "Anzahl der Aktien": ${anzahl},
              "Verkäufer": "${verkäufer}",
              "Gültig bis": "${datum}"
            }
          }
        ]
      }

I also put in the corresponding test values and when I run the test, all the correct values appear in airtable, also the 5. one (user/verkäufer).

I have set up everything again and again and really have no idea what else to do. Does anybody of you had a similar problem or sees a mistake I made?

Highly appreciate your support!
Tobi

4 replies

Florian November 18, 2022

I'm interested to know also. 
I don't have all the variables in the input destination and I am curious to understand why.

Tobias November 28, 2022

Quick update: I got a response from the Bravo Studio team. The problem came up due to the "Umlaut" "ä" within the variables.

Wrote something in this thread and want it removed? Request removal

Still stuck?

Ask the community on Discord

This archive is read-only. New questions, office hours and product updates now happen in the Bravo Discord.

Join the Discord