Campaigns can't have "&" in names.

[Perc-BRC]

Hi- Thanks.

This client(and most of our clients) doesn't use Connect, except to repost broken transactions. They have custom forms and only ever interact w/ the app in Salesforce. The app is asking for names and not IDs in settings and the virtual terminal. If you can add a warning somewhere in your instructions for setting up the app, and perhaps in Virtual Terminal or the Default campaign setting on Opp Settings there, that might be good, save the next person a ton of time troubleshooting when they think it's an unrelated error? Thanks!

B

[CnP.Support]

Good day Perc-BRC

By the way-- if you use the Campaign ID we do not look at the campaign name. In Connect you may add the Campaign ID in the ID field and in the presence of the ID we do not look for the name and simply assign the transaction info to the campaign with the ID.



Hope that helps.

[CnP.Support]

Good day Perc-BRC

Sorry for not having replied to the HUB. We will review and respond there as well.

Salesforce XML interpreter does not support CDATA - see: https://success.salesforce.com/ideav...000000081cUAAQ

To include the & sign in XML the CDATA construct is needed, else XML generates an error. Unfortunately Salesforce does not support CDATA. We have requested this feature for several years and so have others but have not yet seen it in the releases.

Not being able to post & sign to Salesforce, forces us to remove the & symbol and replace it with "and" or simply remove it.

Because of this, if the Salesforce campaign has the & sign and we remove it in the name before posting, the match will not happen. It is an issue that is constantly being watched.

We suggest that you do not use & sign in the campaign name in SF if you want Connect to post to it. In the upcoming release we have a warning in Connect.

Sorry for the inconvenience.

[Perc-BRC]

Hi, I posted to Hub, but haven't heard back yet-

If an existing campaign has an ampersand in the name, it is treated as if it can't be found and a new campaign w/ the "&" replaced by "and" is created, even if the campaign is looked up directly in the Virtual Terminal.

We found this due to an apex trigger that acts as a validation rule (it checks for a specific field on insert or update and fires an error). The new campaign can't be created due to this rule, while simply updating the existing campaign won't fire it.

Here is how I verified the issue:

1. Process gift with existing "&" campaign name in virtual terminal-- failure on Data rec due to validation

2. Remove the "&" in the existing campaign name, works fine,

3. Deactivate rule-- Process gift with existing "&" campaign-- it creates a new campaign with the name being "and" instead of "&".