Instead, can you just make 2 parameters: one for measures and one for dimensions?
Sherzodbek Ibragimov Thank you, first, for trying to tackle this hard question, and I think your onto something but I need to clarify my question. The issue I am having is not so much dimension vs. measure as it data-type string vs. data-type float (number). Its also a secondary issue of aggregated calculation vs. measures. To clarify this, I went back to the original test.twbx and turned the only dimension Discovery method into a calculated string measure like [Habitability Zone] and [HZC Clustering], which I called [Disc_method]. Then I fixed my dynamic parameter [Parameter.Show Color], and the drop-down calculation [Change Color]. As I have highlighted below, the calculated field [Change Color] still has the issue of "expecting string and found float" because ESI is a number while the other three calculations are strings.
The calculated field "Change Color":
CASE [Show Color]
WHEN 'Habitability Zone' THEN [Habitability Zone]
WHEN 'HZC Clustering' THEN [HZC Clustering]
WHEN 'Disc_method' THEN [Disc_method]
WHEN 'ESI' THEN [ESI]
Going back to your original point, I might ask, "Can I just make 2 parameters one for string calculations and one for float calculations?" My answer would be I don't know how I would do that so that multiple parameters are seen by the end user as one single calculation that is being used a single drop down list. Can you show me how?
P.S. Honestly, I have also tried using the dynamic filters which don't use the CASE/When syntax, but I still run into the issue of strings vs. floats.
Whenever you use IF or Case statement, they can't be mixed, (just like in your case). So, they should be either string or numbers, but not both. However, if you convert ESI to string with STR() function, then you should be able to use 'Change Color' dimension. Looks like you deleted you new updated workbook as I don't see it now. Hope it helps.