I have a permission set where I've updated edit access to a single field. What whatever reason DevOps Center detects this as a REMOVAL of the permission set vs a change so I'm not able to deploy it.
I've seen this happen in another org as well. The only way I was able to fix it was to basically clone the permission set and use a new name. (or perhaps remove the permission set and then re-add) but that just seems way too drastic.
Any other workarounds so I can actually use DevOps Center to deploy this again?
Also, when I do pull changes permission sets almost never get pulled in. I almost always have to manually add components. Is this intentional?
Good news, everyone. I have just talked to SF support, and we were able to solve the mystery about REMOVE in DevOps.
Do the following to fix it:
1. Query in DEV console using Tooling API: select Id, IsDeleted, CreatedDate, CreatedById, LastModifiedDate, LastModifiedById, SystemModstamp, MemberIdOrName, MemberType, MemberName, RevisionNum, RevisionCounter, IsNameObsolete, IsNewMember, ChangedBy from SourceMember where MemberName = 'PERMISSION SET API NAME' (or if you don't want the full list use condition "where IsNameObsolete = TRUE")
2. Check if IsNameObsolete is set to TRUE (it most certainly will)
3. Change it to FALSE and click "Save Rows"
4. Make any change to the Permission Set on your DEV Org.
5. Create a Work Item in DevOps Center and pull changes
6. Your Permission Set will be listed as CHANGE.
You're welcome :-)