ADX DataSource with DirectQuery and M-Parameter not working

[Christian_Heinz]

Hi everyone,

we have found an issue with Power-BI Service and ADX Data source.

We want to configure our BI Reports against different deployment stages and are using parameters to switch the data source as described here.

This works fine for Azure SQL Data Source and ADX Data Source in Import Mode, but does not work for ADX in DirectQuery mode in BI Service. So again

The following is working:

• Switch data source of Azure-SQL Server - BI Desktop & Service
• Switch data source of ADX in Import mode - BI Desktop & Service
• Switch data source of ADX in DirectQuery mode - BI Desktop

The following results to visual errors:

• Switch data source of ADX in DirectQuery mode - BI Service

The error we got from visual is: The visualization cannot be displayed (without further helpful details)

Here an example of the query which causes the error:

let
Quelle = AzureDataExplorer.Contents(EnvironementSwitchADX, null, null, null),
public = Quelle{[Name="public"]}[Data],
PUB_TSM_FN_Issues1 = public{[Name="PUB_TSM_FN_Issues"]}[Data]
in
PUB_TSM_FN_Issues1

Replacing the parameter "EnvironmentSwitchADX" by the static Kusto URL fixes the error, but we don't want to have static URLs here..

Is that a known issue? Or does anybody have an workaround for this?

Thank you in advance,

Christian

[v-robertq-msft]

Hi, @Christian_Heinz 

According to using ADX DataSource with DirectQuery and M-Parameter in Power BI service, here are some limitations referred in the professional document, you can take a look:

After research in ICM, I can’t find a known issue related to this.

You can also go to this document to check if there are something wrong within your steps when using a query parameter in the query steps:

https://docs.microsoft.com/en-us/azure/data-explorer/power-bi-best-practices

Best Regards,

Community Support Team _Robert Qin

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

[Christian_Heinz]

Hi Robert,

thank you for your response. 

I cannot see any limitations in that article which affects the issue I reported. 

I will create a minimal report with one simple ADX query to reproduce that issue and upload the file here for further investigation. Makes that sense?

Best regards,

Christian

[v-robertq-msft]

Hi, @Christian_Heinz 

To deal with cases related to issues in Power BI, I suggest you to go to the Power BI community Issue Forum to suggest a new idea so that our members will test and check if it’s necessary to submit this issue to ICM and update the bug fix time in time.

How to Get Your Question Answered Quickly 

Best Regards,

Community Support Team _Robert Qin

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

[Christian_Heinz · Accepted solution]

Hi,

here a short update: After I posted that issue to the ideas forum, i got a suggestion to change "AzureDataExplorer.Contents" to the legacy mode "Kusto.Contents" which solved that problem.

Here my complete (fixed) query script:

let
Quelle = Kusto.Contents(EnvironementSwitchADX, null, null, null),
public = Quelle{[Name="public"]}[Data],
PUB_TSM_FN_Issues1 = public{[Name="PUB_TSM_FN_Issues"]}[Data]
in
PUB_TSM_FN_Issues1

Unfortunately, my idea request was removed. So no Fix for "AzureDataExplorer.Contents" statement is in sight now. However 😞

Best regards,

Christian