topic Set analysis: ignore, but don't ignore in App Development

Set analysis: ignore, but don't ignore

Lauri — Mon, 28 Jan 2019 15:59:44 GMT

This may be simpler than I think... I have a straight table that displays patient names and several measures about their blood pressure (latest date, number of readings, etc.). Users can filter the date range of when blood pressure readings were taken.

I need to display the total count of blood pressure readings each patient has ever had. So it needs to ignore user selection on the date so that it counts all-time readings, BUT I want the table to honor the user selection so that it displays only patients who had (at least) a reading in the date range.

Using this measure causes the table to ignore the user selection altogether of course:

Count({<BPdate= >} BProwID)

As a result, the table is confusing because the user has applied a filter that is not being honored.

How can I get each patient's lifetime count while limiting the table to patients with the user-selected BPdate?

Re: Set analysis: ignore, but don't ignore

sunny_talwar — Mon, 28 Jan 2019 16:07:55 GMT

Try this

Count({<BPdate, Patients = p(Patients)>} BProwID)

Re: Set analysis: ignore, but don't ignore

Lauri — Mon, 28 Jan 2019 16:11:57 GMT

That works perfectly! Thank you for your instant response, Sunny!

Re: Set analysis: ignore, but don't ignore

dplr-rn — Mon, 28 Jan 2019 16:15:33 GMT

Use GetSelectedCount on the date fields to identify if a selection has been made. if no selection has been made

Count( BProwID)

else something like

Count({<BPdate={"<=$(=YOURMAXDATE)>=$(=YOURMINDATE)"} >} BProwID)

if you can give specifics on the columns can help further