REST API updates to Opportunity object not reflected the same way as native integration

ShannonKelly1
Level 3

REST API updates to Opportunity object not reflected the same way as native integration

Custom integration. Using Opportunity object, so that we can take advantage of $TriggerObject in velocity script, based on both Added to Opportunity and Opportunity is Updated triggers.

But we are finding that updates to Opportunities via API are not reflected the same way as updates to Opportunities via native integration. 
 
In the native integration, (Updated Opportunity) Activity Details reflect ALL Opportunity fields. Surprisingly, trigger constraints reference the fields in the Activity Details -- not directly in the Opportunity record (per Marketo Support). 
 
So far, we have not been able to send opportunity updates via API and successfully reflect ALL the Opportunity fields; the Activity Details reflect only *updated* fields. 
 
This differing behavior is unexpected, along with the requirement that Opp field info be present in Activity Details in order to be referenced in trigger constraints. 
 
Does anyone know how to force the Opportunity fields to be present in Updated Opportunity Activity Details, each time they are sent via API, so that the Opportunity is Updated trigger constraints can be used?
Tags (2)