Formatting blank data issues for the Picklist, optionset and boolean fields
When you are running Scribe solutions for a Microsoft Dynamics CRM to Acoustic Campaign Integration, maps that update CRM picklist, optionset fields, or boolean fields from Acoustic Campaign produce update failure errors if the value in Acoustic Campaign is blank.
Note: The record is not updated when the error occurs. If the failure occurs when you are trying to create a record in CRM from Acoustic Campaign, the record might not be created.
ISNULLOREMPTY formula might be to be implemented to fix the issue. After applying the formula, Reprocess the failed records through the Scribe, to see if it was fixed.
Errors caused by running a Scribe Solution that contains the Delete Lead or Delete Contact maps
When running a Scribe Solution containing the delete Lead or delete Contact maps the following error is displayed: Source Entity: sp_deletedobjectpointer.
Open a support case for the CRMi team with the error details, and include the following details:
- Scribe Org Name
- Scribe Solution Name
- Date and time of the Execution History that contains the error
- An Export of the Deleted Object Pointer Records from MS Dynamics CRM
To obtain the Deleted Object Pointer Records, In MS Dynamics CRM, complete the following steps:
- Go to Advanced Find.
- In the Look For drop-down select Deleted Object Pointers.
- Select Edit Columns, then Add Columns.
- Select the following Columns: modified on, Object Deleted Date, Plugin Execution Date, Status, Status Reason.
- Click Results in the Advanced Find.
- Export the Deleted Object Pointers.
Note: The Deleted Object Plugin captures all contact and lead deleted records regardless of their sync status before deletion. This means if you deleted a contact or lead before it was set to Sync to Acoustic Campaign or obtain an Acoustic Campaign ID it still will be counted as a deleted object. Exporting these records helps the CRMi team compare the Acoustic Campaign ID and CRM Sync ID values to verify the record existed in both databases.
"No Record Found" error in Scribe
When setting up or testing a map where Acoustic Campaign is the source and using Scribe Online’s Query Preview feature, the records in the Acoustic Campaign database are not recognized by Scribe Online, and "No Records found" is displayed.
The Scribe Online Silverpop Connector Guide references the CRM Enable Sync requirement under the Silverpop Connector As IS Target section.
- Unsupported while using Restricted contact databases
- Acoustic Campaign must have the CRM Enable Sync field set to a "1". This is a system field that is exposed and managed through Acoustic Campaign when the organization is enabled for Salesforce, Dynamics CRM, or SugarCRM.
The Silverpop Connector cannot recognize records that do not have the CRM Enable Sync system field checked or set to 1.
It’s important to also note, Non-CRM Connections cannot access the following Acoustic Campaign Entities in the Query block:
- Relational Table
- UB Event
- Contact List Member
An item with the same key already exists
When configuring or running a Scribe solution, to Query or Update\Insert records for an Acoustic Campaign Contact Database, the GetLists API is submitted by the Silverpop Connector to retrieve the databases available for the next action in Scribe Online.
The main criteria for the databases being retrieved by the API are:
- Shared (not in private folders)
- Active (not archived)
The Response given to Scribe Online is a list of all the databases available.
If the API encounters duplicate database names, an error is displayed in Scribe Online.
- An item with the same key has already been added.
- Failure completing metadata request: An item with the same key has already been added.
Other symptoms displayed when editing mappings:
- No mappable fields exist on the chosen entity.
- The field is not found in Target Entity
Another related error that may occur during execution is
- Unable to retrieve lists with type database
All reflect the inability to get past the GetLists request and continue to the next steps for the map.
Finding the duplicated database names can be challenging if they were created by different users and exist in separate folders.
If many databases exist, it best to open an Acoustic Campaign support case and request a quick check of duplicate database names matching the criteria used by the API. Often the databases are created by different users and exist in different folders.
Once the duplicates are identified, the names can be changed, or unnecessary duplicates deleted.
Reset the metadata for the Silverpop Connection in Scribe Online, after the Acoustic Campaign database changes are complete, for the solution and map configurations to be updated.
Resolve errors when running a scheduled or on-demand Scribe solution
When you are running a scheduled or on-demand scribe solution the following error occurs indicating that the synchronization is not successful:
The following query was unable to be processed: Requested column 'xxxxxxxxxxxxxx' not in list '##########' The following query was unable to be processed: Requested column 'xxxxxxxxxxxxxx' not in list '##########' Code: ~ 101/SP.API, Message: Requested column 'xxxxxxxxxxxxxx' not in list '##########'
This error occurs because a field in the Acoustic Campaign is changed or removed but is still being referenced in a map. xxxxxxxxxxxxxx refers to the field name in Acoustic Campaign that has been changed or removed. ########## refers to the database id or list id where field is expected.
Refer to the following items to resolve the issue:
- Refer Updating Changed Fields.
- The enabled maps must be checked for the field that is specified and reconfigured before the next sync to fix the error.
- If needed, open a support case with the CRMi team to help fix the error.
Entire record creation or update failure
When you are running a Scribe solution and if one of the fields fails, the entire records fail to create or update in the target database. The issue generally happens with invalid email addresses, blank picklist values, blank boolean values, and string to integer32 incorrect formats.
Scribe Acoustic Campaign Connectors are Scribe Advanced Maps compatible as of Dec 2013. To take advantage of the feature for your MS Dynamics CRM integration, it's best to duplicate and rename the map that is having the problem and convert it to an Advanced map. After completing the process, review the blocks in the advanced map to decide how to handle failures for a particular field. If needed open a case with the CRMi team for further assistance in configuring the advanced map.
For more information, see http://www.scribesoft.com/helpcenter...e=scribeonline.
The recipient already deleted or Sync ID already exists error
When you are running a scheduled Scribe solution for a Microsoft Dynamics CRM to Acoustic Campaign Integration the maps named Microsoft CRM to Acoustic Campaign - Contact Sync, Microsoft CRM to Acoustic Campaign - Lead Sync or, Microsoft CRM to Acoustic Campaign - Leads\Contacts Sync handles the adding and updating synchronized records to Acoustic Campaign from CRM.
If the record was the last one successfully processed, and the next scheduled run keeps encountering the same 'insert' operation for the record based on the last 'modified on' date in CRM, then the following error will occur until Scribe gets a new record to process.
Scribe is just saying 'I've already processed this record, I don't have another active record to process that matches, or more recently modified, the LAST_MODIFIED_ON date requested in the Query block of the specified map, so I'm letting you know again this record has already been added'
Note: The reason why the Insert operation would still be attempted instead of the update operation on the following runs is being investigated further but can only be explained as 'Insert' was that last operation Scribe Online cached for the record and nothing else changed for the record since the last time it was successfully processed so Scribe didn't have a reason to change the cached operation.
|Map Name||MS CRM to Acoustic Campaign - Lead Sync|
|Error Title||Error in calling Operation Update/Insert|
|Error Description||Operation failed. Label: Update/Insert Lead, Name: CRMDatabase_LeadUpdateInsert, Message: Failure: failure_type='permanent' crm_sync_id='########-####-####-####-############' Message: 'Error Updating Recipient; Sync ID Already Exists in List - Error Adding Recipient: ############'|
'MSCRM to Acoustic Campaign Contact Delete' and "MSCRM to Acoustic Campaign Lead Delete" handles the removal of synchronized records in Acoustic Campaign that have been deactivated in CRM.
The CRM GUIDs and Acoustic Campaign RecipientIDs of deactivated records are placed in a table in CRM name 'sp_deletedobjectpointer'. The deactivation and deletion maps in Scribe check this table by the deleted on date of the record. If the record is deleted in both environments but the Scribe mapping process date has not changed an error continuously occurs in Scribe for the last set of records that were actually processed.
The error is explaining that the Acoustic Campaign recipient with the matching CRM GUID has already been deactivated in Acoustic Campaign. This could have been by a previous Scribe sync or someone manually deleting the record in Acoustic Campaign.
Scribe is just saying 'I've already processed this record, I don't have another active record to process that matches, or more recently modified, the LAST_MODIFIED_ON date requested in the Query block of the specified map, so I'm letting you know again this record has already been deleted'
|Map Name||MSCRM to Acoustic Campaign Contact Delete|
|Error Title||Error in calling Operation Delete|
|Error Description||Failure: failure_type='permanent' crm_sync_id='81529A51-241B-E311-BE9D-00155D006E53' Message: 'Recipient Already Deleted in Acoustic Campaign '|
To resolve the issue, change the 'Most recent record processed' date in Scribe for the source of the affected map.
Change the date to match the 'Last run time' of the solution.
For Advanced Maps, Open\Edit the Query Block and go to the General Tab to see the 'Most Recent record processed' field.
Recipient Not Found in List error during Microsoft Dynamics CRMi lead conversion
Read the following troubleshooting topic if you encounter master_sync_id='20C96477-DD1F-E311-8DEC-00155D64D30F merge_sync_id='E934C5A1-4B08-E311-97AE-00155D64D30F Message: 'Recipient Not Found in List' error.
When you are running a scheduled Scribe solution for a Microsoft Dynamics CRM to Acoustic Campaign integration, a default map is included that handles the conversion of synchronized lead records to contact records in Acoustic Campaign. After the conversion is completed in Microsoft Dynamics CRM, if a lead record is qualified or converted it might cause the Recipient Not Found in List error.
This error is suggesting even though the contact is added or updated was created from a qualified or converted lead, the original lead never existed in the Acoustic Campaign. Acoustic Campaign could not find a Recipient with the matching merge_sync_id specified in the error. This can be caused by one of the following reasons:
- The originating lead's Sync to Silverpop check box is enabled but the lead never made it to Acoustic Campaign as a recipient through the Scribe Online sync.
- A contact that was created through lead qualification was set to Sync to Silverpop, manually or automatically, even though the originating lead didn't sync with Acoustic Campaign.
Invalid list type. List must be: non-key list error
After running a solution in Scribe you receive one of the following errors:
Invalid list type. List must be: single opt in list. List Id: #######. Code: ~ 106/SP.API,
Invalid list type. List must be: non-key list. List id: #######. Code: ~ 106/SP.API,
The error occurs because the Acoustic Campaign database specified is not compatible with the integration. The list is either a:
- Double opt-in database
- Restricted database that has a unique identifier.
The synchronizing Acoustic Campaign database must be a regular or single opt-in flexible database.
Invalid email address errors in Scribe
When running a scheduled Scribe solution for a Microsoft Dynamics CRM to Acoustic Campaign integration, maps that update the email address field in Acoustic Campaign for leads and contacts produces Sync Failure errors if they don't meet the email address criteria for Acoustic Campaign.
- The email address is invalid and could include special characters that can't be used or the email address is formatted incorrectly.
- The local part of the email address is blocked. That is, the portion of the email address before the @ is blocked for use by Acoustic Campaign.
Given Key Not Present in Dictionary error
Read the following topic if you encounter Unable to update data into the <entitytype> entity. The given key was not present in the dictionary. error.
When you are running a Scribe solution for a Microsoft Dynamics CRM to Acoustic Campaign Integration, two maps are used to update the opt-out status for Leads and Contacts from Acoustic Campaign to MS Dynamics CRM direction. If there is a mismatch of data based on the CRM GUID, or Acoustic Campaign Recipient ID an error can occur.
The error might occur because of the following reasons:
- The record is created in or exists in another Acoustic Campaign database that is synchronizing with a different CRM environment, and an Acoustic Campaign admin tried to add the record to a different Acoustic Campaign database with the CRM GUID value from the old database still in place.
- One of the other mapped fields is marked as read-only in CRM and is not allowing the update from Acoustic Campaign.
- If you are deleting a record.
Mixing CRM integrated contacts between Acoustic Campaign databases is not suggested. If an Acoustic Campaign admin needs to do so anyway, it's best to exclude the old CRM Sync id and recipient id values. The record has to be re-established in the new databases.
In the error is caused because of reason 2 that is mentioned, the field needs to return to a read or write state and the entity that is republished in CRM. If the values still don't update during the sync after this has been completed, CRM tracing might need to be enabled to determine why the update is not successful.
When deleting records, A CRMi specialist can assist with verifying if the records are deleted. Export the Scribe errors and attach them to your CRMi support case.
COLUMN must be specified error
When running a scheduled or on-demand Scribe solution where Acoustic Campaign is the source, The following query was unable to be processed: COLUMN must be specified. Code: ~ 101/SP.API, error occurs indicating that the synchronization did not perform as expected due to the minimum API query Column (field) limit set in the Acoustic Campaign Connector.
This error generally occurs because the Acoustic Campaign Connector requires a minimum of four fields in the query to Acoustic Campaign. The field count begins after the "For each result" block.
If an If\Else block is added, the fields in the condition are included in the query as well as the matching criteria field and the fields that are mapped.
If an If\Else block is not added, then just the matching criteria field and the fields that are mapped are counted and included in the query. This means without an If\Else block, the matching criteria must be specified and at least three fields need to be mapped.
If a map has been changed to lower the map field count, then the map must be reconfigured before the next synchronization to fix the error.
The most common and minimal Acoustic Campaign fields to be mapped are:
- First Name (if it exists in Acoustic Campaign)
- Last Name (if it exists in Acoustic Campaign)