Announcement

Collapse
No announcement yet.

API uses different parameters

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • CnP.Support.AM
    replied
    Lucy M

    Both of the transactions initiated before you fix the form and the Order number: 20607-190402170230325 processed from SFVT. However, please follow the steps below and update the Campaign for both of the order numbers:

    Click image for larger version

Name:	Camp1.jpg
Views:	53
Size:	89.5 KB
ID:	45565
    Click image for larger version

Name:	Camp2.jpg
Views:	45
Size:	52.7 KB
ID:	45566

    Click image for larger version

Name:	Camp3.jpg
Views:	51
Size:	147.1 KB
ID:	45567


    Please update the Campaigns as specified above and let us know what comes in for next installments.

    Leave a comment:


  • Lucy M
    replied
    Ok thanks for showing that to me. I'll make sure those get entered correctly from the virtual terminal. Besides that, we are still experiencing the original issues with our recurring gifts being coded to the wrong salesforce campaign despite the changes that have been made to both WEC (account 20607) and WCV (account 35074) donation pages. Any other suggestions to help resolve this issue?

    Here are order numbers created after the updates made to the web pages:
    Account 20607 (WEC): https://donate.wecprotects.org/
    20607-190402170230325

    Account 35074 (WCV): https://wcvoters.org/donate/
    35074-190401111503246

    Leave a comment:


  • CnP.Support.AM
    replied
    Good day @Lucy M

    We just reviewed the above order number and found that it is NOT processed from FaaS form. We found that it processed from C&P Virtual Terminal of your Salesforce instance and there is NO transaction campaign included while processing the transaction.

    Click image for larger version

Name:	No Campaign2.jpg
Views:	62
Size:	44.5 KB
ID:	45531


    Click image for larger version

Name:	No Campaign1.jpg
Views:	53
Size:	29.4 KB
ID:	45532


    Leave a comment:


  • Lucy M
    replied
    Hello, web developers made that change to both donation pages on late Thursday 3/28/19. It did not resolve the issue with our recurring gifts and it is now causing a problem with our regular donations made online. Any online donation is now coming into salesforce with no salesforce primary campaign. For example, see this order number: 20607-1903291913151763630

    Please advise on how to fix the issue with the one-time donations made through the websites (this is the most important to us to function properly), and then hopefully another way to fix the original recurring gift salesforce coding problem.

    Leave a comment:


  • Lucy M
    replied
    Thank you, I'll inform them to do that and follow back up if there are any other issues.

    Leave a comment:


  • CnP.Support.AM
    replied
    we just reviewed your donation page and found that the Alias name is not listed correctly.

    Click image for larger version

Name:	alias.jpg
Views:	66
Size:	77.7 KB
ID:	45473

    As you can see there is ** before and after the alias name which is not valid. You need to remove that in order to pass that ConnectCampaignAlias.

    Leave a comment:


  • Lucy M
    replied
    Sure thing. I granted access for 1 week. We have 2 C&P accounts that are connected to our Salesforce instance. The order numbers are for transactions after the website developers added that specific node on both of the web donation pages.

    Account 20607 (WEC):
    https://donate.wecprotects.org/
    20607-190324093827569
    20607-190324100655729
    20607-190323124546891

    Account 35074 (WCV): https://wcvoters.org/donate/
    35074-190324092311762
    35074-190325094148352
    35074-190322091552964

    Leave a comment:


  • CnP.Support.AM
    replied
    Would please share the order number and grant login access so that we can review it?

    Leave a comment:


  • Lucy M
    replied
    Our web developers made that change in our code, but we are still seeing the same issue with our recurring gifts. In C&P, the last transaction of our recurring gifts are coded to the correct Connect campaign (which is associated to our monthly donor Salesforce campaign) but it is not being coded correctly in Salesforce. Any further suggestions to help fix the issue?

    Leave a comment:


  • CnP.Support.AM
    replied
    Yes, you are correct.

    Leave a comment:


  • Lucy M
    replied
    Ok thank you! As a point of clarification - if we enter the Connect Campaign Alias, all donations made through that website page will be assigned that Salesforce campaign associated with that Connect Campaign Alias. But, if i assign a different campaign alias to the last recurring installment (that was originally made through this website page), all of the recurring gift installments will be assigned to the connect campaign of the last recurring installment, not the connect campaign on the website page. Is that correct?

    Leave a comment:


  • CnP.Support.AM
    replied
    Good day @Lucy M

    We reviewed the above form and noticed that you have commented the WID node but didn't include the ConnectCampaignAlias node as specified in our previous post. Please include the following node to pass the correct Connect Campaign.

    <input type="hidden" name="ConnectCampaignAlias" id="ConnectCampaignAlias" value="Insert Campaign Alias here" />

    Regarding the above recurring order numbers, those recurring not initiated after you fix. Those recurring are initiated before you try to fix it so, in order get the correct campaign for above recurring, you will need to go to the last recurring installment order number and update the campaign there so that moving forward it will assign the correct campaign.
    Last edited by CnP.Support.AM; 03-20-2019, 06:24 AM.

    Leave a comment:


  • Lucy M
    replied
    Hello, I am the Salesforce Administrator for Washington Environmental Council. The issue mentioned by sabdap has not been resolved with the removal of that tag in our websites. I've granted C&P access to our Salesforce for one week. Here are a few order numbers to reference (recurring transactions that happened after the code was removed from our web donation pages):
    C&P Account 20607 (Washington Environmental Council):C&P Account 35074 (Washington Conservation Voters):

    Leave a comment:


  • CnP.Support.AM
    replied
    Good day @sabdap

    You simply need to replace the following node in your custom form:

    <input type="hidden" name="WID" id="WID" value="63028">

    TO

    <input type="hidden" name="ConnectCampaignAlias" id="ConnectCampaignAlias" value="Insert Campaign Alias here" />

    To get Connect Campaign Alias, go to respective Campaign and under Campaign details >> Basic Information >> here you will find Campaign Alias field which is an extension for the Campaign's URL.

    Hope that helps. Please check and let us know if we can be of any further assistance.

    Leave a comment:


  • sabdap
    started a topic API uses different parameters

    API uses different parameters

    We manage the web pages for Washington Environmental Council. They were instructed in Live Support that the custom donation forms on their website need to have their parameters modified to pass the correct Campaign information to Salesforce.

    These are links to the affected donation forms:

    https://donate.wecprotects.org/
    (any additional forms on your site that contain html similar to this: <input type="hidden" name="WID" id="WID" value="63028"> )
    How should we modify the HTML to operate correctly?"
    Last edited by sabdap; 03-04-2019, 02:02 AM.
Working...
X