I'm using Dynamic Form 2.05.03 with DNN 4.05.01. I'm not able to get a form field to load the default value using a SQL query using the value from another fields as input.

I have two fields with short names of Ref and Name. The value for Ref is passed on the query string. This value is retrieved without any problems.

I'm trying to load the value for Name (the 2nd field) using the following SQL query...

select lastname+', '+firstname as DefaultValue from members, registrations where members.memberID=registrations.memberID and registrations.regID=$(Ref)

If I change $(Ref) to a hard coded value (ex. 12) then I get a value so I know the query is correct. I suspect the $(Ref) is either not being interrupted correctly or is being process before it's value is pulled from the query string.

Is there a way to make this work in 2.5?

Paul,

Hi. I believe there is a way to make sure work but... You have to have 'question one' cause a postback. The way to do this is to create a question event, where the 'question one' which is the question with the short field name of Ref, is the postback question. It doesn't really matter what the question event type is (for example you could set it so that it 'unhides' a previous question which isn't even hidden to begin with. Just as long as that question causes a postback.

Check out this demonstration as well which focus's on dependent dropdownlists that reference each other. This is specifically what you are needing I think.

-Chad

To do a postback doesn't the field need to be a combobox? If so, then I'm not able to set the default value from the query string plus doesn't it require a user action to cause the postback?

Well.... To do a post back the field doesn't have to be a combo box, but it does currently have to be either a combo box, checkbox, check box list, radio button, listbox, ummm... I think thats it. Currently textbox fields cannot cause a post back (we are working on that)...

But...What you are wanting is a little more tricky I believe because of the querystring variable and the postback. Since the form doesn't render the page and viewstate/form variables initially its difficult to use these types of implementations that involve querystring, multiple combo box's, SQL options, and a combination of these together. This why we just recently introduced (in 2.6.54 which is the latest released version that should be posted at this time) a few new options and features that allow for this.

Please check out this thread related to using querystring variables that can interactive with SQL options and so forth.

I still believe for the query to function properly though on the 2nd field its going to either require a postback or you are going to have to set a default value. What I mean by default is in your query you might use a stored procedure and pass it the parameter $(Ref) but if that parameter is empty the stored procedure would default it to the initial item that it should be (say a number like 12), then after the user selects another option the postback will occur and return the right results as well.


-Chad