Announcement

Collapse
No announcement yet.

Trouble setting up a simple donation form

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

  • #31
    @JoeMoran,

    Yes we do realize it as we battle with it as well. Unfortunately this is not our software and is VBulletin. I have personally posted so many image captures and then removed it and posted it again as JPG since PNG's show up very fuzzy and small.

    We will review the image and get back to you.
    Regards,
    Click & Pledge Support Department

    On Salesforce? Help us by rating our app: Click & Pledge Donor Management on AppExchange

    Join us @ the educational webinars: https://clickandpledge.com/webinars/
    Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
    Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

    Comment


    • #32
      Got it. Thanks!

      Comment


      • #33
        Just checking in on this again. Thanks!

        Comment


        • #34
          Good day!

          Please see the images below:
          Click image for larger version

Name:	SKU.jpg
Views:	17
Size:	82.2 KB
ID:	20464




          click on the advanced tab shown in the following image and enter SKU value
          Click image for larger version

Name:	GF-SKU-2.jpg
Views:	17
Size:	19.8 KB
ID:	20465


          Added based on the post # 45 - each item in the radio button needs to have its own hidden field if SKU is to be assigned. SKU's are per radio button option and cannot be assigned by only 1 hidden field for multiple radio button options. It is important to also point out that the value field has to be unique for each radio option, e.g. the same "Value" cannot be assigned to multiple radio button options.
          Last edited by CnP.Support; 11-26-2015, 10:52 AM.
          Regards,
          Click & Pledge Support Department

          On Salesforce? Help us by rating our app: Click & Pledge Donor Management on AppExchange

          Join us @ the educational webinars: https://clickandpledge.com/webinars/
          Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
          Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

          Comment


          • #35
            Also, is there a way to set the Opportunity Name? Right now, it just shows up as the selection.

            Comment


            • #36
              Good day @Joe,

              The best way to do this is with C&P Settings > Customize name based on SKU

              The item name is posted by GF and not something we have control over. The label is what posts to us.

              Using the SKU and name customization is the only way it can be done and the most flexible way.
              Regards,
              Click & Pledge Support Department

              On Salesforce? Help us by rating our app: Click & Pledge Donor Management on AppExchange

              Join us @ the educational webinars: https://clickandpledge.com/webinars/
              Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
              Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

              Comment


              • #37
                For some reason, our auto-responder is not being triggered. We have it set to trigger based on Campaign name, but the form uses Campaign ID. Could that be why it isn't working?

                Comment


                • #38
                  Good day!

                  Yes- the autoresponder responds to the "Campaign Name" as the ID is not the general case.

                  Please try to post the campaign name.

                  In most cases the easiest way to track issues is using SKU for everything. It is the most versatile solution.

                  BTW: Please start a new thread when the topic changes. This keeps the threads relevant to the original post. Thank you.
                  Regards,
                  Click & Pledge Support Department

                  On Salesforce? Help us by rating our app: Click & Pledge Donor Management on AppExchange

                  Join us @ the educational webinars: https://clickandpledge.com/webinars/
                  Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
                  Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

                  Comment


                  • #39
                    Okay, I'm at my wits end. The donor is being charged a different amount than what is being selected in the form. Why on earth would this be happening? This is very troubling. Please advise ASAP.

                    Comment


                    • #40
                      Good day!

                      Do you have an order number that we can check?

                      The screen you are showing - is that what shows on the receipt?
                      Regards,
                      Click & Pledge Support Department

                      On Salesforce? Help us by rating our app: Click & Pledge Donor Management on AppExchange

                      Join us @ the educational webinars: https://clickandpledge.com/webinars/
                      Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
                      Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

                      Comment


                      • #41
                        Good day @Joe,

                        Here is the result of our extensive test of your scenario.

                        We duplicated your exact values in our test environment as shown below and the results are correct if the payment is done without any interim errors, e.g. missing expiration date, etc. Click image for larger version

Name:	Step 1.jpg
Views:	23
Size:	75.3 KB
ID:	20596




                        As shown above the results are correct.

                        We now forced a warning by not selecting an expiration date for the card and noticed that GF changed the selection from the original $35 to $1000 (the last value in the list): See below: Click image for larger version

Name:	Step 2.jpg
Views:	15
Size:	43.8 KB
ID:	20597



                        Based on repeated tests if an error occurs GF changes the selection to the last value in the field. This behavior was corrected by making the VALUES unique as shown below: Click image for larger version

Name:	Step 3.jpg
Views:	16
Size:	59.5 KB
ID:	20598




                        In your case you have all the values the same and that is confusing GF in case of an error. The following is what you have: Click image for larger version

Name:	All-Same-Values-GF.jpg
Views:	15
Size:	41.3 KB
ID:	20600


                        The values you have entered are all 5110 which based on the Gravity Form manual will cause problem. Based on GF definition for the "Value"

                        https://www.gravityhelp.com/document.../field-object/

                        The value to be stored in the database when this choice is selected. Note: This property is only supported by the Drop Down and Post Category fields. Checkboxes and Radio fields will store the text property in the database regardless of the value property

                        Using the same value for all entries will result in wrong record to be saved in the database.

                        Hope that answers your question. I would like to stress that this is not an integration issue by any means but core Gravity Form functionality and totally outside our scope and control.
                        Last edited by CnP.Support; 11-26-2015, 07:37 AM.
                        Regards,
                        Click & Pledge Support Department

                        On Salesforce? Help us by rating our app: Click & Pledge Donor Management on AppExchange

                        Join us @ the educational webinars: https://clickandpledge.com/webinars/
                        Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
                        Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

                        Comment


                        • #42
                          They are all set as 5110 because I followed instructions in a previous post about how to assign SKUs. This is conflicting information. If I return the values back to the amounts, how will SKUs be assigned?

                          Comment


                          • #43
                            Good day!

                            So we can correct the previous post may I ask which post you are referring to?

                            The post we had earlier in this thread states for the values to be v1, v2, .. which means that for each option a hidden field needs to be set up to identify the SKU.

                            In this case if you want to have the same SKU for all items then you need to create hidden fields for each item in the radio button.

                            Please see the image which was posted earlier [thread #34]: http://forums.clickandpledge.com/for...0463#post20463

                            Are you referring to that image or any other post?

                            In the integration we are taking each item and matching it against the referenced hidden field and tried to force it to comply with Salesforce mapping. GF does not have any feature such as SKU and with hidden fields we are adding such functionality. It is a bit awkward but there is no other way - each item needs to have a separate hidden field for its SKU.

                            Hope that answers your question.
                            Regards,
                            Click & Pledge Support Department

                            On Salesforce? Help us by rating our app: Click & Pledge Donor Management on AppExchange

                            Join us @ the educational webinars: https://clickandpledge.com/webinars/
                            Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
                            Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

                            Comment


                            • #44
                              The post was rather confusing since it was screen captures without instructions of any kind. A simple explanation would be helpful.

                              Comment


                              • #45
                                Good day!

                                We will add more instructions to the manual.

                                The third party integrations get a bit confusing even for us. We use their API and at times are not familiar with their peculiar ways of doing things. As clients face issues we try to figure out how to address them. It is not the most efficient way but we cannot find any other way.

                                We are going to add the cases presented in the forum added as example cases in the manual. It will be quite helpful if we know all that has caused confusion so we can add them as examples.
                                Regards,
                                Click & Pledge Support Department

                                On Salesforce? Help us by rating our app: Click & Pledge Donor Management on AppExchange

                                Join us @ the educational webinars: https://clickandpledge.com/webinars/
                                Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
                                Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

                                Comment

                                Working...
                                X