Allow Dynamic M Query Parameters to be bound to a column other than the slicer column

[jmweekes]

Allow Dynamic M Query Parameters to be bound to a column other than the slicer column...same table, different column.

Currently Dynamic M Query Parameters will only work if the column bound to the M Query Parameter is the same column that is selected for the slicer.  This is a huge limitation, namely, if we need to filter a query by a unique/reference key value but want to display a meaningful (or perhaps composite/constructed) value for the user.

The only way to accomplish this without this functionality would, perhaps, be to filter the query for the dislay value in the slicer, which could require duplicated coding (once for slicer table, once for table to filtered).  Including the slicer table in the SQL and filtering that for the selected M Query Parameter value might work in some circumstances, but that increases complexity and decreases performance...when it should not be necessary.  Way too much overhead...if one could even get it to work in all circumstances.