Maybe there are workarounds on some of these? Although I think a couple of them are just bugs exposed by the type of form I'm trying to build.

* when pulling from a custom profile list, it would be nice if the sort order was retained. But I also haven't looked close enough at it yet to see what sort by might force it in the sql query.

* question events need some sort of inheritance. A combo1 selection reveals combo2; a combo2 selection reveals textbox1. Changing the combo1 selection hides combo2, but doesn't hide textbox1.

* a text/html question type can't be saved when using the rich text editor (FckEditor provider), but only when switching back to the basic text box before trying to commit the save.

* I've got both client & server side validation set, but can't get a combo box to preselect with a default value set in a question event

* nested question events would sure be nice

* an event to enable/disable a form control in a question event would sure be nice too

* DNN core field checkboxes can't be linked (the workaround is to make the DNN field a yes/no list instead)

* can a single dynamic field link to multiple DNN core fields? I know, I should just try it and see...

Great module Chad!

Eric,

Yes that will work and help out many users so thanks for posting that.

On some of the other items you brought up I was waiting to do some more research but there are a few enhancements that you will see in future releases to some of them. Here are some general comments on these....

"question events need some sort of inheritance. " - This actually should function out of the box as you mentioned as long as you make sure that the inheritance is setup in a way so that the sort order of the field is setup after the postback field of the other event.

"a text/html question type can't be saved when using the rich text editor (FckEditor provider), but only when switching back to the basic text box before trying to commit the save". My first instinct is to ask if you are running Firefox or IE. We have noticed certain problems with rich text editors with using Firefox (especially since we use section controls within the manage questions area).

"I've got both client & server side validation set, but can't get a combo box to preselect with a default value set in a question event" - This is a bug and we are aware of it and looking into it.

"nested question events would sure be nice" - This sounds similar to the inheritance that we still need to duplicate but sounds the same. What we have already started to implement on Dynamic Forms/Dynamic Registration that will be ready for the next release is the ability to select as many questions to go along with an event. For example maybe you want to hide 10 questions based on the the user checked a box? In the next release you will be able to do this. Right now you have to setup an event for each question you want to hide and we are finding many users who are requesting this enhancement.

"an event to enable/disable a form control in a question event would sure be nice too" - Now on the list and we will do this. Thanks for the suggestion, this will also make the next release for both modules.

"DNN core field checkboxes can't be linked (the workaround is to make the DNN field a yes/no list instead)" - We have documented this as a bug as well and will be fixing it in the next major or incremental release. The work around you mentioned does help for users needing to implement this now though so thanks for the tip.

-Chad

Thanks Chad, good stuff. Yes on Firefox, I'll try other browsers/platforms.

Caught another small bug -

When editing a series of dynamic questions (i.e., not exiting but staying in admin), if a q has a Question Header, that field doesn't clear when editing the next question, and so on. In other words, subsequent edited questions ALL get the Question Header that never got cleared out. Was still using Firefox/mac on this so maybe a non-issue for IE/Win.

Eric

I believe this is a dotNetNuke issue with the RT Editor. I have noticed it quite a lot in the Repository module where, if you fail to remember to switch back to the plain text box, you can't save module settings later. I use Firefox mostly.