Announcement

Collapse
No announcement yet.

Connecting FaaS with Checkout Page

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

  • Connecting FaaS with Checkout Page

    OK, so I'm separating this out from an earlier thread I somewhat hijacked. I'm creating a form using FaaS, and I've created a checkout page that it refers to. When I submit something, I get an error: on=Xml Error The element 'CustomField' in namespace 'urn:APISchema.xsd' has incomplete content. List of possible elements expected: 'FieldValue' in namespace 'urn:APISchema.xsd'.

    Three Questions:

    1) what does this error mean?
    2) Is there a list of errors that could be generated, and what they mean?
    3) Is there a way to output the error to my Error page so that I don't have to sift through the %20s in the URL?

    thanks,
    benjy

  • #2
    FieldValue & FieldName

    Benji:

    The error is exactly what it says.. the problem you have is with the custom questions.

    Custom questions need to be posted in 2 parts:

    FieldName
    FieldValue

    So here it is:

    <input name="FieldName" value="Employer" class="text" type="hidden">
    <input name="FieldValue" class="text" type="text">

    The above will pass to the FaaS the field Employer as the name of the custom field and the value is what the end user will type in the field called FieldValue.

    So in a form that needs to collect the following:
    • Employer
    • Occupation

    You need to do the following:

    <input name="FieldName" value="Employer" class="text" type="hidden">
    <input name="FieldValue" class="text" type="text">

    <input name="FieldName" value="Occupation" class="text" type="hidden">
    <input name="FieldValue" class="text" type="text">

    Hope this helps.

    Let us know if we can be of more assistance.
    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
      OK, I think I got it...thanks.

      I edited the text input fields following your recommendations, but what about grouped radio buttons that need the same "name" atrribute?

      Also, now that I made the changes, I'm getting the Error Page with the message on=Decline.

      I have OrderMode = Test and TransactionType=Authorize. What does on=Decline mean?

      (NOTE: you really really really ought to implement a better error message system -- or at least have a repository of errors, what they mean, and how to fix them.)
      Last edited by benjyrose; 03-18-2010, 08:16 PM.

      Comment


      • #4
        Benjy:

        Look at the following. With the FaaS you can have 1 radio button set and set it as follows. We are going to come up with a naming convention so you can also use multiple radio buttons but for now you may only use one.

        I agree- we will work on the error messages.

        Sample radio-button form element:

        <input type="hidden" name="FieldName" value="Occupation" class="text" >
        </p>
        <p>Occupation:</p>
        <p>
        <input type="radio" name="FieldValue" value="Engineer" />
        Engineer<br />
        <input type="radio" name="FieldValue" value="Doctor" />
        Doctor<br />
        <input type="radio" name="FieldValue" value="Lawyer" />
        Lawyer</p>
        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