Attendees becoming contacts, no use of the "#" symbol, and list field limit?

[lindsaymakesart]

Hello there,

We had the layout related list and button correct, but I will admit, it was not clear to me that the "Attendee Details" = Attendee Temporary Contacts, and that by clicking on the first name it would bring us to the actual temporary contact management page. Thank you for giving us this Aha. The fields are even mapping correctly! I would suggest that, for literal folks like myself, that future improvements to Events considers changing the term of Attendee Details to Attendee Temporary Contacts, or something of the like.

This is exciting to move forward, thank you again. Now, if only we can figure out why we are receiving the message "j_id0:j_id2:j_id3:j_id24:j_id76:j_id78:0:j_id 80:j _ id89: Validation Error: Value is not valid" on submitting second ticket purchases AND why we are receiving a payment error as described before.

[CnP.Support]

Lindsay,

Sure.. the name change is easy and I will see if we can make it clearer in the next update due out next week. The new update will incorporate another request by another client.

The error that you are describing was found and the solution sent in my earlier answer. Please review that and let me know if that is the problem. Our tests show that the error ONLY occurs in the presence of a carriage return in the pull down menu field.

[lindsaymakesart]

I see, thank you for clarifying about which error you were addressing. So, to make sure I'm understanding correctly, are you saying this error is caused by the user trying to enter a carraige return in the attendee ticket form itself (on the user end, not the back end)?

[CnP.Support]

Lindsay,

This has to do with the backend where you have entered the values for the pull down menu.

Carriage return is causing validation issues in Salesforce and the error you see is caused by Salesforce trying to add the value to the field. Make sure all fields are value followed by semicolon and no carriage returns.

[lindsaymakesart]

Hello again,

I've just copied and pasted the list into Notepad this time, ensured no carraige returns, and pasted back into the list. I then entered in a few test people, and it is working now. Hooray! There must have been a hidden carraige return in there somewhere... whatever it was, thank you for being persistent with me.

I am going to get in touch with our AmEx user and try one last time to run their card.

Thank you again for all of your help,
Lindsay

[CnP.Support]

Great news indeed.

Glad to see all is working.

Once you find out about the AMEX situation please let me know. If we have more information we can contact the processor and find out why this is happening.

[lindsaymakesart]

Good Monday Morning,

We have just tried several times to run an AmEx card through, and are still receiving the error: "Credit Card Number Must be a Valid Number."

The error window pops up so quickly, without any kind of perceivable page loading lag time, that I wonder if it even proceeds to the processor? Please let me know what next steps are.

Thanks,
Lindsay

[CnP.Support]

Lindsay,

Would you please set up the following user and give it admin rights: [email protected]

I will have one of our testers login to your account and review your settings.

Please let us know when it is setup so we can proceed.

[[email protected]]

Hi,

My name is Ryan - I work with Lindsay at Nature Consortium. The account is setup with admin rights - what's the best way to deliver the pw?

[CnP.Support]

Ryan,

Don't worry about the password. The reason we give you the email is because we will be able to set up the password when we first login.

I will let you know what we find out.

[CnP.Support]

Ryan,

We still have not received the account notice from Salesforce.

Did you set the user as instructed? [email protected]

Salesforce should send us an email with a link to setup the password and login but we have not received the email yet.

[CnP.Support]

Lindsay,

Please check the following release note: http://forums.clickandpledge.com/showthread.php?t=962&p=2892#post2892

We evaluated your reported issue and found out that under certain conditions the validation for the AMEX process is having problem with identifying the card. An update has been released to address this issue.

Sorry for the inconvenience.