Error: You cannot deploy to a required field

Mike Arthur • 10 May 2018

Avoid required fields in profiles and permission sets

Since API version 30.0 a change set or ant deployment will fail if a field that is required in the field definition is included in a profile or permission set that is being deployed.

If you create a new custom field and check 'Required', Field Level Security automatically becomes 'Visible' for all profiles. Similarly, if you edit the definition of a custom field which is not visible to all profiles and check 'Required' then it automatically becomes visible to all profiles. Therefore there is no need to reference it in a permission set. Try it!

My Blog of Salesforce Stuff

by Mike Arthur • 16 October 2021
'XHR Failed' error when trying to install VS Code extension
by Mike Arthur • 9 June 2020
What is $A (dollar A) in Lightning Aura component framework? Is it a global variable? Where are the docs for $A?
by Mike Arthur • 8 May 2020
Authorise a Salesforce Connected App using OAuth 2.0 JWT Bearer Flow
by Mike Arthur • 26 April 2020
REST API Connection to Salesforce Connected App Using OAuth 2.0 Authentication from Postman
by Mike Arthur • 23 March 2020
How to create a Lightning tab menu with dropdown sub-menu
by Mike Arthur • 27 November 2018
How to show a month by month trend chart with multiple years on same chart
by Mike Arthur • 6 November 2018
What to do if you receive emails about expiring certificates
22 August 2018
Process json strings when working with integrations
by Mike Arthur • 22 August 2018
If you're switching email accounts you can copy appointments from one calendar to the other
by Mike Arthur • 22 August 2018
When you search in Outlook 2016, how do you see in which folder you filed an email in the results?
More posts