Conflicts between Global Date Filter and Card Date Filter + Projections

DavidChurchman

I have snapshot staff data that only makes sense to show on "by year" timescale. I want to forecast it out (by year), but I keep running into conflicts between my global date filters and my card date filters. If I put a "graph by year" on my card, I get logical projections that render on the analyzer and in the detailed view of the card:

If I remove the "graph by year" on the card and add it as a page control, I can see the card on my App Studio dashboard, but it's projecting 3 months, instead of a year, which doesn't make sense with this data:

If I try to put a "graph by year" on the card, I get "No data in filtered range" for the card on the dashboard, though the card will render with good forecasts in the detailed view after expanding. I've tried leaving the page control graph by as default, by year, and turning off the option to allow global date filters, all with the same result:

I need a card that shows the historic data by year, forecasts by year, and renders on the App Studio dasbhoard.

DavidChurchman

I figured it out. I had a column in my dataset called "Year", that was in a weird school year format, i.e. "2023-2024". I had filters on that column, but for whatever reason, in some places, Domo interpreted that values in that column as "2023" instead of "2023-2024" (trying to force it to a numeric year, I guess). I had a filter on that column on the page, which caused a conflict, because when it looked for values of "2023-2024" it didn't find them, because it only read "2023" (even though that's not what's in the data). I renamed the column to "School Year", and that fixed the problem (but raised a host of other annoying problems that always arise when you rename columns).

DavidChurchman

I figured it out. I had a column in my dataset called "Year", that was in a weird school year format, i.e. "2023-2024". I had filters on that column, but for whatever reason, in some places, Domo interpreted that values in that column as "2023" instead of "2023-2024" (trying to force it to a numeric year, I guess). I had a filter on that column on the page, which caused a conflict, because when it looked for values of "2023-2024" it didn't find them, because it only read "2023" (even though that's not what's in the data). I renamed the column to "School Year", and that fixed the problem (but raised a host of other annoying problems that always arise when you rename columns).