Hey Vince Ybañez , The concern "by the time we apply :items from, Bubble has already loaded the first 1,000 items into memory." is not true. You can test this on network calls. If you ask for Do a search for: count then bubble will only load the count number and not the whole data on the client side, and count it on the client side. :item from , :item until works the same way.

Hey Anthony Hagouel , I am passing the client's unique ID from DB as the client reference ID in stripe. In stripe response from the stripe, I am getting the same client reference ID.

Hey Pedro, Member's value is provided as a text which you can find on the 3rd point after this text: 'Here is a nested array I want to pass as a parameter in Bubble API Connector' This is not an API call-related article, so there is no api call mentioned. If there is a nested array that you want to pass as a body parameter, then you can write a nested array according to the instructions. The setup is currently unavailable as it was a long time back configuration.

Hey Andrey , Do you want to Pass dynamic images for existing products added in stripe? Or Do you want to create a dynamic product with dynamic images? Both use cases are different and Different APIs will be used to achieve it.

Hey Alastair Watson , Do you want to pass dynamic quantity?

Glad to know this helped you and you liked it. Thanks

Hey Maria R , It's cool! No need for sorry. 'Redirect to external website' is already shown in step 4 of this article. That URL is the stripe checkout page URL which is based on the checkout page you have created in Stripe for that particular product. The DB structure can't be shown because of some privacy issue but feel free to share your query and I will be happy to help in all possible manner.

Hey Maria R , Success URL is a URL on which you redirect the user after successful checkout on stripe. Generally It is your app URL.

Pleasure Gael. If the changes are independent means one branch change won't create conflict with other branch change. So You can merge it with main branch in any order. But if one branch change and other branch change has some common UI, Workflows, data-types, plugins anything means there is potential of conflict and in that case, You need to decide hierarchy of merge and merge in sequence of that hierarchy. On each merge, testing of overlapping areas must be done.

Based on your suggestion Calum Brannan , I have added the screenshot. Have fun man! Cheers :)