A user in Europe has reported that they were having issue generating models for their analysis. After some investigation it was discovered that it is an issue with timezones dates iterating.

This isn't the first time a timezone issue has shown up, overall we should address how dates are stored.

We need to migrate the saving of date data as strings "YYYY-MM-DD"

The in calculations we use UTC dates and display results for a users local time.

Right now, if a user in Europe loads in the example, they are going to get different results and if a user in Minnesota loads in the example. This should not happen.