Thank you so much for the response and willingness to help.
I think my use case is a bit different and perhaps I didn’t explain it very well.
Essentially in my app, I have input fields where a user can specify text. One is for the name of a file. Another is for text that will be an overlay in a video or image, etc.
I then take that input field’s value and add it to a URL (API POST request). However, when that input contains special characters such as . , / ! ? - # etc - it breaks the URL/API call because those characters need to be double encoded per the Cloudinary article.
So, I’m not extracting anything from a URL path or parameter.
Lastly, this input field’s value (provided by the user) will be different every time. It may include one special character, three special characters or zero.
Hopefully, that’s a bit clearer of an explanation! Any advice?
In the example I did it two ways to double check Bubble encoding was going to work correctly) - a javascript way using @mishav toolbox plugin (I’d not use this approach for this case - totally unnecessary - but it got my Brain into Bubble gear this morning) and a pure Bubble way (I’d do it this way).
The simplest way is to set a state and use the inbuilt Bubble URL format twice - eg