All Ideas

Idea Details

Post an Idea
30  Points
Open
Idea has been posted. Give it an upvote or downvote.

Make IsPrimary field visible in ChangeEvent Message Structure of Opp ContactRole

Lightning Experience

Having the ability to create triggers on ChangeEvent is awesome. But I found this small limitation while I was playing with the ChangeEvent of OpportunityContactRole. It seems like the IsPrimary field of the OCR object is not a part of the Message Structure. I updated a contact to Primary, and this is what I got as a response.

Response: 
OpportunityContactRoleChangeEvent: {
  Id=1CExx0000000UBpGAM, ReplayId=116053,
  ChangeEventHeader=eventbus.ChangeEventHeader[
    getChangeOrigin=com/salesforce/api/soap/46.0;
    getChangeType=UPDATE;
    getEntityName=OpportunityContactRole;
    getRecordIds=(00K6F00000HmeYlUAJ);
    client=SfdcInternalAPI/; getCommitNumber=10700208387922; getCommitTimestamp=1562529561000; getCommitUser=0056F00000AbEzTQAV;
    getDiffFields=(); getNulledFields=(); getSequenceNumber=2; getTransactionKey=000146f2-73ad-fd0d-347b-0c2ff93e950f;
  ],
  Division=null, OpportunityId=null,
  ContactId=null, Role=null,
  CreatedDate=null, CreatedById=null,
  LastModifiedDate=2019-07-0719: 59: 21, LastModifiedById=null
}

As you can see, IsPrimary field is not available which seems to be odd. Having this would really simplify a lot of things.

Merge Idea · Flag

  • Upvotes
  • Downvotes

Ideas

Apps

from AppExchange

Questions

Help us to keep IdeaExchange clean by pointing out overlapping ideas. We'll investigate your suggestion and merge the ideas if it makes sense.



 

 

Thanks for your merge suggestion. We will review it shortly and merge the ideas if applicable.

Salesforce takes abuse situations very seriously. Examples of abuse include but are not limited to posting of offensive language or fraudulent statements. To help us process your request as quickly as possible, please fill out the form below describing the situation. For privacy and security reasons, the final outcome of an abuse case may not be revealed to the person who reported it.


 

Thank you for your feedback. We take abuse seriously and will investigate this issue and take appropriate action.