When I configure optional DNN fields (e.g. street, city) to be mapped to selected registration fields, the DNN content is not displayed in the registration form.

 

Thomas

Thomas,

Hi. This is actually working 'as designed' originally but we will be changing this functionality within the next release (due out in early January). Basically the issue is that it saves the data to the DNN extended core field but for some user requirements they would prefer to have the users responses as the master response and not the core. In other words, lets say you had 2000 users and they all had a Dynamic Registration response for a dynamic field called 'Company Name'. Well if you just enabled the linking core field it would basically never show users their dynamic response, it would always show them the core response. If the user updated their information it would save it in two places.

This being said, we have found that MANY users do not have those requirements :)

With v2.4 you will be able to specify from within general settings which option or it will just automatically be defaulted to force the values from the core.

-Chad