Forum Discussion

parkergeis's avatar
parkergeis
Helper II
10 months ago
Solved

Deployment Pipeline Rules Disabled for Semantic Model

I have a semantic model (storage mode is Direct Lake) that I have deployed from my development workspace to my test workspace. I want to set up a rule to switch from our development lakehouse to our test lakehouse on deployment, but when I go into the rule menu for the semantic model all options are disabled. I have admin permissions in all workspaces and pipeline. I am the owner of the semantic model and I am setting the rule in the Test workspace. Why is this occurring? We have set up identical processes months ago, but now it it giving us issues.

 

Need Help

6 Replies

  • tayloramy's avatar
    tayloramy
    Super User
    10 months ago

    Hi parkergeis, 

     

    DirectLake models are not currently supported in deployment pipeline rules.  

    See this post with an idea to vote for and some workarounds: Solved: Unable to set deployment rules in a pipeline - Microsoft Fabric Community

     

     

    EDIT: as blopez11 pointed out, DirectLake on SQL is supported, but DirectLake on OneLake is not. This is an important distinction that I felt was worth an update to my post.

    If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, please mark this as the solution.

    • parkergeis's avatar
      parkergeis
      Helper II
      10 months ago

      This was the correct solution. Our tenant had the setting turned on to have models default be "Direct Lake on OneLake". To change our existing model to "Direct Lake on SQL", I used Tabular Editor to update the model expression to use Sql.Database instead of AzureStorage.DataLake

    • Zimppi's avatar
      Zimppi
      New Member
      10 months ago

      Hi,

      We have a Fabric environment where we use semantic models on top of lakehouses across development, test, and production environments. About a year ago, we set up deployment pipelines with deployment rules for these semantic models. Everything worked perfectly for roughly a year.

      However, when I recently reviewed the deployment pipelines that have been running without any issues until now, I noticed that all previously defined semantic model rules are missing.

      Can someone explain what’s happening here?

      • Has this feature been removed or changed?

      • Is this a known issue or limitation?

      This is a serious problem for us, as our customer is understandably frustrated — this disruption increases their operational costs, and we believe Microsoft should address or compensate for this issue.

      Thank you for any clarification or official response.