Hi, it's me again

I have a reg form that contains a RadioButton Group.  I want to generate the options via an SQL call to a stored procedure.

The SP accepts a single argument, the $(UserID).  From this value, the  QuestionOption and QuestionOptionValues can be generated.

I call the SQL like this (in the 'SQL Driven Options' box):

exec GenerateUpgradeOptions $(UserId)

I cannot for the life of me get $(UserID) to actually be passed - indeed the 'Test SQL' generates an error.  If I replace $(UserID) with a 'hardcoded' userid like:

exec GenerateUpgradeOptions 278

It works fine and generates the correct options and their values (though it's only valid for Userid = 278 obviously).  Is there a way to pass in the current $(UserID) to this procedure?  Any ideas?

Thanks.

David, I have tried various combinations of this and have had no luck.  To keep things simple, I first just created a simple textfield for ease of testing (located after the username/password/confirm password fields).

I tried the following as part of the SQL driven content for this text field:

select userid AS DefaultValue from users where userid = $(UserId)

The field is empty when displayed.  I have a Username field as the first field in this form, which does display the logged in username.  I also tried just hardcoding the userid as so:

select userid AS DefaultValue from users where userid =331

Same result (blank field).

So, since I have a Username field on the form (which does display the Username properly) I thought I would try something 'sneaky' like:

select userid AS DefaultValue from users where username = '$(Username)

That also results in an empty textbox.  So far I have been unable to get any of these to work.  The documentation does indicate UserID is valid here, but niether that, nor any existing field name (Username) results in anything other than a blank text field.  

I also found this thread:  https://www.datasprings.com/Products/Product-Forums/tabid/727/forumid/3/tpage/1/view/topic/postid/862/language/en-US/Default.aspx#862

Is this really the case?  Is there *anyway* for my stored procedure (or any other SQL driven field) to be able to key on the current user in someway?  Surely this must be possible and I'm just missing something...?

Not sure what to try next.

For kicks, I tried the exact example given below the SQL field entry box: 'select count(*) As DefaultValue from users'.  This to ends up with an empty textbox.  What could be the problem here? 

For kicks, I've created a test reg form on beta springs.  It's at: http://www.betasprings.com/DynRegis...aspx  (I wasn't able to create a new page - Got a 'primary storage full' error).  The module is called ' Jon's SQL tests Hidden field. visible test field using sql'. 

It has a hidden field, a textfield, and an radiobutton field, all driven by SQL.  Only the radiobutton field actually works, though tokens like $(UserID) (or any others I tried) do not work.

The hidden field is not found at all via 'View Page Source' in FF. 

Clearly the version of DR on betasprings is newer than what we have (3.2.70), but it still seems to have the same problems.

Any pointers would be appreciated.

David, sorry for the delay in response.  I was not aware that SQL defaulting would only work for initial registrations - I guess if the fields were not tied to core dnn fields, I didn't see why that should not work.  I was aware that 'Test SQL' would not work when tokens are involved.

For the radiobutton, you asked 'So if you go to host, sql and enter:
exec GenerateUpgradeOptions 278'

Yes this works fine as I mentioned previously.  It's only when I supplied $(UserID) that it did not work.

What records get generated? Are those columns names 'QuestionOption' and 'QuestionOptionValue'? The query would need to return those two columns specifically.

Yes, when called directly as mentioned above, the correct values are generated.

The $(UserID) query is referenced in SQL options a lot so I am not sure why it wouldn't work. I know the SQL Default is only for initial (default value) registrations and not when you are signed in so I understand why that wouldn't work, but not sure. Ill review the beta springs page you created.

Yes, and it was even documented that way which is why I tried it.  On the betasprings site mentioned above, I created a radiobutton that was init'd via SQL.  Using all 'hardcoded' values works (As you can see).  Add $(UserID) and it stops working.

At anyrate, I decided to ditch DR and give Dynamic Forms (DF) a try.  With DF, it all worked as expected, and that's what we are now using for the upgrade form.