Hello,

I am running DF 2.5 on dnn4.8. I have a form1 that has a sql completion event to insert a record on save and also a redirect event go to the next form2. However, it seems to go to form2 even if there was a sql error. Is there a way to change the workflow on a sql error?

For example. From1 has a sql completion event:

insert into table1 (UCID) VALUES ($(uniquecompletionID))

Is there a way in Form2 to SELECT count(*) from table1 where ucid = $(uniquecompletionID) and then redirect the user (or display a friendly message to start over) if the record does not exist?

Hey Chad,

That new SQL event would satisfy half of the issue. It will solve the issue of proceeding a form in error. However that would not solve the issue if a user enters a step in the workflow out of order.

For example From1 creates a record. Form2 uses the record for further processing. The new SQL event will not allow the user proceed from form1 to form2. However what will happen if the user enters the url for form2 directly. form2 needs to know (using current session or query string variables) that there is no previous record associated with it.

The new event that you suggest will catch the error at form1 submit, but offering validation onload of a second form will really make things flexible when creating a workflow. Possibly an onload sql event that can hide or show a DIV in the future?

For a quick fix. I think if the custom javascript file can read querystring or session variables I would be able to do something with the window.onload object combined with unique completion id. (i.e. if ($(uniquecompletionID)=='') window.onload = function1() else window.onload=function2)

Thanks for the quick response!

That would work if Form1 should only be submitted once per user. After the user completes the workflow successfully we will have the same issue (unless somewhere in the workflow we revert the role of the user).

This also would not work for anonymous users for obvious reasons.

Comparing to a real life scenario, lets say you want to have an elaborate quote system. you dont want to force the user to register to fill out a quote since it might discourage some quote leads and potential sales. However you might have an initial form1 for some data, and then form2 to add items/services to the quote which will vary depending on the data in form1. You can't do this in a single form since in form2, it can potentially loop to add additional items (i.e. form2 event: "add more items.click" ->insert line item ->go to form2 again ... or ... on "complete quote.click" ->insert line item -> go to form3)