I am talking to an API that is used to determine how long a business process takes, given the process starting on a certain calendar day. To accomplish this, it takes an input date in YYYY-MM-DD format and returns a future date, again in YYYY-MM-DD format.
However, if I set the response field to the Bubble “date” data type, Bubble is trying to be too helpful. If the response field in the API is, for example:
if I mark that as a data element of type “date” and pass it to my DB, I get
“September 16, 2020 7:00 PM”
(to use one example of how one could render the date.)
It is almost as if Bubble is assuming the value coming back is a UTC representation, further assumes the lack of timestamp means midnight, and normalizes it to the local time zone I have set. I can see how that would be helpful - if I could control when it’s happening.
Is there a way I can defeat this auto-conversion, short of declaring the API response field as text and constructing my own date from parsing the string?