Forum Discussion
TDS Endpoint multi value parameter PBRS
- 6 months ago
Hii lherbert501
The TDS endpoint expects strongly typed scalar parameters, so IN (@Team) or JSON parsing won’t work, which is why it throws “@Team was not supplied.”
Correct approach: Let Report Builder handle the multi-value expansion automatically by using:
t.name IN (@Team)Then ensure the parameter is configured as Multi-value and the dataset query type is Text (not stored procedure). Report Builder will internally expand it to multiple scalar parameters (@Team1, @Team2…).
If this still fails, the limitation is from the Dataverse TDS endpoint, which does not fully support multi-value parameterization in that case, you must switch to FetchXML or Power BI semantic model instead.
Hii lherbert501
The TDS endpoint expects strongly typed scalar parameters, so IN (@Team) or JSON parsing won’t work, which is why it throws “@Team was not supplied.”
Correct approach: Let Report Builder handle the multi-value expansion automatically by using:
t.name IN (@Team)
Then ensure the parameter is configured as Multi-value and the dataset query type is Text (not stored procedure). Report Builder will internally expand it to multiple scalar parameters (@Team1, @Team2…).
If this still fails, the limitation is from the Dataverse TDS endpoint, which does not fully support multi-value parameterization in that case, you must switch to FetchXML or Power BI semantic model instead.
- lherbert5016 months ago
Post Prodigy
Hi rohit1991 ,
Can I just confirm, you said that's why IN (Team) won't work but then said the correct approach is
t.name IN (@Team)
Is this not the same?
Thanks
- Anonymous6 months agoNot applicable
Hi lherbert501 ,
Thanks for reaching out to the Microsoft Fabric Community forum.
Please make sure you have allowed multiple values for the parameter.
In the General tab, select Allow multiple values to allow a user to select more than one value for the parameter.
Additionally,
The text for the query variable must include the IN operator, as shown in the example below.WHERE Production.ProductInventory.ProductID IN (@ProductID)Finally, Be sure to include the parentheses around the variable as shown above. Otherwise, the report fails to render and the "must declare the scalar variable" error is displayed.
I hope this information helps. Please do let us know if you have any further queries.
Thank you- lherbert5016 months ago
Post Prodigy
Hi Anonymous
Thanks for your reply. I have it set to multiple values,
Unfortunately the IN (@Parameter) method doesnt work for PBRS with the dataverse read only
Thanks