Mixing
Primary Contact Role is getting saved without role in Lightning
When you mark a Contact as primary while adding it as Opportunity contact role in Lightning, It allows to save even without assigning a role to the primary Contact. When we try the same thing in Classic, the error message comes up and does not allow to save.
How we can bring the same functionality in Lightning?
lightning opportunitycontactrole
asked Jan 10 at 12:43
sanket kumarsanket kumar
2,7272323
add a comment |
When you mark a Contact as primary while adding it as Opportunity contact role in Lightning, It allows to save even without assigning a role to the primary Contact. When we try the same thing in Classic, the error message comes up and does not allow to save.
How we can bring the same functionality in Lightning?
lightning opportunitycontactrole
asked Jan 10 at 12:43
sanket kumarsanket kumar
2,7272323
add a comment |
When you mark a Contact as primary while adding it as Opportunity contact role in Lightning, It allows to save even without assigning a role to the primary Contact. When we try the same thing in Classic, the error message comes up and does not allow to save.
How we can bring the same functionality in Lightning?
lightning opportunitycontactrole
asked Jan 10 at 12:43
sanket kumarsanket kumar
2,7272323
When you mark a Contact as primary while adding it as Opportunity contact role in Lightning, It allows to save even without assigning a role to the primary Contact. When we try the same thing in Classic, the error message comes up and does not allow to save.
How we can bring the same functionality in Lightning?
lightning opportunitycontactrole
lightning opportunitycontactrole
asked Jan 10 at 12:43
sanket kumarsanket kumar
2,7272323
asked Jan 10 at 12:43
sanket kumarsanket kumar
2,7272323
asked Jan 10 at 12:43
sanket kumarsanket kumar
2,7272323
asked Jan 10 at 12:43
sanket kumarsanket kumar
2,7272323
asked Jan 10 at 12:43
sanket kumarsanket kumar
2,7272323
2,7272323
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I don't think there's much you can do here, as per the usual with Opportunity Contact Role. Since there's no triggers or validation rules on that object, you don't have any real-time chance to intervene in the transaction.
You're stuck then with either (a) Scheduled Apex to locate and remedy those records; or (b) observing in real time with Change Data Capture, which does support OpportunityContactRole.
The only route I can see, and it's a tricky one, would be a component on the Lightning record page for Opportunity that listens for change data capture events for Contact Roles on its own Opportunity. It could then post a Toast message, open a modal, or even set a flag on the Opportunity itself to prevent it from saving. But that's a lot of work (with pre-release technology!) and it wouldn't buy you a guarantee of data integrity since it's purely reactive in the UI layer.
Lots of good Idea Exchange posts to vote up on Opportunity Contact Roles, although I don't see this specific one among them:
Make Opportunity Contact Role a First Class Object is the big one that would solve this case.
Opportunity Validation Rule on Contact Roles is related.
Opportunity Contact Role Default: Should pop when Opp created from Contact also seems related.
answered Jan 10 at 13:04
David ReedDavid Reed
34k72052
Thanks for your answer. I have raised a case with salesforce about it. I will update soon.
– sanket kumar
Jan 10 at 17:06
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%2f246185%2fprimary-contact-role-is-getting-saved-without-role-in-lightning%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
I don't think there's much you can do here, as per the usual with Opportunity Contact Role. Since there's no triggers or validation rules on that object, you don't have any real-time chance to intervene in the transaction.
You're stuck then with either (a) Scheduled Apex to locate and remedy those records; or (b) observing in real time with Change Data Capture, which does support OpportunityContactRole.
The only route I can see, and it's a tricky one, would be a component on the Lightning record page for Opportunity that listens for change data capture events for Contact Roles on its own Opportunity. It could then post a Toast message, open a modal, or even set a flag on the Opportunity itself to prevent it from saving. But that's a lot of work (with pre-release technology!) and it wouldn't buy you a guarantee of data integrity since it's purely reactive in the UI layer.
Lots of good Idea Exchange posts to vote up on Opportunity Contact Roles, although I don't see this specific one among them:
Make Opportunity Contact Role a First Class Object is the big one that would solve this case.
Opportunity Validation Rule on Contact Roles is related.
Opportunity Contact Role Default: Should pop when Opp created from Contact also seems related.
answered Jan 10 at 13:04
David ReedDavid Reed
34k72052
Thanks for your answer. I have raised a case with salesforce about it. I will update soon.
– sanket kumar
Jan 10 at 17:06
add a comment |
I don't think there's much you can do here, as per the usual with Opportunity Contact Role. Since there's no triggers or validation rules on that object, you don't have any real-time chance to intervene in the transaction.
You're stuck then with either (a) Scheduled Apex to locate and remedy those records; or (b) observing in real time with Change Data Capture, which does support OpportunityContactRole.
The only route I can see, and it's a tricky one, would be a component on the Lightning record page for Opportunity that listens for change data capture events for Contact Roles on its own Opportunity. It could then post a Toast message, open a modal, or even set a flag on the Opportunity itself to prevent it from saving. But that's a lot of work (with pre-release technology!) and it wouldn't buy you a guarantee of data integrity since it's purely reactive in the UI layer.
Lots of good Idea Exchange posts to vote up on Opportunity Contact Roles, although I don't see this specific one among them:
Make Opportunity Contact Role a First Class Object is the big one that would solve this case.
Opportunity Validation Rule on Contact Roles is related.
Opportunity Contact Role Default: Should pop when Opp created from Contact also seems related.
answered Jan 10 at 13:04
David ReedDavid Reed
34k72052
Thanks for your answer. I have raised a case with salesforce about it. I will update soon.
– sanket kumar
Jan 10 at 17:06
add a comment |
I don't think there's much you can do here, as per the usual with Opportunity Contact Role. Since there's no triggers or validation rules on that object, you don't have any real-time chance to intervene in the transaction.
You're stuck then with either (a) Scheduled Apex to locate and remedy those records; or (b) observing in real time with Change Data Capture, which does support OpportunityContactRole.
The only route I can see, and it's a tricky one, would be a component on the Lightning record page for Opportunity that listens for change data capture events for Contact Roles on its own Opportunity. It could then post a Toast message, open a modal, or even set a flag on the Opportunity itself to prevent it from saving. But that's a lot of work (with pre-release technology!) and it wouldn't buy you a guarantee of data integrity since it's purely reactive in the UI layer.
Lots of good Idea Exchange posts to vote up on Opportunity Contact Roles, although I don't see this specific one among them:
Make Opportunity Contact Role a First Class Object is the big one that would solve this case.
Opportunity Validation Rule on Contact Roles is related.
Opportunity Contact Role Default: Should pop when Opp created from Contact also seems related.
answered Jan 10 at 13:04
David ReedDavid Reed
34k72052
I don't think there's much you can do here, as per the usual with Opportunity Contact Role. Since there's no triggers or validation rules on that object, you don't have any real-time chance to intervene in the transaction.
You're stuck then with either (a) Scheduled Apex to locate and remedy those records; or (b) observing in real time with Change Data Capture, which does support OpportunityContactRole.
The only route I can see, and it's a tricky one, would be a component on the Lightning record page for Opportunity that listens for change data capture events for Contact Roles on its own Opportunity. It could then post a Toast message, open a modal, or even set a flag on the Opportunity itself to prevent it from saving. But that's a lot of work (with pre-release technology!) and it wouldn't buy you a guarantee of data integrity since it's purely reactive in the UI layer.
Lots of good Idea Exchange posts to vote up on Opportunity Contact Roles, although I don't see this specific one among them:
Make Opportunity Contact Role a First Class Object is the big one that would solve this case.
Opportunity Validation Rule on Contact Roles is related.
Opportunity Contact Role Default: Should pop when Opp created from Contact also seems related.
answered Jan 10 at 13:04
David ReedDavid Reed
34k72052
answered Jan 10 at 13:04
David ReedDavid Reed
34k72052
answered Jan 10 at 13:04
David ReedDavid Reed
34k72052
answered Jan 10 at 13:04
David ReedDavid Reed
34k72052
34k72052
Thanks for your answer. I have raised a case with salesforce about it. I will update soon.
– sanket kumar
Jan 10 at 17:06
add a comment |
Thanks for your answer. I have raised a case with salesforce about it. I will update soon.
– sanket kumar
Jan 10 at 17:06
Thanks for your answer. I have raised a case with salesforce about it. I will update soon.
– sanket kumar
Jan 10 at 17:06
Thanks for your answer. I have raised a case with salesforce about it. I will update soon.
– sanket kumar
Jan 10 at 17:06
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%2f246185%2fprimary-contact-role-is-getting-saved-without-role-in-lightning%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
