I am setting up a DNN site to take requests for free samples, but I don't want to send a sample if the same person has already successfully requested a sample within the last year. To do this, I need to manipulate the form variables and then make a couple of queries to my own, non-DNN SQL DB to make sure this person isn't a repeat. 

Hi Matt,
I think that this process can be done with Dynamic Forms this way as one way to do it. What if every time some one does the request for the free sample their contact info and the current date was entered into a table ( i.e DF_Free Samples table)? this is done through a sql completion event and a insert is made into this table if the person isn't previously in the table. You want every member in the table to be unique based on at least something like address of where the item is sent. So maybe only one household gets the item for free. This table will have a field that is for date when free sample is sent. Everybody gets a free sample if the date field is empty. When YOU send out a sample the date field gets filled with today's current date. Also when someone orders a free sample in the completion event an update is run to delete all records in the table that have the date field for free items sent with a date to be equal to or greater than 365 days. That way you are always cleaning out records for free samples that are a year old. This allows anyone to get back into the table after a year has passed. So in short you have a form where you are running the insert into the table for the customers and then an admin form set up where you guys to the filling of the orders. No need to worry about postback processing this way.

Thanks


I would expect that you would have a note in the form that when people get the free sample they can only get one per year.

Hi Don,

I truly appreciate the brainstorm on this one, but unfortunately our internal fulfillment processes are not able to be reworked to this extent. In addition, we have to do a bit of variable gymnastics to make try and anticipate how folks might slightly tweak their address etc to get around the verification.

Any way to do my original question?

Thanks,
Matt

Hi Mat,
The way I understand things dynamic forms has Initial SQL Rendering/Bind feature in module configurations that allows for a sql stored procedure to be called prior to form submission but after certain values have been input into the form by the user ( i.e. name, address, etc). These values can be required fields and will be parameters to the stored procedure to your database. As required fields the form can't be submitted until all the needed values for the stored proc are supplied. A return value like Pass or Fail can be brought back into a hidden field in the dynamic form and serve as a flag that is processed by completion events in the form upon form submission. The completion events can then use the hidden field value to re-direct the user to one of two message pages. One message page will be for displaying "Sorry you have already received your free sample for this year". The other message page will be for displaying "Thank you for submitting your request for our free sample. Your product will be sent to you soon ( or something like this)".

Mat, the process above is not done through HTTP post because I have not seen any way to accomplish what you are asking for with HTTP post in Dynamic Forms but I have seen 1) Initial SQL Data Bind, and 2) Re-direct completion events do the kind of thing that you want. Some variation may be needed and I am also assuming that your current non DNN database has the needed data to be queried through a properly structured stored procedure to do what you need.

To actually look into accomplishing this you may want to get a Premium Support quote. At any rate, I hope this gives you something to go on.

Thanks