If you plan to change or customize Acoustic Campaign and CRM integration templates that are supplied by the operation settings, filter settings, match field settings, default system field settings, or by adding or removing blocks, review the following recommendations.
After the default template maps are set up, it is best to duplicate the existing map you want to change and rename the duplication if you plan to change or customize something other than the original name. We cannot fully troubleshoot and support all customizations of the listed settings because the default templates designed by Acoustic Campaign engineering to protect data in both CRM platforms and Acoustic Campaign.
When you make changes to the filter, operation, match fields, and system fields use the Show Preview feature in Scribe Basic maps or the Debug feature in Scribe Advanced maps to see how the data might look once it reaches the target system. By duplicating and renaming the maps, you can revert to the default map settings if it becomes necessary.
The Lead and Contact maps are for general data sync of entity fields at the main entity and CRM-related entities level.
If you need more robust customization of the legacy Basic Maps, you can convert a duplicated basic map to an advanced map. After you duplicate the basic map, select it and click Advanced to convert it to an advanced map. After conversion, the enabled row for the new map will show as incomplete. Open the map to allow the metadata validation to occur and ensure that there are no errors. When validation is complete and no errors exist, click Apply then OK to save and close the map. The map appears as Enabled. Click OK again to save the Solution. For more information, you can refer to the Scribe Help Documentation for advanced maps.
Following operations are supported when Acoustic Campaign is the target
Basic Maps Legacy Connector |
Advanced Maps |
Advanced Maps Generic Connector |
---|---|---|
Delete (allows batch processing) Delete if exists (requires a match field, no batch processing) Insert (allows batch processing) Insert if exists (requires a match field, no batch processing) Update (allows batch processing) Update if exists (requires a match field, no batch processing) Update\Insert (requires a match field, no batch processing) |
Create Delete Fetch Lookup Update Update\Insert |
Delete Fetch Lookup Merge Update Update\Insert |