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
Chamil MadusankaChamil Madusanka 

Change Set issue in Deployment

Hi All,

 

Currently, I'm doing some R&D on deployment in salesforce. I created a trail enterprice edition(60 day trial) to do those tests. And I created a sandbox for that production environment.  Doployment connection is ok.Then I have follow below test cases;

CASE 1:

 

  1. Created a custom object in sandbox
  2. created a outbound change set in sandbox and add the custom object with dependencies
  3. upload it to production environment
  4. Deployed in production environment

CASE 2

 

  1. Created a custom field for previous custom object in sandbox
  2. Created outbound Change set in sandbox and add the custom field with dependencies
  3. upload it to production
  4. deployed in production

CASE 1 is completed succesfully.

After complete CASE 2, the custom field has been added to the custom object in production environment. But that custom field is not in standard page that related to the custom object.

 

What is the issue?

 

Thanks in Advance

 

Best Answer chosen by Admin (Salesforce Developers) 
florian.hoehnflorian.hoehn

Ok. Sorry :)

 

Then it could/should be the field level security of that field.

 

I guess you have not included a profile in your changeset?

 

If not, you have to set the FLS of the new custom field manually.

 

Hope this helps.

 

  Florian

All Answers

florian.hoehnflorian.hoehn

Hi Chamil,

 

You have to deploy the 'Page Layout' as well.

 

Just clone your changeset for CASE 2 and add the Page Layout for your custom object. :) That will do it.

 

 Florian

Chamil MadusankaChamil Madusanka

Hi Florian,

 

Thanks for the reply.

I have already deployed the page layout that related to the custom object(That's why I mentioned as "Created outbound Change set in sandbox and add the custom field with dependencies" )

But it didn't work.

florian.hoehnflorian.hoehn

Ok. Sorry :)

 

Then it could/should be the field level security of that field.

 

I guess you have not included a profile in your changeset?

 

If not, you have to set the FLS of the new custom field manually.

 

Hope this helps.

 

  Florian

This was selected as the best answer
Chamil MadusankaChamil Madusanka

Hi Florian,

 

Thank you!

It works..

I didn't add the profile into change set.

 

 

James CarboneJames Carbone

Hi,

 

Does this suggest that anytime a field is added via a change set that I should add all the profiles as well?  

 

-Jim