- Last Active
Upvoting as I think there are some unresolved issues / suggestions in here. For example, instead of just saying "Warning, fields don't match", why not let us map non-matching fields to new ones? E.g. I just migrated 300 cards over from one dataset to another, in which we had renamed a field (same data) in response to user…
We get around this problem in a slightly long-winded way 1. Create a new date calculated field called YoYDate with formula equal to: case when year(date) = year(curdate()) - 1 then date_add(date, interval 1 year) else date end Use this to power the x axis on the chart. It shifts all prior year data into this year. 2.…
I agree with the questioner here - it would be useful if we could set certain defaults both to datasets and card design. e.g: Always abbreviate values Always zero decimal places Remember that column called "revenue" is a currency amount Default auto-preview to "off" for all users (surely this benefits the whole community…
I am having the same issue - is this a feature that could be added?