Most text field mappings are simple drag and drop within the Scribe Online mapping interface, however, these Scribe Online field type-specific formulas should always be evaluated and used when mapping to a Relational Table. These formulas are examples. It's up to you to know what values are coming out of your CRM (Source Connections), adjust these formulas accordingly.
| Relational Table Field Type | Scribe Formula Example | Reason |
|---|---|---|
| Yes/No | IF(CampaignMember.Campaign_Campaign.IsActive = true, "Yes", "No") |
Null/Empty not allowed in Engage. |
| Date | IF
(ISNULLOREMPTY(CampaignMember.FirstRespondedDate), |
Null/Empty not allowed in Engage. The record will fail if null/empty is passed into an Engage Relational Table Date field, so in this example, null/empty values will be replaced with 01/01/0001....or whatever date you choose. |
| Number | IF (ISNULLOREMPTY(Opportunity.TotalOpportunityQuantity), 0,
Opportunity.TotalOpportunityQuantity) |
Null/Empty not allowed in Engage. |
| *Text Column Used as Association column to 'CRM Sync ID' - Salesforce.com Integrated data. | LEFT(Applications__c.ContactId, 15) |
Silverpop® CRMi for Salesforce.com stores the 15 character Lead/Contact ID in the master contact database 'CRM Sync ID' field. If these relational table rows are 'related' by the Lead/Contact ID, then you must trim it to 15 characters otherwise it will be 18 characters and not match. |
| *Text Column Used as Association column to "CRM Sync ID" - Microsoft CRM Integrated data via Scribe Online. | UPPER(contact.contactid) |
The Microsoft CRM Integration via Scribe Online uppercases the Lead/Contact GUID when syncing Leads/Contacts to the Engage contact database 'CRM Sync ID' field. If the Relational table field stores the lowercase, it will not match *The 'CRM Sync ID' column of the Engage Contact database is case-sensitive which forces a case-sensitive join to the relational table rows. |
| Text | LEFT(Campaign.Description, 4000) |
4000 character max for Text field. The row will fail if the character count exceeds 4000. Common for CRM Text Area fields which can store 32,000 characters or more. |
An error occurred while modifying Relational Table
When attempting to update Relational Tables via Scribe Online, the following can occur:
Error title: Error in calling Operation Update/Insert
Error description: Operation failed
Label: Update/Insert RT_<Name_ID>
Name: RT_<Name_ID>UpdateInsert
Message: An error occurred while modifying Relational Table: Error in calling Operation Update/Insert 156/SP.API
This error suggests a data type mismatch for non-text relational table fields. The update attempt may have encountered NULL values or incorrectly formatted data from the source.
A Scribe Online formula is needed to compensate for NULL values or to convert true/false values for yes/no field.
IFNULLUSE can be used or IF combined with ISNULLOREMPTY
IF alone can be used for True/False to Yes/No conversions as suggested above or CHOOSEBYVAL