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
Kevin Stinson 5Kevin Stinson 5 

Which components should be included in the project manifest?

My company is new to Salesforce (we are primarily a C# development shop) and we are trying to wrap our heads around how best to approach the development process. As a first step, we would like to have everything locked down under source control. In order to accomplish this we intend to:
  1. Use the 'Choose Metadata Components' menu from the Force.com IDE in order to generate a package manifest (i.e., package.xml)
  2. Download all metadata for our org using the https://workbench.developerforce.com/.
  3. Convert the metadata to a SFDX project and push to a GitHub repository.
In my first attempt at this process I had to manually comment out several dozen lines in the package manifest in order to get around errors that came up when I tried to push this code to one of my sandboxes (using the SFDX CLI). 

In order to avoid these sort of errors on deployment, as well as a matter of principle and best practices, which metadata components should be included in the project manifest? My instinct is to include everything, but I am new to the Salesforce eco-system and am still working out how things ought to be done around here.

Any advice would be really appreciated!

Kevin