Comments
Sort by recent activity
Hi @DanC Sounds like a solution. I have already set the filter to only include users with name = "1" in order to not commit users to the changeset but I have never thought of doing the other way around! I will try and update back later. Thanks! / comments
Hi @DanC Sounds like a solution. I have already set the filter to only include users with name = "1" in order to not commit users to the changeset but I have never thought of doing the other way ar...
Hi @DanC, I have setup the filter as [image] And tried: 1. Not include the Filter path as the tool says it will pick the default filter file in source control (I committed it there). Result: Not work, same issue. 2. Include the Filter path ($/Project.SQL/Filter.scpf) Result: Error: The specified path either doesn't exist or can't be accessed by the current Windows account: 'D:\a\17\s\$\CurrentProject\Project.SQL\Filter.scpf' Am I missing any configuration here? I was hoping that we can exclude the Users entirely from the process in both comparing and putting into source control as normally you don't want to replicate users from database to database, especially between dev and production. Edit: nevermind, it was my fault that the error happened. Dan's solution works perfectly. But I wonder why the tool doesn't pick up the filter while it is right there in the source control folder as default. Regards. / comments
Hi @DanC,I have setup the filter as And tried:1. Not include the Filter path as the tool says it will pick the default filter file in source control (I committed it there). Result: Not work, same i...