Hi, JayaVenkatasubramanian-2440 Thanks for posting your query in Microsoft Q&A.
I understand that you have two different databases and both have a dependency on each other and you want to deploy only a single dacpac, Please correct me if thats not accurate.
The dacpac deployment is a whole-database operation, this can only be altered by deployment contributors or SQLPackage command line flags (properties).
It gets messy quickly, so the first question is why are we wanting to only deploy a part of the SQL database?
Beyond validating that this is truly necessary, it can be accomplished. By having a view in Sln1 that references the contents of Sln2, the 2 are completely dependent on each other. If you require an independent development component of a portion of the database, further break apart Sln1 to the components that do not rely on Sln2 (now called Sln3), and make Sln1 dependent on Sln2 and Sln3. Sln3’s dacpac can be independently built and deployed ONLY in conjunction with /p:DropObjectsNotInSource:False. Removing objects from Sln3 will not impact the database and this will be done manually, but components missing from Sln1 and Sln2 will not be removed during the deployment.
also please refer Add Database Reference Dialog Box - SQL Server Data Tools (SSDT) | Microsoft Learn
Regards
Geetha