No announcement yet.

CP Data not coming into Salesforce with Transaction Campaign.

  • Filter
  • Time
  • Show
Clear All
new posts

  • CnP.Support

    As discussed previously this issue was fixed in the latest update to the FaaS platform.

    We discovered an issue with the combination of words you were choosing for the Campaign which resembled a script. The filter has been modified to be less strict.

    Please let us know if we can be of any further assistance.

    Leave a comment:

  • Simon
    I've modified my developer test page to pass it statically.

    It looks like it's something specific to that campaign name "Incline to Sand Harbor Bike Path"

    If I post to the verify.faas site it works fine and shows that the campaign name is being submitted properly.

    However the CP Data that gets inserted to SF looks like this and is missing the campaign.

    <?xml version="1.0" encoding="UTF-8"?>
    <BillingEmail>[email protected]</BillingEmail>
    <BillingAddress><BillingAddress1>123 street</BillingAddress1>
    <BillingCountryName>United States of America</BillingCountryName>

    <OrganizationName>TEST: KELL Partners 2</OrganizationName>
    <WindowName>TEST: KELL Partners 2</WindowName>
    <TransactionDate>2014-09-29 11:41:41</TransactionDate>
    <TransactionTimeZone>2014-09-29 08:41:41</TransactionTimeZone>
    <PaymentType>Credit Card</PaymentType>
    <NameOnCard>john smith</NameOnCard>

    <CampaignName>Incline to Sand Harbor Bike Path</CampaignName>


    Leave a comment:

  • CnP.Support
    Good day Simon,

    Here are the 2 lines in your code that you have campaign:

    <input id="campaign" name="Campaign1" type="hidden" />
    <input id="campaignMaster" name="Campaign" type="hidden" />

    The first line (Campaign1) is for the item campaign and the second one with id of campaignMaster is for the Transaction campaign as you have named it.

    In reviewing the posted XML we don't see the Transaction campaign being posted. The XML has the item campaign but the transaction campaign is NULL.

    Based on your HTML it seems like you are using JavaScript to add campaigns in run-time based on user selection. Are you sure the Transaction campaign is being posted?

    I strongly suggest that you use: and see exactly what you are posting.

    I am sure once you post to the verification service you will see the NULL value for that field.

    Have you tried passing the campaign value statically to see if that posts? e.g.

    <input id="campaignMaster" name="Campaign" type="hidden" value="test" />

    It could be a good test.

    Let us know what you find out.

    Leave a comment:

  • CnP.Support

    We are investigating this. We don't see the main campaign in the XML so we are investigating the FaaS processor & your code.

    I will be back with you once we can determine what is going on.

    Leave a comment:

  • Simon

    Leave a comment:

  • CnP.Support
    Good day Simon,

    Do you have an Order Number that we can review its XML?

    Leave a comment:

  • Simon
    anyone have any idea?

    Leave a comment:

  • CP Data not coming into Salesforce with Transaction Campaign.

    I've got a FAAS Form that's working fine except for some reason the CP data that's being pushed back into Salesforce in isn't being sent back with the transaction campaign like it used to, just the opportunity (item)'s campaign.

    Is this a change you've made or is something gone glitchy?

    I made a test / sample donation on
    To the project - Incline Path
    Which setst the campaign for the transaction
    <input name="Campaign" type="hidden" value="Incline to Sand Harbor Bike Path">

    And the campaign for the Item :
    <input name="Campaign1" type="hidden" value="Incline to Sand Harbor Bike Path">

    So for my test donation it submitted the data and I did it again to the faas form verification url and it did show the transaction campaign IS being sent.

    But it resulted in the CP Data sent to salesforce shows that the transaction campaign is blank , but it did push through the item campaign.
    But since the autoresponders only fire off of the transaction's campaign, the autoresponders are not firing.