CI/CD dependencies not processed properly (warehouse and lakehouse)

[Jerome22]

Hi,

I try to use the source control to store my workspace's content.

but restoring it to a new workspace is not working.

I have a warehouse with cross databases views (selecting data from a lakehouse and the warehouse database itself)

the system did not restore the lakehouse first, and so fail to restore the warehouse, it can't recreate the views (as the source tables are missing).

so... how to restore databases first, then the tables, then the views and finally the storedprocedures in this order?

this also cause issues in deployment pipelines. certainly for the same reasons

[Amit_K]

I have the same problem and I have used 2 ways to do this :

Deployment Pipelines :

Deploymentment pipelines allow selective deployment. So you could deploy LH first, and the rest of WH/LH in the correct dependent order and then connect and sync up from GIT

GIT based:

Create a branch from main

drop the WHs and retain the LH and commit

Connect the Workspace to Branch and sync

Revert your commit on the branch

Delete any next level dependent WH if needed

Commit and then sync your workspace again

The first method has proven to be easier for me.

[v-ssriganesh]

Hi @Jerome22,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.

[v-ssriganesh]

Hi @Jerome22,

May I ask if you have resolved this issue? If so, please mark it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[v-ssriganesh]

Hi @Jerome22,

Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to @nilendraFabric for sharing valuable insights.

Could you please confirm if your query has been resolved by the provided solution? If so, please mark it as the solution. This will help other community members solve similar problems faster.

Thank you.

[nilendraFabric · Accepted solution]

Hi @Jerome22 

there is no built-in mechanism in Fabric to enforce dependency-aware deployment .order

The system does not automatically restore lakehouse objects before warehouse objects, leading to failures when views reference missing tables.

deployment pipelines do not natively support specifying a custom deployment order, which is critical for cross-database dependencies.

Use Fabric’s object management tools (e.g., Explorer or SQL scripts) to manually deploy objects in this order

Or

Fabric deployment pipelines provide APIs that can be used for custom orchestration