Can we specify DX runtime versions by project?
With Spring '19 around the corner, I decided to set up a pre-release org and upgraded my client to 45.x. After playing around a bit, I then went back to work on my actual work projects, and came across an error:
ERROR: The configured apiVersion 45.0 is not supported for this org. The max apiVersion is 44.0.
Now, I'm not able to do any work in my sandbox! Is there a way I can use the correct API version in each project? For now, I have to switch between installing salesforcedx@latest and salesforcedx@pre-release each time I want to switch modes.
salesforcedx
asked Dec 17 at 11:40
sfdcfox
246k11186423
add a comment |
With Spring '19 around the corner, I decided to set up a pre-release org and upgraded my client to 45.x. After playing around a bit, I then went back to work on my actual work projects, and came across an error:
ERROR: The configured apiVersion 45.0 is not supported for this org. The max apiVersion is 44.0.
Now, I'm not able to do any work in my sandbox! Is there a way I can use the correct API version in each project? For now, I have to switch between installing salesforcedx@latest and salesforcedx@pre-release each time I want to switch modes.
salesforcedx
asked Dec 17 at 11:40
sfdcfox
246k11186423
add a comment |
With Spring '19 around the corner, I decided to set up a pre-release org and upgraded my client to 45.x. After playing around a bit, I then went back to work on my actual work projects, and came across an error:
ERROR: The configured apiVersion 45.0 is not supported for this org. The max apiVersion is 44.0.
Now, I'm not able to do any work in my sandbox! Is there a way I can use the correct API version in each project? For now, I have to switch between installing salesforcedx@latest and salesforcedx@pre-release each time I want to switch modes.
salesforcedx
asked Dec 17 at 11:40
sfdcfox
246k11186423
With Spring '19 around the corner, I decided to set up a pre-release org and upgraded my client to 45.x. After playing around a bit, I then went back to work on my actual work projects, and came across an error:
ERROR: The configured apiVersion 45.0 is not supported for this org. The max apiVersion is 44.0.
Now, I'm not able to do any work in my sandbox! Is there a way I can use the correct API version in each project? For now, I have to switch between installing salesforcedx@latest and salesforcedx@pre-release each time I want to switch modes.
salesforcedx
salesforcedx
asked Dec 17 at 11:40
sfdcfox
246k11186423
asked Dec 17 at 11:40
sfdcfox
246k11186423
asked Dec 17 at 11:40
sfdcfox
246k11186423
asked Dec 17 at 11:40
sfdcfox
246k11186423
asked Dec 17 at 11:40
sfdcfox
246k11186423
246k11186423
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
After moving into a project folder, specify a version override with the following command:
sfdx force:config:set apiVersion=44.0
This will allow you to use the newer 45.0 features in a LWC project, whilst still being able to work in a 44.0 org without any errors.
Make sure that, if you're playing with an advanced version of the API, that you keep the salesforcedx@pre-release plugin installed until it is upgraded to the latest release.
answered Dec 17 at 11:40
sfdcfox
246k11186423
Thanks, brilliant timing. I was just looking for this!
– berry120
Dec 17 at 15:55
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
});
}
});
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%2f243847%2fcan-we-specify-dx-runtime-versions-by-project%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
After moving into a project folder, specify a version override with the following command:
sfdx force:config:set apiVersion=44.0
This will allow you to use the newer 45.0 features in a LWC project, whilst still being able to work in a 44.0 org without any errors.
Make sure that, if you're playing with an advanced version of the API, that you keep the salesforcedx@pre-release plugin installed until it is upgraded to the latest release.
answered Dec 17 at 11:40
sfdcfox
246k11186423
Thanks, brilliant timing. I was just looking for this!
– berry120
Dec 17 at 15:55
add a comment |
After moving into a project folder, specify a version override with the following command:
sfdx force:config:set apiVersion=44.0
This will allow you to use the newer 45.0 features in a LWC project, whilst still being able to work in a 44.0 org without any errors.
Make sure that, if you're playing with an advanced version of the API, that you keep the salesforcedx@pre-release plugin installed until it is upgraded to the latest release.
answered Dec 17 at 11:40
sfdcfox
246k11186423
Thanks, brilliant timing. I was just looking for this!
– berry120
Dec 17 at 15:55
add a comment |
After moving into a project folder, specify a version override with the following command:
sfdx force:config:set apiVersion=44.0
This will allow you to use the newer 45.0 features in a LWC project, whilst still being able to work in a 44.0 org without any errors.
Make sure that, if you're playing with an advanced version of the API, that you keep the salesforcedx@pre-release plugin installed until it is upgraded to the latest release.
answered Dec 17 at 11:40
sfdcfox
246k11186423
After moving into a project folder, specify a version override with the following command:
sfdx force:config:set apiVersion=44.0
This will allow you to use the newer 45.0 features in a LWC project, whilst still being able to work in a 44.0 org without any errors.
Make sure that, if you're playing with an advanced version of the API, that you keep the salesforcedx@pre-release plugin installed until it is upgraded to the latest release.
answered Dec 17 at 11:40
sfdcfox
246k11186423
answered Dec 17 at 11:40
sfdcfox
246k11186423
answered Dec 17 at 11:40
sfdcfox
246k11186423
answered Dec 17 at 11:40
sfdcfox
246k11186423
246k11186423
Thanks, brilliant timing. I was just looking for this!
– berry120
Dec 17 at 15:55
add a comment |
Thanks, brilliant timing. I was just looking for this!
– berry120
Dec 17 at 15:55
Thanks, brilliant timing. I was just looking for this!
– berry120
Dec 17 at 15:55
Thanks, brilliant timing. I was just looking for this!
– berry120
Dec 17 at 15:55
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f243847%2fcan-we-specify-dx-runtime-versions-by-project%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
