CONCAT(opportunity_id, contact_id)
as part of your data model. Your data model should also still include opportunity_id
, contact_id
, and contact_email
, as well as any other fields you want to eventually pass to Salesforce. Pro tip: Your model should exclude any records where either the Opportunity or Contact are null
.census_tracking_id__c
, though you can provide whatever label you want.opportunity_id
as well as Contact lookup either using either Contact contact_id
or contact_email
. You can also map any other fields you want on the OpportunityContactRole.;
In Snowflake, this is best done via a listagg(val, ';')
NULL
values from your data source. Note that the Salesforce will ignore any empty string or ''
values from your source and make no changes.DUPLICATES_DETECTED:Use one of these records?:--
CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY:MyCoolTrigger: System.LimitException: SBQQ:Too many SOQL queries: 101
CANNOT_EXECUTE_FLOW_TRIGGER: Apex CPU time limit exceeded
CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY: Apex heap size too large
scheduleBactch()
function can help with this as well.INVALID_CROSS_REFERENCE_KEY:INVALID CROSS REFERENCE ID
OAUTH_APP_BLOCKED: this app is blocked by admin
UNABLE_TO_LOCK_ROW: unable to obtain exclusive access to this record or 200 records