Unable to deploy metadata from Partner Developer scratch org because of extra fields
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
As I hoped for higher limits I created my scratch org as a "Partner Developer" org.
{
"orgName":"myns",
"edition":"Partner Developer",
"features":[
"CascadeDelete",
"DebugApex",
"AuthorApex",
"Communities"
],
"settings":{
"orgPreferenceSettings":{
"networksEnabled":true,
"s1DesktopEnabled":true,
"chatterEnabled":true,
"translation": true
}
}
}
But now I am unable to push into my QA and Packaging org as they miss certain fields:
sfdx-source/ns/main/default/objects/Account/fields/NameLocal.field-meta.xml
Could not resolve standard field's name. (161:13)
sfdx-source/ns/main/default/objects/Contact/fields/FirstNameLocal.field-meta.xml
Could not resolve standard field's name. (162:13)
sfdx-source/ns/main/default/objects/Contact/fields/LastNameLocal.field-meta.xml
Could not resolve standard field's name. (188:13)
I thought "Easy, I just rebuild my scratch org as a regular Developer org and then retry. But No! Now I am not even able to push my source into a scratch org.
How can I solve this without manually removing all the Partner specific metadata from my sources? I don't actually use all the Partner stuff. I just accidentally created a dependency.
salesforcedx metadata-api isv scratch-org partner
add a comment |
As I hoped for higher limits I created my scratch org as a "Partner Developer" org.
{
"orgName":"myns",
"edition":"Partner Developer",
"features":[
"CascadeDelete",
"DebugApex",
"AuthorApex",
"Communities"
],
"settings":{
"orgPreferenceSettings":{
"networksEnabled":true,
"s1DesktopEnabled":true,
"chatterEnabled":true,
"translation": true
}
}
}
But now I am unable to push into my QA and Packaging org as they miss certain fields:
sfdx-source/ns/main/default/objects/Account/fields/NameLocal.field-meta.xml
Could not resolve standard field's name. (161:13)
sfdx-source/ns/main/default/objects/Contact/fields/FirstNameLocal.field-meta.xml
Could not resolve standard field's name. (162:13)
sfdx-source/ns/main/default/objects/Contact/fields/LastNameLocal.field-meta.xml
Could not resolve standard field's name. (188:13)
I thought "Easy, I just rebuild my scratch org as a regular Developer org and then retry. But No! Now I am not even able to push my source into a scratch org.
How can I solve this without manually removing all the Partner specific metadata from my sources? I don't actually use all the Partner stuff. I just accidentally created a dependency.
salesforcedx metadata-api isv scratch-org partner
add a comment |
As I hoped for higher limits I created my scratch org as a "Partner Developer" org.
{
"orgName":"myns",
"edition":"Partner Developer",
"features":[
"CascadeDelete",
"DebugApex",
"AuthorApex",
"Communities"
],
"settings":{
"orgPreferenceSettings":{
"networksEnabled":true,
"s1DesktopEnabled":true,
"chatterEnabled":true,
"translation": true
}
}
}
But now I am unable to push into my QA and Packaging org as they miss certain fields:
sfdx-source/ns/main/default/objects/Account/fields/NameLocal.field-meta.xml
Could not resolve standard field's name. (161:13)
sfdx-source/ns/main/default/objects/Contact/fields/FirstNameLocal.field-meta.xml
Could not resolve standard field's name. (162:13)
sfdx-source/ns/main/default/objects/Contact/fields/LastNameLocal.field-meta.xml
Could not resolve standard field's name. (188:13)
I thought "Easy, I just rebuild my scratch org as a regular Developer org and then retry. But No! Now I am not even able to push my source into a scratch org.
How can I solve this without manually removing all the Partner specific metadata from my sources? I don't actually use all the Partner stuff. I just accidentally created a dependency.
salesforcedx metadata-api isv scratch-org partner
As I hoped for higher limits I created my scratch org as a "Partner Developer" org.
{
"orgName":"myns",
"edition":"Partner Developer",
"features":[
"CascadeDelete",
"DebugApex",
"AuthorApex",
"Communities"
],
"settings":{
"orgPreferenceSettings":{
"networksEnabled":true,
"s1DesktopEnabled":true,
"chatterEnabled":true,
"translation": true
}
}
}
But now I am unable to push into my QA and Packaging org as they miss certain fields:
sfdx-source/ns/main/default/objects/Account/fields/NameLocal.field-meta.xml
Could not resolve standard field's name. (161:13)
sfdx-source/ns/main/default/objects/Contact/fields/FirstNameLocal.field-meta.xml
Could not resolve standard field's name. (162:13)
sfdx-source/ns/main/default/objects/Contact/fields/LastNameLocal.field-meta.xml
Could not resolve standard field's name. (188:13)
I thought "Easy, I just rebuild my scratch org as a regular Developer org and then retry. But No! Now I am not even able to push my source into a scratch org.
How can I solve this without manually removing all the Partner specific metadata from my sources? I don't actually use all the Partner stuff. I just accidentally created a dependency.
salesforcedx metadata-api isv scratch-org partner
salesforcedx metadata-api isv scratch-org partner
edited Apr 5 at 19:50
Robert Sösemann
asked Apr 5 at 19:24
Robert SösemannRobert Sösemann
13.1k1178230
13.1k1178230
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Since the error is not so clear on why this is happening , this is where one needs to see whats the actual metadata for the object that is getting deployed.
There is an environment variable in the DX CLI named SFDX_MDAPI_TEMP_DIR you might want to set it to a temp metadata directory so that when sfdx push command runs you see the actual metadata thats being deployed.
Enable in MAC (For windows similar to any other environment variables you set one) using export SFDX_MDAPI_TEMP_DIR=/users/myName/myDXProject/metadata
.This assumes you have myDXProject as project folder and metadata as the temporary folder.
Examining the metadata folder will tell whats going on here since it is weird .
add a comment |
I solved it the hard way. I manually removed all the Partner Developer specific metadata from my code:
- Fields
- App permissions
- WebLinks
and then I was able to push it into a Developer scratch org. Not so much work. But still a learning. I will not make my scratch orgs big and powerful from the beginning. Better upgrade than downsize.
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%2f256789%2funable-to-deploy-metadata-from-partner-developer-scratch-org-because-of-extra-fi%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Since the error is not so clear on why this is happening , this is where one needs to see whats the actual metadata for the object that is getting deployed.
There is an environment variable in the DX CLI named SFDX_MDAPI_TEMP_DIR you might want to set it to a temp metadata directory so that when sfdx push command runs you see the actual metadata thats being deployed.
Enable in MAC (For windows similar to any other environment variables you set one) using export SFDX_MDAPI_TEMP_DIR=/users/myName/myDXProject/metadata
.This assumes you have myDXProject as project folder and metadata as the temporary folder.
Examining the metadata folder will tell whats going on here since it is weird .
add a comment |
Since the error is not so clear on why this is happening , this is where one needs to see whats the actual metadata for the object that is getting deployed.
There is an environment variable in the DX CLI named SFDX_MDAPI_TEMP_DIR you might want to set it to a temp metadata directory so that when sfdx push command runs you see the actual metadata thats being deployed.
Enable in MAC (For windows similar to any other environment variables you set one) using export SFDX_MDAPI_TEMP_DIR=/users/myName/myDXProject/metadata
.This assumes you have myDXProject as project folder and metadata as the temporary folder.
Examining the metadata folder will tell whats going on here since it is weird .
add a comment |
Since the error is not so clear on why this is happening , this is where one needs to see whats the actual metadata for the object that is getting deployed.
There is an environment variable in the DX CLI named SFDX_MDAPI_TEMP_DIR you might want to set it to a temp metadata directory so that when sfdx push command runs you see the actual metadata thats being deployed.
Enable in MAC (For windows similar to any other environment variables you set one) using export SFDX_MDAPI_TEMP_DIR=/users/myName/myDXProject/metadata
.This assumes you have myDXProject as project folder and metadata as the temporary folder.
Examining the metadata folder will tell whats going on here since it is weird .
Since the error is not so clear on why this is happening , this is where one needs to see whats the actual metadata for the object that is getting deployed.
There is an environment variable in the DX CLI named SFDX_MDAPI_TEMP_DIR you might want to set it to a temp metadata directory so that when sfdx push command runs you see the actual metadata thats being deployed.
Enable in MAC (For windows similar to any other environment variables you set one) using export SFDX_MDAPI_TEMP_DIR=/users/myName/myDXProject/metadata
.This assumes you have myDXProject as project folder and metadata as the temporary folder.
Examining the metadata folder will tell whats going on here since it is weird .
edited Apr 6 at 22:08
answered Apr 5 at 19:59
Mohith ShrivastavaMohith Shrivastava
61.9k7105147
61.9k7105147
add a comment |
add a comment |
I solved it the hard way. I manually removed all the Partner Developer specific metadata from my code:
- Fields
- App permissions
- WebLinks
and then I was able to push it into a Developer scratch org. Not so much work. But still a learning. I will not make my scratch orgs big and powerful from the beginning. Better upgrade than downsize.
add a comment |
I solved it the hard way. I manually removed all the Partner Developer specific metadata from my code:
- Fields
- App permissions
- WebLinks
and then I was able to push it into a Developer scratch org. Not so much work. But still a learning. I will not make my scratch orgs big and powerful from the beginning. Better upgrade than downsize.
add a comment |
I solved it the hard way. I manually removed all the Partner Developer specific metadata from my code:
- Fields
- App permissions
- WebLinks
and then I was able to push it into a Developer scratch org. Not so much work. But still a learning. I will not make my scratch orgs big and powerful from the beginning. Better upgrade than downsize.
I solved it the hard way. I manually removed all the Partner Developer specific metadata from my code:
- Fields
- App permissions
- WebLinks
and then I was able to push it into a Developer scratch org. Not so much work. But still a learning. I will not make my scratch orgs big and powerful from the beginning. Better upgrade than downsize.
edited Apr 9 at 22:46
answered Apr 5 at 20:26
Robert SösemannRobert Sösemann
13.1k1178230
13.1k1178230
add a comment |
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.
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%2f256789%2funable-to-deploy-metadata-from-partner-developer-scratch-org-because-of-extra-fi%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