Forum Discussion
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.
Hi Mauro89, Thank you for your answer. Yes there were issues with KQL query in all of my fabric workspaces (dev, staging and prod) and I managed to solve them for dev database, but the semantic model located in dev workspace, which was created and configured not by me, points to the db in prod workspace, not in dev, as the id in the error message suggests.
If you just solved the issues in DEV workspace/database, then maybe the KQL code differs between DEV and PROD. And as the semantic model takes the PROD KQL DB maybe this could be worth checking and comparing.
I also found this interesting post which might help if there are issues with related tables https://stackoverflow.com/questions/67092083/how-to-recover-from-a-broken-row-level-security-policy#:~:text=Semantic%20error:%20SEM0116:%20Error%20in,or%20scalar%20expression%20named%20'Filter'
Best regards!
Yep, that's right, and basically the question is how to make semantic model point to the dev database instead of prod. I tried creating new cloud connection in the model parameters tab, but it didn't give any results (screen attached)
Thank you for support