This is unnecessary and inefficient in Bubble. It means every time you want to get a thing you have to Do a search for (unique ID):first item… it’s inefficient from a performance perspective, and from an editing perspective. More details here:
Primary keys / foreign keys don’t exist in Bubble really. Well, behind the scenes they obviously do, but Bubble treats it differently (and I think they do it quite well).
You rarely need to use ‘ids’ in Bubble. The primary key of a Thing is it’s unique ID. But you don’t save that unique ID to a different thing to connect it, you just save the actual Thing. Yes, it sounds weird if you’re familiar with other DB structures.
Let’s suppose you have data as follows:
Product
Variant
On the Product…
To be explicit (because this also comes up a lot)
Let’s suppose you create a Shopify Variant in Step 1 and Shopify Product in Step 2. In Step 2, you want too add the Shopify Variant you created to the Variants list. In the expression composer, this looks like:
Variants add Result of step 1 (i.e, the thing you created in Step 1).
This is different from:
Variants add Result of step 1's unique ID because unique ID is a string, not an object.
To make matters more confusing, in the Bubble databa…
Forum
Academy
Marketplace
Showcase
Pricing
Features