Hi Chris,
Thanks for sharing the screenshots.
After reviewing them, it looks like the issue may be related to how the date field is defined in your dataset. Currently, the date appears to be stored as a
string rather than as a
date or timestamp data type, which is required for correct handling in GoodData.
This mismatch can cause errors during report creation or data transformations, especially if the platform expects a proper date format (as outlined in the
GoodData documentation). If this issue persists after changing the date definition, kindly provide a CSV extract for us to test this and possibly find the root cause.