Help with Semantic Model connection

Hi GlibAvrutin,

The issue happens because the semantic model in your DEV workspace relies on another upstream semantic model, which is still connected to the PROD KQL database instead of the DEV one. When a semantic model uses a live connection or DirectQuery to another model, you can’t change the data source from the downstream model, so the KQL database connection doesn’t appear in the Data source settings.

To fix this, go to the DEV workspace and check the Lineage view for your semantic model to find the upstream model or data item it depends on. If it’s pointing to the PROD KQL database, update that upstream model by changing the KQL cluster URL and database name to DEV. Save, publish, and refresh so the changes apply to dependent models.

If you can’t modify the upstream model, it’s best to create a new semantic model in DEV that connects directly to the DEV KQL database and update your reports to use this model. For environments using deployment pipelines, setting up environment-specific parameters or data source rules ensures that DEV, TEST, and PROD models connect to the right KQL databases automatically.

Thank you
Sahasra.