I am trying to create an SSDT project (in VS2022) for a database whose objects are primarily owned by a vendor application. This application dynamically creates views that we interface with from 'under-the-hood' tables that have non human-readable names. We have some custom integration code including some procedures, views, and functions, which are in-house additions created by our own team, and this is what I am trying to capture in the project for version control. I created a dacpac of the database and tried using it as a reference (as same database) so that our custom objects can use the reference to build. However, I believe that because our custom objects are in both the project and the reference, I am getting build errors of: "SQL71508: The model already has an element that has the same name xxxxxxxxx" for what appears to be every object in the project. The project name and the reference dacpac are named the same thing, the name of the actual DB.
Is there a way to tell the project or reference to ignore the same objects if they are in the reference? Or would there be a better way to organize this and still enforce build checks to the references? I would like to avoid having to create a manually altered dacpac to reference, removing the custom objects that are in the project in a tedious way, unless that is the only way to make this work.
Any other thoughts or questions are appreciated. I have searched extensively for how to implement something like this where the code is only partially "owned" and the unowned objects need to be referenced in an 'all objects' dacpac and haven't come up with anything.