Dynamic M Query with Table Visual

[ClaytonPenner]

I have a report that utilizes a dynamic M query parameter. The parameter is binded to a column and everything works great when the binded column is a slicer or when the column is the only column in a table visual. What I would like, and seems to not work, is have other columns included in the table with the binded column and still only pass the binded column as the parameter.

I've tried including a table that only has the item number and relating it to my item table which sort of works but the user still needs to select the value in that new table after searching which isn't great functionally. 

I know using a Drill Through page would solve this and that's likely what I'll do if this doesn't have a solution.

data source is SQL Server.

Parameter working when the binded column is the only column.

When adding more columns

[ClaytonPenner]

I ended up going with a drill through page instead.

[v-rzhou-msft]

Hi @ClaytonPenner ,

If your use cases require passing multiple values to a single parameter, set the control to Yes and make sure your M query is set up to accept multiple values. Here's an example for RepoNameParameter, which allows multiple values:

You may also check the Considerations and limitations.

Best Regards,
Rico Zhou

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[ClaytonPenner]

I don't require multiple parameters. I essentially don't want the table row selection to be a concatenation of all the columns together but rather just the first column "Item Number". In my last screenshot it shows my item number "AG000003" is being combined with the description and default vendor which makes it an incompatible filter for the parameter mapping. I don't know if that combining of column data has a work around or a setting that can be changed.

[lbendlin]

Does your M code account for the two different scenarios. scalar value or list?

[ClaytonPenner]

No, only scalar value. But I don't need my report to work with selecting multiple rows of the table.

[lbendlin]

the visual (or the user interacting with it) will decide if it sends a single value or a list to the M parameter - you need to prepare for both scenarios.