Hi there

I'm using the Collection v5.0 of DR and ran into this problem.

I created a profile page with a field that is associated with a DNN Core field. However, the field needs to be a list of radiobuttons or just a list.

I noticed that it works correctly if I don't associate the field to the DNN Core field. When I edit and save the profile, and come back to the profile later, the profile picks the field that was selected previously.

If I attach the field to a Core DNN field, it saves the data correctly in UserProfile table, but when I come back to the profile, it shows the field not-selected at all - ie the radio button is not selected or the list item is not selected.

In both cases, checking the UserProfile table does put in the correct value. So what did I do incorrectly? What doesn't the profile come back as a selected value? Thanks.

Hi Reuben,

A couple questions:
1. Is the field you are mapping to a text DNN profile field or another profile property definition?

2. If you change this to a combo box field type instead of a radio button, does it work then?

3. What is the specific version it shows you are running under host, extensions?

Thanks,

Chad

Hi there

Thanks for the quick response. To answer your questions -

1. It is mapping to a DNN Profile Field of type LIST.

2. If I change it to a combo box, it does NOT select either. Similar to radio buttons.

3. I'm using Dynamic Registration 4.20.20

Thanks.

Hi Reuben,

I believe in order for Dynamic Registration to property work / map with DNN Core profile fields you have to map this field type to a "TEXT" field type and not a specific other field type such as LIST. I would have to research more to know why exactly but I think this is likely causing the problem. If you switch the profile property to a type of "TEXT" this should work ok.

Thanks,

Chad