MicrosoftMicrosoftbia_e - whatever is in the source file is going to matter too. If you think it should be creating roles in the target, make sure they are in the source. The dacpac is just a zip file so you can use 7zip to extract it to a folder. In the extracted folder is a `model.xml'. Make sure the role that you think is present in the dacpac is actually there and wasn't missed.
If its missing, check the build action for the file in the sqlproj and make sure its set to "Build" and not "None"
If you see the role in the model.xml you can try running the publish operation against an empty database and see if it creates the Role, or you can run the publish against the base_destino with the `/d:true` and `/df:<path to a file>` options to get the diagnostic level output. One of those two things should help clue you in to what is happening.
I would also suggest using the /Action:Script so that you can see the changes it expects to make and is usually much more readable than the "DeployReport" action.
The https://github.com/microsoft/DacFx is the public "home" for SSDT. If you are still stuck It may be worthwhile to open an issue there, but the SQL team is really slow to respond _anywhere_ so expect to wait.
Whenever there is a new object, increment these bases, without impacting the existing structure.
If I read this correctly, you only want objects missing in the target that exist in the source to be created in the target. Any object in the target that is also in the source should be ignored, even when there are differences between them. Objects in the target that are not in the source should be untouched in the target.
The second sentence is unusual, and indicates to me that either your SqlServer project is out of sync with target and just needs to be refreshed, or that your SqlServer project has schema elements that actually belong to someone else and should be removed from your SqlServer project, and their dacpac needs to be referenced in your project.
If I'm guessing incorrectly on that, or you dont have time to fix this in that proper way, you will need to specify a bunch of the https://docs.microsoft.com/en-us/sql/tools/sqlpackage/sqlpackage-publish?view=sql-server-ver15#:~:text=/p%3A-,DropObjectsNotInSource,-%3D(BOOLEAN) or possibly specifying DropObjectsNotInSource to true and setting DoNotDropObjectTypes to have every possible value. I've not tried either of these before, and would really suggest sync-ing the project with the target in one of the ways mentioned above. Especially if you want to automate this process, the changes in the target schemas need to come from one source.
