Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
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"?
Solved! Go to Solution.
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:
I have to give credit to this Reddit comment where the author followed similar steps.
Regards,
Owen
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:
I have to give credit to this Reddit comment where the author followed similar steps.
Regards,
Owen
That did it. Thanks for the steps. This doesn't seem to be documented well by Microsoft.
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:
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
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.
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]
)
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
26 | |
20 | |
19 | |
14 | |
13 |
User | Count |
---|---|
43 | |
36 | |
24 | |
22 | |
21 |