Forum Discussion
Using 'What If' parameter as part of a table calculation
- Anonymous6 years ago
Hi Anonymous
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!
- 6 years ago
hi Anonymous
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 summaryhttps://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
Hi Anonymous
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!
hi Anonymous
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