Multiple Date Fields and Filters
I have one table with two date fields: date-1 and date-2. I would like to configure two filters such that filter-1 operates on date-1 and filter-2 operates on date-2. Is this possible?
My experiments so far have yielded inconsistent results. I'm not sure how to control the mapping between dates and filters.
Thanks!
Best Answer
-
If you go into the analyzer for each card (or slider), click on the date range in the top right. This will tell you which field the card is using for the date and you can change it to what you want the card to use. This may be your issue.
**Check out my Domo Tips & Tricks Videos
**Make sure toany users posts that helped you.
**Please mark as accepted the ones who solved your issue.0
Answers
-
You might need to give some examples of your filters, but you can add multiple fields into the quick filters, which may accomplish what you need.
Another idea that may help you is to create a beast mode for a date. For example:
IFNULL(date1,date2)
This would use date2 for the date field if date1 was null.
Hope this helps.
**Check out my Domo Tips & Tricks Videos
**Make sure toany users posts that helped you.
**Please mark as accepted the ones who solved your issue.0 -
Gotcha. Thanks for the feedback.
I'm referring to the range selector (slider) and calendar date selector objects that I've embedded in a client dashboard (visible to end users).
For example, every record in the underlying dataset has a 'create date' and an 'end date'. The calendar selector should allow users to initially filter the dashboard based on 'create date', then the range selector can be used to further restrict the data by 'end date'. Being able to see the relationship between the two dates and manipulate them real-time is a very impactful visualization.
In this case both dates are always defined; however, I can't seem to figure out how to 'tell' the calendar selector to only interact with the creation date field and 'tell' the range slider to only interact with end date field. Domo seems to be making the decision automatically, under-the-hood, resulting in inconsistent behavior among cards (some work as expected, some don't).
I think I'm overlooking a simple setting somewhere. I would expect both filter objects to have a configuration setting that specifies which date field they map to. I'm brand new to Domo and still learning my way around the UI.
0 -
@MarkSnodgrass Ah ...thank you! It seems quite obvious now that I see it :)
0
Categories
- 7.7K All Categories
- 3 Connect
- 919 Connectors
- 244 Workbench
- 477 Transform
- 1.8K Magic ETL
- 60 SQL DataFlows
- 446 Datasets
- 37 Visualize
- 198 Beast Mode
- 2K Charting
- 8 Variables
- 1 Automate
- 348 APIs & Domo Developer
- 82 Apps
- Workflows
- 14 Predict
- 3 Jupyter Workspaces
- 11 R & Python Tiles
- 241 Distribute
- 59 Domo Everywhere
- 241 Scheduled Reports
- 15 Manage
- 36 Governance & Security
- 27 Product Ideas
- 1.1K Ideas Exchange
- Community Forums
- 14 Getting Started
- 1 Community Member Introductions
- 49 Community News
- 18 Event Recordings
- 579 日本支部