function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
CDelaneyCDelaney 

Cannot deploy to a required field

I have the source of an org which was retrieved using a pre-30 release version. Before release 30, a retrieve would include permissions for required fields, and a deploy would successfully push those permissions to the org. But as of release 30, permissions for required fields are no longer retrievable or deployable. Why?

Updating to version 30 of the Force.com IDE causes the deployment to fail since the source includes permission sets which have permissions for required fields. I'm having a hard time understanding why this change was put in place. How is our development team supposed to handle adding permissions for required fields and committing those changes in source to a repository to share?
KevinPKevinP
I'm comepletely unfamiliar with the force.com ide, but I know with other tools I've used you'll need to "subscribe" to the permission metadata. In mavensMate, you'll update your project to select the additional metadata.
Brian Watts 12Brian Watts 12

I know 2014 was ancient history, but we've been on the platform since around v47.

FWIW - I'm noticing my permissionset-meta.xml has some entries in it to "required fields" that produce this same "You cannot deploy to a required field" error when I try to deploy the source to a shape-based scratch org (now using v51 as I say this)