Dashboard Primary Query with No Records Still Shows Data on Sub-queries

I have a dashboard with a large primary query and several sub-queries. Each key field needed by the sub-queries is published from the primary query, so filtering is applied against the first row, or whatever row the user clicks on in the primary query.

My problem is that when NO rows are returned by the primary query, each of the sub-queries show ALL records in the database, which is often perceived by the user as being “hung” since this can take a while.

Is there a way that I can instruct the sub-queries to require at least one row from the primary query before it applies the filters? I am open to any suggestions. Thanks.

Is this a Classic or Kinetic dashboard?

This is a Classic dashboard.

1 Like

You want to put your subscription on the Grid not the sub BAQ. When you do is to the sub-grid BAQ it’ll pull all rows if the parent (Publish) query returns null.

Thanks for you help, Randy. It would seem that was the issue.

1 Like