Kusto Connection, pipelines and more

[DennesTorres]

Hi,

I got this semantic model "ready". I'm noticing some problems and I'm not sure why.

1) The tables/queries connected to Kusto give an alert message advising the feature is not supported a directquery, it should use import. 

However, the data is retrieved. I can't change to import, the purpose of directquery to kusto is exactly to get real time data.

Why is this message appearing?

Is there something wrong on this query? (according to the image below)

What am I losing by not following the recomendation? 

2) When creating rules in a deployment pipeline, the Kusto connection doesn't appear as an option. 

The semantic model has 3 connections: Sharepoint, lakehouse and Kusto. I can see and manage the sharepoint and lakehouse connection, but the Kusto connection doesn't appear (image illustrating this below).

Is there something wrong with this connection? Is it done in a wrong way?
Is there other reason for it not appear in the deployment pipeline?

Kind Regards,

Dennes

[v-nikhilan-msft]

Hi @DennesTorres 
Thanks for using Fabric Community.

Apologies for the issue that you are facing.

This might require a deeper investigation from our engineering team about your workspace and the logic behind it to properly understand what might be happening. 

Please go ahead and raise a support ticket to reach our support team:

https://support.fabric.microsoft.com/support
Please provide the ticket number here as we can keep an eye on it.

[DennesTorres · Accepted solution]

Hi,

This one I managed to solve, thank you for your attention.

The solution: The Kusto connection doesn't appear directly on the rules neither allow to create a parameter directly on the UI, but if we create two power query parameters (server and database) and use the parameters in replacement to the string literals used on the M code, later we can use a parameter rule on the deployment pipeline to change the value of the parameter.

Thank you!

Kind Regards,

Dennes