@Jeffrey Tran
airtable : https://airtable.com/app31qz0B7OLXnQTA/shrLh2w3pU6oQqHKS
Of course, here's an improved version of your response:
I'll refine the Airtable structure while providing some basic examples. Each cocktail will have several variants, and each variant will belong to a specific cocktail.
In other words, in the Figma file, we'll have a section for cocktail categories, one for variants which are subcategories of a given cocktail, and another for details of each variant based on the chosen cocktail category.

2-
Dans Bravo Studio, specifically in "Account Data Collections," I have my APIs to configure:
The API:
- GET Cocktails - list: To list cocktail categories
- GET Cocktails - detail: For details of the cocktail category
- GET Variation - list: To list variation sub-categories
- GET Variation - from Cocktail: To list variations linked to a specific cocktail
- GET Variation - detail: For details of each variant for both "GET Variation - list" and "GET Variation - from Cocktail".
To create the "GET Variation - from Cocktail," simply duplicate that of "Get Variation - list" and add this formula:
?filterByFormula=search('${from_Cocktails}'%2Carrayjoin(from_Cocktails))

3 -
To configure the formula, it depends on your Airtable setup. I focused on the Variations table: I took "from_cocktail" from the Variations table, retrieved from "Cocktails" through the link between the Cocktail and Variation tables to form the following formula: ?filterByFormula=search('${from_Cocktails}'%2Carrayjoin(from_Cocktails)).
Then, in the API collection, you add this formula to the "Get Variation - from cocktail" API. In the value test on the left, you put "from_Cocktails", and on the right as the value, you put "Old Fashioned" since it's in the first position in Airtable.




Then, after sending, check the elements that concern you, change the "ALL" to "0", and then recheck them.

4-
Let's go back to the GET Cocktail - List, more precisely in the data selection. We will change the name or title "Cocktail" to the right of ".data.records[].fields.Cocktail" to from_Cocktails, and that's it.

Here's the result after synchronizing the elements of each screen:
screen-20240319-123402.mp4