Announcement

Collapse

Information Needed

See more
See less

Custom Questions Mapping - Cannot Save

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

  • Custom Questions Mapping - Cannot Save

    We upgraded to PAAS version 8.1 yesterday. When configuring the custom questions in C&P Settings a value is required in the custom text field. The system will not let you keep the answer value and custom replacement text value blank.

    If I put a value in the custom replacement text field of the custom questions, the system allows the custom questions to be saved. The system does not have an issue allowing the answer value field to be blank, just the custom replacement text value.

    In PAAS version 7.4 this worked just fine and both the answer value and the custom replacement text fields of the custom question can be blank just passing whatever value was entered on the online form.

  • #2
    Good day!

    Strange.. would you please grant us access so we can review your account. If this is a bug we need to make sure it is fixed in the next update scheduled for next week.

    Please grant us access and post your Salesforce Organization ID so we can login and review the issue.
    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


    • #3
      Sure, my org id is 00DA0000000ALDj

      You already have been granted access.

      Comment


      • #4
        I forgot to tell you that you can just delete one of the number 1 values I entered in the custom text column of the custom question mappings just to save. None of the questions should have a custom text value except for the two questions where the answer value is filled in (in memory of/in honor of picklist)

        On those two questions that have the answer value entered, I am still trying to figure out what the question text should be from the C&P support created custom form. Normally, the other fields questions is the <title> value, but this one is a picklist on the custom form and I can't get the value to pass over to Salesforce. My acct is 24617.

        Comment


        • #5
          Good day!

          Sorry about the inconvenience. We have identified the problem and will resolve the bug in the next update due out next week.

          Unfortunately I can't give you a work around as it requires a change in the validation rule. The next update is due out next week and we will post it in the Salesforce PaaS update forum: http://forums.clickandpledge.com/forumdisplay.php?f=54

          Updating release 8 is quite easy and may be done using the C&P Settings > About C&P App tab.

          The release is scheduled for January 9, 2014.
          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


          • #6
            Glad to see we are not the only one with this problem. Question to the OP, we are using the same format (in honor of/in memory of) and want to have the text from the recipient field appear via the custom question.

            I was trying to set this up for the first time today and getting the same cannot save error, I just want to confirm this was working for you prior to the recent PAAS update so I can stop looking for a work around and wait it out for the time being. Thanks!
            Last edited by [email protected]; 01-03-2014, 03:25 PM.

            Comment


            • #7
              Good day @[email protected]

              Would you please grant us access to your account so we can review your instance. We are trying to test all reported instances to make sure the solution works.
              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


              • #8
                Access granted, Org ID: 00DA0000000aYkB

                Comment


                • #9
                  Good day @[email protected],

                  Your concern is valid and thanks for letting us know, we are able to duplicate the issue in our instance. This will be address in our next release which is due in next week. We do apologize for any inconvenience.

                  Thanks,
                  Support.Department

                  Comment


                  • #10
                    Has the patch been released to fix this issue of saving custom questions? You had indicated it was scheduled for 1/9/2014, yesterday.

                    Comment


                    • #11
                      Good day!

                      We are still working on the issue. Here is the problem we are facing and why the release has been delayed - we tried to release it today but it was delayed.

                      The C&P Settings page includes a lot of queries and scripts in a single page. When the Settings was released it we did not realize the Salesforce limitations when accounts have 100+ custom fields added to their any of the 3 objects we deal with, namely Contact, Account, and Opportunity.

                      We have had reports of Salesforce viewstate error with clients that have over 100 custom fields added. The new release 8.0 has a new feature for custom lookup as part of the mapping which is causing this problem. By changing a few things we have managed to make it work for the existing fields that are mapped but adding one more will cause the viewstate error.

                      Next week we will release the latest update with a few patches but this patch cannot be released since it requires a total restructuring of the C&P Settings. This is the #1 priority with the team and the entire team is now working on moving the C&P Settings into separate pages and into the new design.

                      We apologize for the inconvenience but dealing with Salesforce limitations is a problem at times. Our program is working fine without any issues, it is Salesforce that causes the issue because of the number of objects in the account. 100+ custom object is just incredible. I will keep you posted.
                      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


                      • #12
                        Is it possible to downgrade to 7.x until an update is released? Do you have any idea on how long this total restructuring of the C&P settings would take to do? I am just looking for a time range. Two weeks? Two months? I can delay another week, but I need a solid workaround plan with a line in the sand date. I need to communicate and coordinate the go live dates of our entire donation migration. Click and Pledge is just one part.

                        We can't go live without credit card payments working. It is a critical step to our complete donation management migration from another platform.

                        By the way, the reason for the incredible number of custom fields on the account object is because of FinancialForce. They add a ton of fields to extend the account object.

                        Comment


                        • #13
                          Good day!

                          Thank you for the added note- I don't have any experience with the Financial Force application. That many fields to the account object is just incredible. I have heard great things about the package and we have to make sure we are compatible with its extensive additions.

                          We are targeting Friday for the release and this issue is the only thing that is holding the release. We have had 2 other reports of this issue with one account having over 170 custom fields to the Contact and over 100 fields to the Opportunity object.

                          Please give us a few more days. Moving to version 7 for existing clients is not possible since 8 has to be uninstalled and then data migration issues, etc. etc. If needed our support team will help you but I rather wait and have a fix.

                          Sorry for the inconvenience.
                          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


                          • #14
                            Thanks for giving a target release date expectation. Since the fix is relatively soon, I can delay our migration rather than go down the workaround route.

                            Comment

                            Working...
                            X