Yet Another URL Filter not Working Question

[wsdcawefwqrevfq]

There are many posts about how to filter a PBi report URL and wondering why it "doesn't work".

I find myself in the same situiation despite taking advantage of the wisdom in the several posts and responses.

To Wit:

1. The table name and column cannot contain spaces or special characters

2. The table name and column name are case sensitive

3. The search value must be in single quotes

4. The column must be of type text

5. Use ?filter=Table/Column eq 'value'

Some unclear things in the documentation:

Some examples have different treatment of the end of the URL:

URL/?filter...

URL?filter...

Also the documentation shows:

URL/Reportsection?filter...    Is that just part of the particular report URL or is it a significant component of the search parameter spec?

As for my URL that does not work:

 //app.powerbi.com/groups/xxxxxx/reports/xxxxx/ReportSection?ctid=xxxxx&experience=power-bi?filter=Employees/COMPANYID eq 'SSI'   

Case confirmed, No spaces, Single Quotes, COMPANYID is of type Text

Not sure what that "Experience= Power_bi" is.

Please Wax Poetic!

[GilbertQ]

Hi @wsdcawefwqrevfq 

here a link to the office way to use the URL Filtering: Filter a report with a URL query string parameter | Microsoft Power BI Blog | Microsoft Power BI

You can view the video for more details to get it working.

The "Experience= Power_bi" is just the way it displays in the web.

[wsdcawefwqrevfq]

Yep. Saw that earlier. Watched it. Pretty much matches the criteria I mention in my post.

As far as I can tell my query string conforms to all the requirements. Maybe additional eyes might find an issue I am missing?

[GilbertQ · Accepted solution]

Hi @wsdcawefwqrevfq

What happens if you remove the ctid and Power BI experience and start your URL filter directly after the report section?

[wsdcawefwqrevfq]

Well, what do you know, that worked!

Any idea what the logic is here? Is it running the report outside the app?

Thx

[GilbertQ]

Hi @wsdcawefwqrevfq 

The only thing I can think of is that it somehow interferes with the URL being passed down to the dataset.