How to handle URL parameter efficiently in Bubble?

Hi everyone,

My Problem:

I have a Bubble application that updates based on a URL parameter c using “Get data from page URL”. The first time, the update works perfectly. However, if the user selects another c value without it becoming empty between selections, the app doesn’t update because the workflow relies on the condition c is not empty.

Example:

  1. From the initial URL https://url.com/?c=youtube-expert, the app updates correctly.
  2. Switching to https://url.com/?c=facebook-expert, the app does not update because c never became empty between selections, so the workflow doesn’t detect the change.

How I’m solving it now:

I am using a workaround involving two searches, leading to additional workload usage:

  1. Add a custom state: to store the data from the c parameter.
  2. Add an additional conditional: Besides checking if c is not empty, I also verify that c is not the same as the value stored in the custom state; this involves an initial search.
  3. Update the custom state: After processing the new value of c, I update the custom state with this new value, which involves another search.

Any idea on how to solve this? Thanks in advanced!

If your Cis a predefined list of option i.e: Option A, Option B, Option C, Option D.

then create a Option Set and add all those Option into it.

and then create the same number of condition which check if C equal to an Option and flow you workflow.

1 Like

Thanks, this could work but it’s not a predefined list :s

then what is it, i have , is it an unknow list. if so how would your workflow run after each change it can be unique each time.

can you kindly tell me you senario, like what is happening after C is changing ?

Yes ofc, here quick loom video showcasing it.

Seems like you just need to clear the c= param from the URL when you click to create a new thing

This topic was automatically closed after 70 days. New replies are no longer allowed.