function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
RA2013RA2013 

Page Layout not updating

Hi.

 

I have been trying to incorporate two new custom fields into the page record for the Contact object.  I used an inbound change set to bring in the two new fields.  I then manually added these two new fields to the page layout for the Contact record using the standard page layout editor in the production environment.  While the two new fields appeared in the correct place on the editor, when I then selected preview, they didn't appear under any of the profiles either in the Preview Edit Page or in the Preview Detail Page.  They also don't appear in the actual Contact record.

 

I've tested this with moving the new fields to different places; making them required fields; saving; going back in and re-saving; etc., but nothing works: they simply will not appear on the Contact record.

 

The change set was prepared in the Winter '14 Sandbox, whereas our production environment is still Summer '13.

 

Please advise.

 

Many thanks.

 

Roger.

Best Answer chosen by Admin (Salesforce Developers) 
Peter_sfdcPeter_sfdc
Have you assigned the field level security for any profiles or permissions sets? If you don't, change sets assume the worst and don't make them available to anyone, not even administrator.

This is true with any permissionable item: fields, objects, visualforce pages, apps, tabs...unless you explicitly state which users/profiles can access them, they will be made unavailable.

All Answers

Peter_sfdcPeter_sfdc
Have you assigned the field level security for any profiles or permissions sets? If you don't, change sets assume the worst and don't make them available to anyone, not even administrator.

This is true with any permissionable item: fields, objects, visualforce pages, apps, tabs...unless you explicitly state which users/profiles can access them, they will be made unavailable.
This was selected as the best answer
RA2013RA2013

Thanks, Peter: that solved my problem.
Peter_sfdcPeter_sfdc
Glad to hear it. Change set's can catch you out that way. If you know the profile, or have a permissions set, always deploy it with the features of the change set.