I was just so excited to see the feature since I’d been asking for it for so long. Truly gutting to have the functionality you wanted so badly and needed so much dangled out like that and then taken away.
I had plans to convert the core functionality of our app over to relying on it within the next month or so, and I’m now thankful that I didn’t, but there are still multiple features I have to rebuild.
There are partial workarounds I’m already aware of and using in our apps core functionality by formatting dates as text and then converting them back to date values, but it’s complex and prone to errors (particularly later at night/morning when time zone context can push a UTC date value over to a different day entirely rather than just a different time of day). These workarounds also require 2-6 additional workflow steps for the same result. Highly inefficient.
Most of the situations I have involve an API workflow that schedules another workflow that needs to run at a very specific time of day in a specific time zone (whatever time zone my users have set in their settings). This workflow can be triggered from the frontend, or automatically from the backend. Consequently, the “API Request’s Time Zone” for the workflow isn’t consistent. So when you use the “+Hours” or “Change Hours to” operators the results are unpredictable.
The other situation where this was a godsend was properly parsing incoming dates from outside APIs that don’t include a time zone. For example, properly parsing “22/12/09 10:00 AM” to the correct date value based on my user’s set time zone. Without the broad override, there is no way to predict exactly what this date will be parsed to. The workaround is to bring the date in as text and use multiple steps to ensure it gets parsed in the proper time zone context, but it’s so frustratingly more complex and inefficient to do this.
I’m still just in shock. This is just such a step back for no apparent reason. The feature worked flawlessly. Why remove it? Why take it away from us who have built with it? It seems pointlessly cruel. No upside for Bubble, all downside for users.