topic Re: RSCustomDaxFilter Documentation in DAX Commands and Tips

RSCustomDaxFilter Documentation

sedkimic — Wed, 29 Mar 2023 15:35:55 GMT

Is there documentation anywhere on the RSCustomDaxFilter function used in Report Builder? Specifically, I'm interested in what (if any) other accepable options are for the second parameter besides EqualToCondition. Is there a "greater than or equal to option"?

Re: RSCustomDaxFilter Documentation

OwenAuger — Thu, 30 Mar 2023 13:07:31 GMT

sedkimic

I have not been able to find the official documentation on RSCustomDaxFilter 😞

However, based on this article, it appears that the only possible conditions for RSCustomDaxFilter are:

EqualToCondition
NotEqualToCondition

But if you have a single-valued parameter that you are using as the lower-bound of a filter, then you can use syntax like this in the Report Builder DAX query:

MyTable[MyColumn] >= @MyParameter

This assumes "MyParameter" is configured correctly and the type corresponds to MyColumn etc.

Regards,

Owen

Re: RSCustomDaxFilter Documentation

sedkimic — Thu, 30 Mar 2023 14:07:23 GMT

This is what I tried based on your suggestion where @CalendarEndofMonth matches a report parameter that had been previously defined and is being used by other datasets in the report. When validating the query I receive an error message that contains "The query contains the 'CalendarEndofMonth' parameter, which is not declared." Does the parameter have to be declared in the query as well? And if so, how?

This does return the expected result within DAX Studio.

EVALUATE
SUMMARIZECOLUMNS (
    'Calendar'[End of Month],
    FILTER (
        VALUES ( 'Calendar'[End of Month] ),
        ( 'Calendar'[End of Month] >= @CalendarEndofMonth )
    ),
    "5 Year Treasury Yield", [5 Year Treasury Yield]
)

Re: RSCustomDaxFilter Documentation

OwenAuger — Fri, 31 Mar 2023 12:29:31 GMT

Hi again,

I did get this working yesterday, but today tried to retrace my steps and realised I'd forgotten some of the fiddly details, so just replying now 😅

In short, yes, you should create a query parameter and set its value to that of the existing report parameter (in Dataset Properties > Parameters).

Also, you should avoid Query Designer (in my experience).

For completeness, the full set of steps I followed:

Create a new Dataset
In the Dataset Properties dialog box, in Parameters section, click Add.
Enter Parameter Name
This can be the same name or a different name from the existing report parameter, as it is scoped to the query.
For Parameter Value, select the existing report parameter from the dropdown.
Go to Query section of Dataset Properties dialog box.
Specify Name & Data source
Don't click Query Designer. Enter or paste DAX query into Query dialog box, incorporating the query parameter defined above.
Click Validate Query to confirm it works, then OK.

I have to give credit to this Reddit comment where the author followed similar steps.

Regards,

Owen

Re: RSCustomDaxFilter Documentation

sedkimic — Fri, 31 Mar 2023 13:39:02 GMT

That did it. Thanks for the steps. This doesn't seem to be documented well by Microsoft.

Re: RSCustomDaxFilter Documentation

leathard — Wed, 20 Mar 2024 01:10:42 GMT

Additionally, RSCustomDaxFilter for multi-value parameters is essentially syntactic sugar for this FILTER pattern:

FILTER( VALUES('MyTable'[Filter Column]), PATHCONTAINS(@MyParameter, 'MyTable'[Filter Column]) ),

as long as you first change the dataset parameter to be a string that joins the parameter array items using the pipe character:

=join(Parameters!MyParameter.Value, "|")

and once you have the DAX you can change it as needed.