I have a user complaining that he tried to complete a form using Auth.Net and received an error when trying to submit the transaction.  The form allows for both card and check payments and has been used successfully for both types of transactions.  

Hi David,

Is this happening to all transactions or just to this one customer? What is the exact Dynamic Forms version do you have. Also, what DNN version are you on?

I also found this blog. Does it help?
http://www.aspnetajaxtutorials.com/...ument.html

Thanks,
Candace

We also had this issue and managed to track it down to a combo box that has "Allow user ability to add item?" Ticked

.NET picks up on a change to the control and treats it as a possible security risk

Apart from relaxing security, is there a fix for this?

DC

Hello DC,

If you need this type of functionality, a work around that you can implement is:

1.) Add an item to your Combo Box called "Other" with a value of "Other"
2.) Add a new Question of type Textbox with the Question Label of "Other" and check the feature under Advanced Field Options -> Hide until Forced Visible by Question Event.
3.) Create a Question Event that fires only when your Combo Box's selected value = 'Other'. Then display the Textbox that was just created.

Where ever this Combo Box data source is located, Host -> List or a custom SQL table, I would recommend using a SQL Form Completion Event to store this Other value if provided into your Combo Box data source.

Please let us know if you have any questions.

Thanks,

Ryan