Hi, I am a new user (purchased today).

Do you have SQL that I can use to change the value of a DNN profile element?

I have found SQL to retrieve a profile field, but not to update it, and my SQL is a bit too shaky to want to mess with DNN's DB without being sure I know what Im doing.

Thank you for responding so quickly.

I do understand that I can tie a dynamic field to a DNN core field. 

However, I want to be able to access profile fields from modules OTHER than yours, modules which allow programming (specifically listx and open smart module).

I want to use DR to update these fields when people sign on, but at other times I may need to change them myself. I just basically want to have control over them, inside or outside of DR.

So I need SQL to update a DNN core field.  Or, if that isn't possible, I will not link the fields to the core and I would need SQL to update one of YOUR core fields.

Actually,  before I bought, I thought I understood from an email to your support yesterday that this was not a big deal. Hope so, cause I have a small brain.

Again, thanks again for your really fast response.

Did either you or I misunderstand my snowcovered question ?

Below is the conversation, I took it to mean that I would be able to both read or update profile fields myself should I need to do so, using SQL. I have found SQL that works to read such fields if they are bound to the DNN core, I just would like to be able to update the value of the field. I do not need to be able to create or delete it.

Question:

Hi. I have questions about access to your fields. Lets say I use your module to add a new registration field (myNewField), then UserX registers and your module creates a value for his myNewField. What are the ways that I can access that field elsewhere in DNN? Can I display it with a token using the DNN HTML module? Can I read it with SQL from another module? Can I easily UPDATE it using SQL in another module? If so, would something bad happen if I update the value of myNewField for UserX using SQL in another module?

Answer:

Hi. Well there are multiple options here. First, you can create an extended DNN Core profile field and you can always link this profile property field to your new Dynamic Registration dynamic field. This way whenever the field is updated (outside of Dynamic Registration) it will still render properly within Dynamic Registration. Additionally, any time the user updates (or registers) it will update this extended profile property in the core so that other 3rd party modules (and modules such as the DNN HTML Module) can then retrieve or render that users profile property. Besides these methods you can also use SQL Events to actually store the data into any table you want to. If you are needing more options, Dynamic Registration also does include its own tables you could pull the information out of if you needed to.

Having DR to adjust default user properties is really simple. Say you want to have a value “mother’s maiden name” on a user and you want the user to be able to insert/view this value both using DNN built in profile editor and in a form using DR.  

So create it in the core DNN user properties editor, make it “visible” and your users should be able to view it and change it using the built in user profile.

Then you want a form somewhere where this value should be updated/created, here is where DR makes it simple. Drop a DR form on a page; use the wizard to create first three fields, username, password and password reminder, maybe hide this three fields to already logged in users by a setting in the form core integration advance settings.  Continue create a textbox question; in textbox question advanced settings connect this question to the core field, your done!

Now you have a form where the user can change this value, this form can now be modified in gazillion ways to accomplish additional things you want but the core “mother maiden name” field will always be viewed/changed from this additional form together with the core DNN default user profile editor.

Two ways to change “mother maiden name” is accomplished, no “sql code” is necessary.