Error deploying to environment via deployment pipeline

[jakaihammuda]

Hello,

I have a powerbi report which is using sql and synapse connections (not the issue) as well as 2 direct query connections to existing powerbi semantic models (where you get data from semantic model). these semantic models are from a different workspace to the report i am building. The semantci models exist in their DEV workspace but not in SIT, UAT or Prod

however, when trying to deploy via the deployment pipeline. I get this error when attempting to deploy from DEV to UAT in the different workspace for my new report.

i can only assume its due to the semantic models i am connecting with. but i dont know why that causes an issue? is it because those semantic models also need to be in their retrospective SIT envionments? to be alliged with the deployment in some way? otherwisse, that defeats the purpose of connection to an existing semantic model as i would need to include it in this new workspace too...

thanks

[Anonymous]

Hi @jakaihammuda 

Please refer to the following link which mentions that there are limitations to the deployment pipeline:

Datasets that use DirectQuery or Composite connectivity mode and have variation or auto date/time tables aren't supported in deployment pipelines.

• In your dataset, instead of using DirectQuery or Composite mode, use import mode.
• Remove the auto date/time tables from your semantic model. If necessary, delete any remaining variations from all the columns in your tables. Deleting a variation may invalidate user authored measures, calculated columns and calculated tables. Use this method only if you understand how your semantic model model works as it may result in data corruption in your visuals.

https://learn.microsoft.com/en-us/fabric/cicd/faq#what-can-i-do-if-i-have-a-dataset-with-directquery... 

If you are not in the above situation, please share the detailed error message.

Best Regards,
Jarvis Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[jakaihammuda]

Hello,

Thnk you for your reply. Due to the fact we are connecting ("get data") directly to semantic models - we are forced to use direct query for those connections

we used a dedictaed calendar table from synpase too 

[Anonymous]

Hi @jakaihammuda 

Since you are forced to use Direct Query, it is recommended that the semantic model be present in all environments to ensure that the report connects correctly to the desired data source in all different environments.

Best Regards,
Jarvis Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[jakaihammuda]

@v-huijie-msft do you have any expertise in this? 🙂