Apex Code Development You need to sign in to do that
Don't have an account?
Salesforce code repository - What metadata to commit?
Our Salesforce team are planning to use a code repository to commit all code changes.
However, the question we are currently asking ourselves is what metatdata should be committed to the repository.
We definately want all Apex code and triggers under version control.
We are thinking that profiles and permission sets should be excluded from version control.
However what about standard and custom objects, which of course include validation rules, sharing etc?
And what about workflow rules, process flows etc, they contain logical processing so should they be under version control?
Lots to think about, if anyone has been through this and has any advice on what worked well for them that would be great.
Many thanks
However, the question we are currently asking ourselves is what metatdata should be committed to the repository.
We definately want all Apex code and triggers under version control.
We are thinking that profiles and permission sets should be excluded from version control.
However what about standard and custom objects, which of course include validation rules, sharing etc?
And what about workflow rules, process flows etc, they contain logical processing so should they be under version control?
Lots to think about, if anyone has been through this and has any advice on what worked well for them that would be great.
Many thanks
Except the metadata types listed in this link (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_unsupported_types.htm) all other metadata can be commited to git.
Please refer below link which might help you in this.
https://salesforce.stackexchange.com/questions/242629/how-to-get-all-metadata-into-git-and-what-will-the-optimal-release-flow-using-sa
Hope this helps you
Let me know if this helps you. Kindly mark it as solved so that it may help others in future.
Thanks and Regards
All Answers
Except the metadata types listed in this link (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_unsupported_types.htm) all other metadata can be commited to git.
Please refer below link which might help you in this.
https://salesforce.stackexchange.com/questions/242629/how-to-get-all-metadata-into-git-and-what-will-the-optimal-release-flow-using-sa
Hope this helps you
Let me know if this helps you. Kindly mark it as solved so that it may help others in future.
Thanks and Regards
The link provides some good details to start with our planning.