Forum Discussion
URL Filtering not working
Hi I have tried filtering powerbi report using url filters, but unable to make it filter the published report
{url of report}/ReportSection?filter='Sheet1'/name eq 'Samuel Jack'
Any help is appreaciated. Thanks in advance
Hi Kushagra
A couple of suggestions that may help:
- Does your table Sheet1 contain the column Sheet1[name]?
Just checking, since the column used in the visual appears to be name column.
If it doesn't exist, you could create a name column and set it equal to name column. - Column names used in URL parameter filters only work if they don't contain spaces.
- In my testing, filters will not work if table names are enclosed in single quotes, so remove the single quotes around Sheet1.
Putting this together, as long as your table Sheet1 contains the column name, this should work:
{url of report}/ReportSection?filter=Sheet1/name eq 'Samuel Jack'- Does your table Sheet1 contain the column Sheet1[name]?
7 Replies
- OwenAugerSuper User
Hi Kushagra
A couple of suggestions that may help:
- Does your table Sheet1 contain the column Sheet1[name]?
Just checking, since the column used in the visual appears to be name column.
If it doesn't exist, you could create a name column and set it equal to name column. - Column names used in URL parameter filters only work if they don't contain spaces.
- In my testing, filters will not work if table names are enclosed in single quotes, so remove the single quotes around Sheet1.
Putting this together, as long as your table Sheet1 contains the column name, this should work:
{url of report}/ReportSection?filter=Sheet1/name eq 'Samuel Jack'- KushagraFrequent Visitor
Hi Owen,
I tried using a new report, with correct names of table and columns, but it still wont work. Is this a limitation of PowerBI Pro license for a report that is published?
How my data looks has been shared below for reference -
Visualization view -
Dataset -
After publishing, my url to test this filtering is - {url of the report}/ReportSection?filter=Salary/emp eq 'Jack'
Yet there is no update on the filter (both with and without filter lock on PowerBI desktop)
- OwenAugerSuper User
Hi again Kushagra
That's odd that it's not working at your end. Have you had any success since your last message?
I have created and published a report essentially identical that in your last post, and the URL filter you posted works as intended. I used an account without a Pro licence and published to My Workspace.
Regards,
Owen
- Janey2024Microsoft Employee
What if in my case, the column names contains space, is there a way to make this work by url filter?
- OwenAugerSuper User
Hi Janey2024
Yes, see here.
If table or column names contain spaces, they can be encoded as
_x0020_I just tested this with one of my own reports and it's working as expected 🙂
For example, to apply a filter equivalent to this DAX expression
'Employee Table'[Employee Name] = "Jack"a valid report URL would be
https://app.powerbi.com/groups/me/reports/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX/ReportSection?filter=Employee_x0020_Table/Employee_x0020_Name eq 'Jack'Other special characters can be encoded similarly with 0020 being replaced by the 4-digit Unicode hex code of the character.
Regards
- Does your table Sheet1 contain the column Sheet1[name]?
- AnonymousNot applicable
I am trying to use a URL for Employee Name. Does the limitation for filtering on a URL still have to be a single name without spaces? Or, does anyone have other suggestions to work around this? We have a page with multiple reports/visuals, all relating to the Employee. I'm trying to see if I give the URL to this page, but then just with a specific Employee Name, how to do this.
Thank you for any suggestions.
- OwenAugerSuper User
Hi Anonymous
Yes spaces are allowed in the URL filter parameter.
For example, I published the attached PBIX and this form of URL filters the report correctly:
https://app.powerbi.com/groups/me/reports/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX/ReportSection?filter=Employee/Name eq 'Will Graham'The spaces and other punctuation marks within the parameter will be converted with percent-encoding (%20 etc) and can also be entered that way in the first place.
Regards