Forum Discussion

andy808's avatar
andy808
Resolver I
10 months ago
Solved

Backend Error when publishing a composite model through the pipeline

I have a pbix that has a direct query and an import source. Publishing direct to Dev from desktop when connection strings are for Dev refreshes fine OR when I publishe direct to Test when strings are...
Need Help
  • andy808's avatar
    andy808
    9 months ago

    I ended up creating parameters in the pbix for each datasource for each environment. This allowed me to set the parameter in the Settings section after I promoted via pipeline but BEFORE before I applied the new parameters in the pipeline. This allowed me to set the parameters, apply them and then refresh.

anilgavhane's avatar
anilgavhane
Super User
10 months ago

andy808 

  • Composite Model Behavior
      : Your PBIX file includes both DirectQuery and Import sources. When publishing directly to Dev or Test with matching connection strings, everything works fine.
    • Pipeline Deployment Issue: When you publish to Dev and then deploy to Test via the pipeline, Power BI tries to apply new data source rules and refresh the dataset in one go.
    • Backend Limitation: Power BI Premium does not support adding a new data source and refreshing the semantic model in the same transaction. This triggers the Premium_ASWL_Error.

     

    How to Fix It

    1. Split the Deployment into Two Steps

    • Step 1: Deploy the model from Dev to Test using the pipeline without triggering a refresh.
    • Step 2: After deployment, manually update the data source credentials in Test.
    • Step 3: Perform a separate refresh after the credentials are saved.

    This avoids the unsupported “add + refresh” combo.

    2. Preconfigure Data Source Rules

    • Before deploying, ensure that the data source rules for Test are already defined and valid.
    • This includes:
    • Correct connection strings
    • Valid credentials
    • Gateway mappings (if applicable)

    3. Use Parameters for Environment Switching

    • Instead of hardcoding connection strings, use parameters in your model to switch environments.
    • This allows the pipeline to apply rules without modifying the underlying data source directly.

    4. Check Gateway Configuration

    • If your model uses an on-premises SQL source, ensure the gateway is properly configured in both Dev and Test.
    • Missing or misconfigured gateways can also trigger credential errors

 

andy808's avatar
andy808
Resolver I
10 months ago

anilgavhane  #4 is done, I have gateway connections with credentials already done, set for mapping test data source. It is step #1 where I am having an issue. I do not see anywhere where I can: 

  • Step 1: Deploy the model from Dev to Test using the pipeline without triggering a refresh. How do I do this?
  • Step 2: After deployment, manually update the data source credentials in Test. How?
  • KarenL7's avatar
    KarenL7
    Advocate V
    5 months ago

    Hi andy808  / anilgavhane 

    I have exactly the same issue and rather than start a new thread, would just like to ask if you have an answer for 

    • Step 1: Deploy the model from Dev to Test using the pipeline without triggering a refresh. How do I do this?

    I cannot see this in the post here. The report was successful with rules from dev > test.  Now I have this error deploying to the next stage.

    I would like to try to see if I can get past Step 1 first....

    Thanks

    Karen