Filtering on Null Values
I have seen this question/idea opened and closed several times but I will submit again that a user being able to include or not include null values with a simple filter is important. I understand the ETL and beastmode workarounds but it is not scalable to have every request run through a limited data team just to find out which orders do not have an optional shipped date
.
Comments
-
@chris_schenk can you give me a specific example of where this null filter is not working? Are you taking about a cross card interaction filter based on a slicer? Could saved filter views potentially help here?
0 -
For example: I have a chart that shows order volume by sales channel (channel is in the series). I want to filter the channel by only those orders missing sales channel. If I select "Include" the blank values only, there is no data returned. If I select "exclude" and choose all of the other values, I receive the same result.
I can see that there are a lot of orders without a channel but cannot filter for these without creating a beastmode. I have seen this with string, date, and numeric values. The easiest way to reproduce this is by using the "selection" filter instead of the "range" filter
0
Categories
- 7.7K All Categories
- 12 Connect
- 925 Connectors
- 247 Workbench
- 441 Transform
- 1.7K Magic ETL
- 61 SQL DataFlows
- 456 Datasets
- 88 Visualize
- 222 Beast Mode
- 2.1K Charting
- 8 Variables
- 5 Automate
- 349 APIs & Domo Developer
- 85 Apps
- Workflows
- 17 Predict
- 3 Jupyter Workspaces
- 14 R & Python Tiles
- 242 Distribute
- 60 Domo Everywhere
- 241 Scheduled Reports
- 18 Manage
- 39 Governance & Security
- 46 Product Ideas
- 1.1K Ideas Exchange
- 6 Community Forums
- 19 Getting Started
- 6 Community Member Introductions
- 50 Community News
- 18 Event Recordings
- 577 日本支部