I am working in an environment where my Dev sandbox is API 53.0 and my destination QA sandbox is API 52.0. I use the metadata api to deploy changes but I am running into some frustrating issues when trying to deploy to an org that is a version behind.
I am trying to push Profile changes to QA but there are properties of the profiles that only exist in my Dev org because of new features/installed packages introduced in 53.0. These new Profile properties try to deploy to QA and error out because they don't exist.
My current work around is to retrieve metadata, CRTL+F that property in the metadata config files, delete it, and re-deploy. This works but it is a major pain and it is preventing less technical team members from being able to move their changes to QA without my assistance.
Is there a deployment setting I can adjust to have it ignore properties that don't exist in the destination org? I run into this issue of my Dev sandboxes being ahead of my destination sandboxes a lot so a long term solution to this would be appreciated. Thanks in advance!