How do you change the field used for the date range on a card?

I feel like it is a bug that it does this and could be worth reporting to Domo. The workaround I have found is that Domo will use the last date field added to your table card as the date range field. So, if the field that you want to use as your date range is not being used, remove it from your table card and then add it back and it should be the one selected.

Hope this helps.

@mlb I believe it lets you choose a date in the date range field when there is no date field added to the list of columns in the table. Once you add a date field to the table, the option to select a field in the date range is greyed out.

It is odd behavior and would be worth submitting as an enhancement in the ideas exchange to have it never be disabled.

Some time has passed but Google suggested this to me, so dropping a comment for future web travelers who wrestle with a similar issue—grayed out date filter options.

My scenario was that one card (bar chart) displayed an x-axis with a calculated date, but the date filter had a different date column selected entirely. This was the desired outcome. A future built card using similar data would not replicate function because of the "default" behavior, as explained above in @mlb's note:

"As mentioned in the dojo article shared by you, I found out that, it is true. It is the functionality of Domo that, it uses the last date field added to your table card as the date range field but specially in table card. In case of bar chart, it always uses the date field which is in X-axis." and Domo claims it isn't a bug at all.

Well, that's sort of true.

For a bar chart, you can CAST the date field as a string with a DATE_FORMAT Beast Mode, and Domo charting then types and no longer overrides the date filter behavior. It's a situation where you have to unfortunately outsmart the tool, rather than the tool allowing the behavior and flexibility needed for design requirements.

What's even more confusing is the original card, the one I was trying to mirror, both the calculated date and the x-axis date were both typed correctly as dates, but this alleged default behavior was not applied. It's not clear if there's a secret handshake or order of actions to override the standard behavior, and it seems like a bug (even if we call it an 'escaped feature'). I'm not going to try to bark up that tree though — just cast display dates as strings and work from there.

Icing on the cake, Domo will (smartly!) pick up formatted date strings and allow date display strings under Properties to override, so you don't have to worry about y-m-d, m-d-y, d-m-y, etc. in pushing your string.

(Potential use case: Let's say you need to build a forecast each month that shows the next twelve months. You want to review last month's forecast versus this month's forecast using built-in date filtering, but all forecast dates are projected into the future. Domo, thinking its being helpful, blocks setting the date filter to 'Forecast Create Date' by defaulting to the displayed date of 'Forecasted Month'.)