Forum Discussion
Use DAX expressions to set parameters?
Hey,
PowerQuery queries are creating the "1st level" of the data model, the "2nd" level is created by something than can be considered as model processing, this "materializes" all the calculated column that have been added using DAX.
Finally a user interacts with the model (2nd level) by selecting values from a slicer, etc ...
These interactions can not be passed down to the levels that have been creating the data model. This explains why a measure can not be used inside a calculated column. From a technical point of view this is possibel, but the value of the calculated column will not change if the the measure will change, e.g. by a user interaction with the data model.
Regards,
Tom
I can see how this could be an issue if I was using DAX to pass a parameter to the same query I used the DAX on, but I was hoping to taking selections from slicers/visuals built based off of query A, set it as a paramater, and use that in query B.
Hey,
PowerQuery queries are creating the "1st level" of the data model, the "2nd" level is created by something than can be considered as model processing, this "materializes" all the calculated column that have been added using DAX.
Finally a user interacts with the model (2nd level) by selecting values from a slicer, etc ...
These interactions can not be passed down to the levels that have been creating the data model. This explains why a measure can not be used inside a calculated column. From a technical point of view this is possibel, but the value of the calculated column will not change if the the measure will change, e.g. by a user interaction with the data model.
Regards,
Tom