Dynamic M Query Parameter with Redshift

[Al345]

I am testing the Dynamic M Parameter feature and I'm having trouble getting it to work once it is published to PBI Service. I am connecting to a Redshift database which I believe is an M based connector (correct me if I'm wrong here, I couldn't find much documentation on this point). I followed the steps in the documentation and bound the parameter to the virtual table of values I created and the slicer appears to work correctly in PBI Desktop. Then when I publish to PBI Desktop, the visual that should be changing based on my slicer selections has an error message that it "Can't desiplay the visual". When I look at the error code all I see is this: "Couldn't retrieve the data for this visual. Please try again later."

I also double checked that the report is setup on our enterprise gateway and I can refresh the report without issue so I don't think there are any issues with connecting back to the datasource. Can anyone confirm if Redshift is a compatible source for this feature? If so, what am I doing wrong? 

[Anonymous]

Sorry, Could you share a sample .pbix file for me ? i use redshift too, But I still can't see 'bind to parameter' option.

[amitchandak]

@Al345 , As per the document, this supported on following:https://docs.microsoft.com/en-us/power-bi/connect-data/desktop-dynamic-m-query-parameters

• The feature is only supported for M based data sources. The following DirectQuery sources are not supported:

  • T-SQL based data sources: SQL Server, Azure SQL Database, Synapse SQL pools (aka Azure SQL Data Warehouse), and Synapse SQL OnDemand pools
  • Live connect data sources: Azure Analysis Services, SQL Server Analysis Services, Power BI Datasets
  • Other unsupported data sources: Oracle, Teradata and Relational SAP Hana
  • Partially supported through XMLA / TOM endpoint programmability: SAP BW and SAP Hana

[Al345]

Thank you but I have reviewed that documentation and Redshift is not in the list of unsupported sources. I found another article (not from Microsoft) that indicated that Redshift is an M based connector and should thus be compatible with this functionality. 

[Anonymous]

Hi @Al345 ,

Could you share the below information with us in order to make troubleshooting?

1. The codes in your Advanced Editor (please mask the sensitive data)

2. How did you set your virtual table with parameter values? Which data type are they?

Note: Please DON'T select the type as "Any" when set the data type for parameter list

Best Regards