Irregular Extract Files & Time Intelligence

[Melissa]

Hi @oscar_wandel,

Welcome back!

As I mentioned in post #4 interaction with Parameters is not intuitive or user friendly…

@Melissa

The Parameter value has to be selected. And here’s the catch Parameters are hard to interact with for ‘users’. If they have acces to the PBIX file and view it from within Power BI Desktop they can change the Parameter by going to the Home tab, Edit Queries and select Edit Parameters.

However if they only have acces to the report from within the Power BI Service, the only way to change a Parameter would be by going to that reports Workspace, Dataset (select the ellipsis …), choose Schedule Refresh and there you’ll find Parameters…

.

So I totally understand the need to interact with the user from the report page itself and I think there is a way to accomplish that. However the downside will be a significant increase of data in your model.
Won’t keep up the suspense any longer the general idea would be to leverage of this technique described in the dynamic date range slicer (see topic below).

Dynamic Date Range Slicer- Query M

All, Here is a solution that I use on most of my models regarding a dynamic date range slicer. I found the solution from Chris Webb, from this blog post: I changed up his solution a bit to match the solution I wanted. In order to set this up, you’ll need 2 different sets of M code. Read the blog to understand fully how this is done, but I wanted to point out that an important feature in the setup is the Relationship between the Table and the “Date Table”, Make sure in this case to have the Cr…

Meaning that instead of only loading the data into the datamodel for one scenario (like you are when using a PQ Parameter), you will have to bring in the data for both scenarios and create a key between the Slicer table and the Fact table and in the Slicer settings (in the report) you’ll have to enable “single select” for this to work.

I hope this is helpful.