Filter Issue - Worst Case Tool

[Chris-Burgess-ACTGOV]

Hi Team
Am getting am Uncaught 'filters property is Invalid' error in the PBIESinglePageUOD_noADAL_event_filter_loop.html file. This appears to occur regardless of filter settings entered.
All prerequisites are in place (elevated and PowerShell plugins). Am logging onto a virtual machine (that has www and admin access) with a pBI service account. So all line of sight issues addressed.

Attached is basic pbix, filter is set for 'all pages'

Filter criteria: dimDates, dtmCalYear, 2013,2017

cb1.zip

Any light shedding appreciated

EDIT: This is also happening with Realistic Case Tool using demo pbix and filters

Cheers

Chris

[Chris-Burgess-ACTGOV]

Also getting a warning about cross site cookie setting. Is this relevant?

PBIESinglePageUOD_noADAL_event_filter_loop.html:1 A cookie associated with a cross-site resource at https://app.powerbi.com/ was set without the SameSite attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with SameSite=None and Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.

Chrome 79 installed. Updated to v80. Same experience.

Is there a config change to https://app.powerbi.com/13.0.12161.266/scripts/reportembed.externals.bundle.js required?

CB

[furmangg]

I'm seeing something similar. I'll do some more research but the simple workaround for now is to change this line:

    <script src="https://cdn.rawgit.com/Microsoft/PowerBI-JavaScript/master/dist/powerbi.min.js" type="text/javascript"></script>

to:

    <script src="powerbi.min.js" type="text/javascript"></script>

And then download the latest release (I tested with 2.10.3) from here:
https://github.com/microsoft/PowerBI-JavaScript/releases

Then unzip and grab the dist/powerbi.min.js file and put it in the same folder as your .html file.

Let me know if this solves the problem for you.

[furmangg]

I would also remove the dtmCalYear report level filter so that the filter you specify will work properly. For some reason it's trying to keep your filter from the .pbix in addition to adding the filter you specify in the PBIReport.json file. This would be a good enhancement to the tool to replace existing filters on that same field but at the moment it looks like that's how it works.

I should say I'm testing with the RealisticLoadTestTool which I'm more familiar with. I assume it's the same on the worst case tool you're using.

[Chris-Burgess-ACTGOV]

All working with PowerBI.js replaced. Thanks Greg @furmangg

Will investigate the filter level settings and see if it breaks the tool.

Agree that enhancement. Don't want client or admins having to strip filters to load test :)