Using 'What If' parameter as part of a table calculation

[Ristaul]

Hi Community -

I am trying to use a what if scenario parameter as part of a table calculation. In essence, when I change the parameter value in the slicer, I want the value (on each record of a non-related table) to update.

I feel like it should be easy, but I am stuck.

Here is what has been done:

1. Created a new parameter named 'parameter' that has a max value of 200 and min of 0 and incraments by 10

2. This creates the table 'parameter'

3. I have the parameter slicer and paramater value (as a card) on the canvas, and the card updates dynamically as the slicer is moved

4. I have created a seperate column on a seperate table (unrelated table) that simply calls the parameter value (same thing being visualized on the card - which works on the card). This column in named Test, and the syntax looks as such: Test = 'Parameter' [Parameter Value] *** This is where the issue is *** - It is simply assigning a blank to each record

What I need to happen is for each record on the unrelated table to update as I move the slicer, and impact the parameter value.

Any help would be GREATLY appreciated!

[Ristaul · Accepted solution]

Hi @Tad17 

I don't believe the issue has anything to do w/ a table relationship, and I was not trying to call anything from a visual. I simply used the visual to verify that the parameter value was dynamically changing as I used that what if slicer (and it does).

As for seeing that data, I think if you are famriliar with What if (really a 'generateseries' function), I have provided enough information. (in essence it would be a list from 0 to 200 incramenting by 10 as I listed).

I am starting to just simply believe that you cannot use parameter values for column values, but instead they are limited only to measures. I hope that is not the case, but I fear it may be.

Any additional color if you are familiar w/ what I mentioned would be awesome.

Thanks!

[Tad17]

Hi,

This wont work as there is no relation between your parameter table and the data table. 

Ffurthermore it won't work because you can't call the value from a visual. Without seeing your data or knowing what you're trying to accomplish with your "Parameter" my only suggest is to maybe check out this article and see if it gives you some ideas: https://docs.microsoft.com/en-us/power-bi/visuals/desktop-slicer-filter-date-range

[Ristaul · Accepted solution]

Hi @Tad17 

I don't believe the issue has anything to do w/ a table relationship, and I was not trying to call anything from a visual. I simply used the visual to verify that the parameter value was dynamically changing as I used that what if slicer (and it does).

As for seeing that data, I think if you are famriliar with What if (really a 'generateseries' function), I have provided enough information. (in essence it would be a list from 0 to 200 incramenting by 10 as I listed).

I am starting to just simply believe that you cannot use parameter values for column values, but instead they are limited only to measures. I hope that is not the case, but I fear it may be.

Any additional color if you are familiar w/ what I mentioned would be awesome.

Thanks!

[v-lili6-msft · Accepted solution]

hi @Ristaul 

First, you should know that:

1. Calculation column/table not support dynamic changed based on filter or slicer.
2. Measure can be affected by filter/slicer, so you can use it to get dynamic summary

https://www.sqlbi.com/articles/calculated-columns-and-measures-in-dax/

Calculate table has the same logic with calculated column, they are getting loaded when you are loading your dataset for first time.

'What If' parameter is a calculated table essentially, and when you create it, It will automatically generate a slicer that by its field in the report.

You could use the dataset to create the report, and Slicer is a visual that only work in current report, it couldn't affect the dataset.

Regards,

Lin