Is there a way to restrict a data trigger on backend workflows to work only on test version? I have an unreleased module that I wanted to calculate only on test version untill I am sure it is stable.
How to support both dev and production version of bubble webhook? - Need help / APIs - Bubble Forum
not sure if this will help you or not.
1 Like
Thanks for an idea, but that would help greatly with API from backend.
But here is the database trigger, which has very limited choice of what can be configured on it.
I haven’t ran into this problem. I think maybe a solution would be to add a temporary item in your table that has a test boolean (then check if true/false)? The other thing is you can setup an underlying conditional on whenever the item is being created or modified as well.
1 Like
OK, solved.
I cannot do it on the trigger, but I can do it on the workflow action itself. So solved to someway.
1 Like
Great. So underlying workflow was a solution for now. Glad I could help.
If you ever want real-time conversation or guidance on Bubble related stuff, join BuildAppolis’ Discord!
1 Like