Salesforce - multiple pre production environments
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I am pretty new to Salesforce, just learning. My background is custom applications using Java. So I have two questions:
1) How can I have multiple pre-production environments in Salesforce - like dev, QA and UAT?
2) How can I apply the same configuration/code changes I applied in dev to QA and UAT (or how can I promote my changes from dev to QA and UAT)?
deployment environment
New contributor
add a comment |
I am pretty new to Salesforce, just learning. My background is custom applications using Java. So I have two questions:
1) How can I have multiple pre-production environments in Salesforce - like dev, QA and UAT?
2) How can I apply the same configuration/code changes I applied in dev to QA and UAT (or how can I promote my changes from dev to QA and UAT)?
deployment environment
New contributor
2
There are some excellent Trailhead modules that cover Salesforce's preprod environments and migration tools. Try Change Set Development Model, Package Development Model, Org Development Model, and various other Salesforce DX modules.
– David Reed♦
3 hours ago
add a comment |
I am pretty new to Salesforce, just learning. My background is custom applications using Java. So I have two questions:
1) How can I have multiple pre-production environments in Salesforce - like dev, QA and UAT?
2) How can I apply the same configuration/code changes I applied in dev to QA and UAT (or how can I promote my changes from dev to QA and UAT)?
deployment environment
New contributor
I am pretty new to Salesforce, just learning. My background is custom applications using Java. So I have two questions:
1) How can I have multiple pre-production environments in Salesforce - like dev, QA and UAT?
2) How can I apply the same configuration/code changes I applied in dev to QA and UAT (or how can I promote my changes from dev to QA and UAT)?
deployment environment
deployment environment
New contributor
New contributor
edited 3 hours ago
Jayant Das
18.9k21331
18.9k21331
New contributor
asked 3 hours ago
ThomasKAThomasKA
61
61
New contributor
New contributor
2
There are some excellent Trailhead modules that cover Salesforce's preprod environments and migration tools. Try Change Set Development Model, Package Development Model, Org Development Model, and various other Salesforce DX modules.
– David Reed♦
3 hours ago
add a comment |
2
There are some excellent Trailhead modules that cover Salesforce's preprod environments and migration tools. Try Change Set Development Model, Package Development Model, Org Development Model, and various other Salesforce DX modules.
– David Reed♦
3 hours ago
2
2
There are some excellent Trailhead modules that cover Salesforce's preprod environments and migration tools. Try Change Set Development Model, Package Development Model, Org Development Model, and various other Salesforce DX modules.
– David Reed♦
3 hours ago
There are some excellent Trailhead modules that cover Salesforce's preprod environments and migration tools. Try Change Set Development Model, Package Development Model, Org Development Model, and various other Salesforce DX modules.
– David Reed♦
3 hours ago
add a comment |
1 Answer
1
active
oldest
votes
This is your staring point Application Lifecycle and Development Models which will help you to understand more about this topic in Salesforce. As for your questions, below are pointers, where you will find more details on the linked documentation for these topics.
1) How can I have multiple pre-production environments in Salesforce - like dev, QA and UAT?
In Salesforce you utilize Sandboxes or Scratch Orgs for these purposes. The number of sandboxes/scratch orgs depends on the edition of your Production instance.
2) How can I apply the same configuration/code changes I applied in dev to QA and UAT (or how can I promote my changes from dev to QA and UAT)?
You can do this using couple of different ways:
- Metadata deployments
- Change Sets
- Salesforce DX
On the management of configuration/code changes my recommendation is to use a VCS and only deploy from there to your orgs (obviously bearing in mind the limitations applied by Salesforce to certain org types and the need to use Change Sets at times). The source of truth should be your VCS, not some unversioned org.
– Phil W
3 hours ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "459"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
ThomasKA is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f258715%2fsalesforce-multiple-pre-production-environments%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This is your staring point Application Lifecycle and Development Models which will help you to understand more about this topic in Salesforce. As for your questions, below are pointers, where you will find more details on the linked documentation for these topics.
1) How can I have multiple pre-production environments in Salesforce - like dev, QA and UAT?
In Salesforce you utilize Sandboxes or Scratch Orgs for these purposes. The number of sandboxes/scratch orgs depends on the edition of your Production instance.
2) How can I apply the same configuration/code changes I applied in dev to QA and UAT (or how can I promote my changes from dev to QA and UAT)?
You can do this using couple of different ways:
- Metadata deployments
- Change Sets
- Salesforce DX
On the management of configuration/code changes my recommendation is to use a VCS and only deploy from there to your orgs (obviously bearing in mind the limitations applied by Salesforce to certain org types and the need to use Change Sets at times). The source of truth should be your VCS, not some unversioned org.
– Phil W
3 hours ago
add a comment |
This is your staring point Application Lifecycle and Development Models which will help you to understand more about this topic in Salesforce. As for your questions, below are pointers, where you will find more details on the linked documentation for these topics.
1) How can I have multiple pre-production environments in Salesforce - like dev, QA and UAT?
In Salesforce you utilize Sandboxes or Scratch Orgs for these purposes. The number of sandboxes/scratch orgs depends on the edition of your Production instance.
2) How can I apply the same configuration/code changes I applied in dev to QA and UAT (or how can I promote my changes from dev to QA and UAT)?
You can do this using couple of different ways:
- Metadata deployments
- Change Sets
- Salesforce DX
On the management of configuration/code changes my recommendation is to use a VCS and only deploy from there to your orgs (obviously bearing in mind the limitations applied by Salesforce to certain org types and the need to use Change Sets at times). The source of truth should be your VCS, not some unversioned org.
– Phil W
3 hours ago
add a comment |
This is your staring point Application Lifecycle and Development Models which will help you to understand more about this topic in Salesforce. As for your questions, below are pointers, where you will find more details on the linked documentation for these topics.
1) How can I have multiple pre-production environments in Salesforce - like dev, QA and UAT?
In Salesforce you utilize Sandboxes or Scratch Orgs for these purposes. The number of sandboxes/scratch orgs depends on the edition of your Production instance.
2) How can I apply the same configuration/code changes I applied in dev to QA and UAT (or how can I promote my changes from dev to QA and UAT)?
You can do this using couple of different ways:
- Metadata deployments
- Change Sets
- Salesforce DX
This is your staring point Application Lifecycle and Development Models which will help you to understand more about this topic in Salesforce. As for your questions, below are pointers, where you will find more details on the linked documentation for these topics.
1) How can I have multiple pre-production environments in Salesforce - like dev, QA and UAT?
In Salesforce you utilize Sandboxes or Scratch Orgs for these purposes. The number of sandboxes/scratch orgs depends on the edition of your Production instance.
2) How can I apply the same configuration/code changes I applied in dev to QA and UAT (or how can I promote my changes from dev to QA and UAT)?
You can do this using couple of different ways:
- Metadata deployments
- Change Sets
- Salesforce DX
answered 3 hours ago
Jayant DasJayant Das
18.9k21331
18.9k21331
On the management of configuration/code changes my recommendation is to use a VCS and only deploy from there to your orgs (obviously bearing in mind the limitations applied by Salesforce to certain org types and the need to use Change Sets at times). The source of truth should be your VCS, not some unversioned org.
– Phil W
3 hours ago
add a comment |
On the management of configuration/code changes my recommendation is to use a VCS and only deploy from there to your orgs (obviously bearing in mind the limitations applied by Salesforce to certain org types and the need to use Change Sets at times). The source of truth should be your VCS, not some unversioned org.
– Phil W
3 hours ago
On the management of configuration/code changes my recommendation is to use a VCS and only deploy from there to your orgs (obviously bearing in mind the limitations applied by Salesforce to certain org types and the need to use Change Sets at times). The source of truth should be your VCS, not some unversioned org.
– Phil W
3 hours ago
On the management of configuration/code changes my recommendation is to use a VCS and only deploy from there to your orgs (obviously bearing in mind the limitations applied by Salesforce to certain org types and the need to use Change Sets at times). The source of truth should be your VCS, not some unversioned org.
– Phil W
3 hours ago
add a comment |
ThomasKA is a new contributor. Be nice, and check out our Code of Conduct.
ThomasKA is a new contributor. Be nice, and check out our Code of Conduct.
ThomasKA is a new contributor. Be nice, and check out our Code of Conduct.
ThomasKA is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Salesforce Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f258715%2fsalesforce-multiple-pre-production-environments%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
There are some excellent Trailhead modules that cover Salesforce's preprod environments and migration tools. Try Change Set Development Model, Package Development Model, Org Development Model, and various other Salesforce DX modules.
– David Reed♦
3 hours ago