Contents
How can I deploy custom fields in standard objects?
If you deploy such a .profile file to your production org, you will overwrite these Field-Level Security settings. This should let you do what you need, just be careful about FLS! 1. Add the custom fields on a standard object to a package.
How to deploy standard field and permissions in Salesforce?
That being said, there is a way to perform this task if you chose to use the metadata api. This does require either the use of tools such as Salesforce Migration Tool Kit, Eclipse (if the project is small enough), or 3rd party paid solutions which leverage the metadata api.
How to deploy standard field and permissions in sandbox?
It is frustrating that we need to replicate all picklist changes on standard objects when deploying from sandbox to live as changeset do not support standard objects. Close Case page layout is missing from the changeset options and cannot be deployed.
Where are the fields stored in Salesforce sandbox?
The field accessability is not depoyed with it. That information is stored on the profile. So, if you have the fields in the sandbox visible to all of the profiles – that doesn’t get transfered.
Is it possible to compose package.xml manually?
In case that you have a lot of metadata in your organization (classes, pages, triggers, objects etc.) it is hard to select only few of them in Force IDE as it freeze for longer time on metadata list selection when you search for names. Therefore if you know already name of needed components it is possible to compose package.xml manually.
How to create a project in package.xml?
Each component declared in package.xml will be pulled into the project you just created when you retrieve metadata from your playground. Be sure that you have all the components you want to grab properly listed and named in the package.xml file. Select Documents and then select PackageXMLProject. Name the new file package.xml.
How to reference a component in a package.xml?
For each metadata component you reference in the package.xml file (such as a custom tab for a custom object, Sticker__c), you receive a coded file. This coded file defines how the component functions within the database. To call on the metadata components in your package.xml, you reference them by their metadata type.