Ongoing challenges, especially in the face of the User Access Profile-to-Permissions topic. We regularly experience issues where a simple Profile change (like removing access to an App) does not actually deploy. The change tracking sees that a change was made to the Profile, but no actual change occurs upon promotion. Is there something my Admins are forgetting to do when deploying these types of "destructive" change to a Profile, or a recommendation to ensure the change deploys to production?
I'm going to note, that I've seen many people say "don't deploy profiles to reduce deployment issues". That's fine(?) but then how do you then deploy Profiles when you need to?
The overarching challenge we're having is that we have lots of profiles in our org, and we continue to support those profiles. So when we need to remove access to an object, we're unable to use DevOps to deploy that change. We can include App, Tab, Field, and other dependencies and deploy without issue, but not Object.
@Oleg Mastriukovappreciate the recommendation, but want to verify we're not missing something in DevOps, since we can also just use a Change Set.
(We are in the midst of transitioning from Profile-based to Perm-based user access, but that isn't going to help us in the near future.)
