Can OWD be imported/exported as metadata?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty{ margin-bottom:0;
}
up vote
5
down vote
favorite
I'm currently trying to create a scratch org which reflects our ludicrously complicated production org which contains hundreds of Roles.
Upon deploying most of these, I get errors like:
Error src/roles/WhateverUser.role WMSportCustomerUser field integrity exception: unknown (Opportunity access level below organization default)
I guess this means I need to correctly configure the OWD before these roles can be deployed.
Is there any way to do this using metadata (preferably "mdapi" since we aren't ready to move to "source" yet)?
metadata-api metadata roles owd mdapi
add a comment |
up vote
5
down vote
favorite
I'm currently trying to create a scratch org which reflects our ludicrously complicated production org which contains hundreds of Roles.
Upon deploying most of these, I get errors like:
Error src/roles/WhateverUser.role WMSportCustomerUser field integrity exception: unknown (Opportunity access level below organization default)
I guess this means I need to correctly configure the OWD before these roles can be deployed.
Is there any way to do this using metadata (preferably "mdapi" since we aren't ready to move to "source" yet)?
metadata-api metadata roles owd mdapi
add a comment |
up vote
5
down vote
favorite
up vote
5
down vote
favorite
I'm currently trying to create a scratch org which reflects our ludicrously complicated production org which contains hundreds of Roles.
Upon deploying most of these, I get errors like:
Error src/roles/WhateverUser.role WMSportCustomerUser field integrity exception: unknown (Opportunity access level below organization default)
I guess this means I need to correctly configure the OWD before these roles can be deployed.
Is there any way to do this using metadata (preferably "mdapi" since we aren't ready to move to "source" yet)?
metadata-api metadata roles owd mdapi
I'm currently trying to create a scratch org which reflects our ludicrously complicated production org which contains hundreds of Roles.
Upon deploying most of these, I get errors like:
Error src/roles/WhateverUser.role WMSportCustomerUser field integrity exception: unknown (Opportunity access level below organization default)
I guess this means I need to correctly configure the OWD before these roles can be deployed.
Is there any way to do this using metadata (preferably "mdapi" since we aren't ready to move to "source" yet)?
metadata-api metadata roles owd mdapi
metadata-api metadata roles owd mdapi
asked 8 hours ago
Brian Kessler
1,5181131
1,5181131
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
5
down vote
accepted
Yes. Each object has two fields, "sharingModel" and "externalSharingModel". You can import and export these values between orgs. You'll find this setting in the CustomObject metadata. I personally use this method to set up the sharing model for standard and custom objects. There's some weird bugs around it sometimes, so some manual setup may still yet be required, but it mostly works okay.
<CustomObject xmlns="http://soap.sforce.com/2006/04/metadata">
...
<sharingModel>Read</sharingModel>
</CustomObject>
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
5
down vote
accepted
Yes. Each object has two fields, "sharingModel" and "externalSharingModel". You can import and export these values between orgs. You'll find this setting in the CustomObject metadata. I personally use this method to set up the sharing model for standard and custom objects. There's some weird bugs around it sometimes, so some manual setup may still yet be required, but it mostly works okay.
<CustomObject xmlns="http://soap.sforce.com/2006/04/metadata">
...
<sharingModel>Read</sharingModel>
</CustomObject>
add a comment |
up vote
5
down vote
accepted
Yes. Each object has two fields, "sharingModel" and "externalSharingModel". You can import and export these values between orgs. You'll find this setting in the CustomObject metadata. I personally use this method to set up the sharing model for standard and custom objects. There's some weird bugs around it sometimes, so some manual setup may still yet be required, but it mostly works okay.
<CustomObject xmlns="http://soap.sforce.com/2006/04/metadata">
...
<sharingModel>Read</sharingModel>
</CustomObject>
add a comment |
up vote
5
down vote
accepted
up vote
5
down vote
accepted
Yes. Each object has two fields, "sharingModel" and "externalSharingModel". You can import and export these values between orgs. You'll find this setting in the CustomObject metadata. I personally use this method to set up the sharing model for standard and custom objects. There's some weird bugs around it sometimes, so some manual setup may still yet be required, but it mostly works okay.
<CustomObject xmlns="http://soap.sforce.com/2006/04/metadata">
...
<sharingModel>Read</sharingModel>
</CustomObject>
Yes. Each object has two fields, "sharingModel" and "externalSharingModel". You can import and export these values between orgs. You'll find this setting in the CustomObject metadata. I personally use this method to set up the sharing model for standard and custom objects. There's some weird bugs around it sometimes, so some manual setup may still yet be required, but it mostly works okay.
<CustomObject xmlns="http://soap.sforce.com/2006/04/metadata">
...
<sharingModel>Read</sharingModel>
</CustomObject>
answered 8 hours ago
sfdcfox
242k10184409
242k10184409
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.
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%2f241072%2fcan-owd-be-imported-exported-as-metadata%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