Null values in Q topic

Q&A
, , ,
1

Hi community,

I have 90+ fields in a topic and I wants to get rid of null values from the visuals created by Q. What are the possible workarounds?

Thanks & regards,
Raghu

2

Hi @Raghu

Please refer to the following community documentation to include/exclude nulls.

3

Hi @Xclipse

Thanks for your response. I have already gone through that document and still have some confusion. I’m writing my query down:

My topic contains over 90 fields, and for my visual, I plan to create a filter for each field. Specifically, if two fields are used in a visual—Field 1, which contains 5 null values, and Field 2, which contains 3 null values in different rows—will the visual skip a total of 8 rows (i.e., the rows with the null values in either field)?

Can anybody from the community guide me through this?

4

Hi @Raghu

Yes, filters excluding nulls on multiple fields work as AND logic across fields, skipping any row with a null in either filtered field. The visual excludes the union of null rows (5 + 3 = up to 8, minus overlaps), showing only rows where both fields are nonnull.

5

Hi @Xclipse

Do we have any work around that’ll hide the slice/bar of “null” from visual instead of removing the entire row? Similar to what we do in quicksight.

6

Hi @Raghu

Yes, you can hide the null bar visual without removing entire rows. Right click directly on the null element in the visual and select Exclude null to suppress it while keeping underlying data for other measures. Alternatively, create a calculated field like ifelse(isNull({field}), 'Other', {field}), use it for grouping, then hide the Other category via filters.

7

Hi @Xclipse

I have 90+ fields and I’m embedding Q in my application for anonymous user. I have no idea on kind of questions from users. Creating calculated fields for all 90 fields won’t be that practical. Do we have any option that’ll automatically filter out null values whenever user asks anything?

8

Hi @Raghu

No, there is no built-in option to automatically filter nulls from all 90+ fields for every user query in embedded Q without setup.

Closest Workaround - Set Exclude nulls only filters on priority/high-null fields in the topic.