Hi everyone!  We're so excited that the newly released Dynamic Forms 3.0 is so well-received!  Thank you!  While we're thrilled with all the new features and enhancements, we also want to share some known issues with this release as listed below.


The following are the known issues at the time of 3.0 release at the time of the release (03.00.10):

    * Not all Rich Text Editors and DNN® versions support AJAX, therefore if you are using Rich Text Fields or having problems saving emails events or other properties with the Rich Text Editor, you can disable AJAX within module configuration under the Module Configuration, General Settings section.

    * There are known issues with AJAX and the file upload/image upload fields. If you are using these fields you should disable AJAX for the form. This is disabled under module configuration, general settings.

    * There is a known bug with the Data Grid field type if you also enable the feature to display the label and the field in the same column (instead of left to right). If you have problems with the data grid field please disable the feature to display the label and the field in the same column. Our development team is reviewing this issue.

    * Some field types do not currently support the ‘Save for later’ and ‘Edit Results’ enhancements. These include the Gridview/DataGrid/File Upload/Image Upload field types.

    * Dynamic Forms will generate an ‘Error 500’ on servers running IIS7 with 64 bit operating systems whenever you click ‘Update Settings’. All settings appear to be saved and we are still researching why it generates this error. This should only occur when clicking Update Settings and the settings are saving properly.

    * Tokens that include the _Text property such as $(ComboBox_Text) or $(RadioButtonField_Text) do not currently work for PayPal integrations at this time. These variables are generated from the form itself at the time of submission and not saved directly to the database, and since PayPal integration works within a silent ‘live’ link between PayPal and the form it pulls the value from the database. We are researching ways to handle this in future versions. Additionally, a work around is to use a client side event to save the text property to a hidden field. Please refer to the product forums for examples and assistance to implement this work around.

    * If you are signed in as an admin / user with edit rights and have enabled the display after message, you might receive (in edit mode) several JavaScript pop up messages when you submit the form. These messages reference the Drag/Drop ability within Dynamic Forms and we are reviewing a fix (the same JavaScript functions are being called but since the form fields no longer exist its generating a pop up error). This message is only reflected when an admin submits the form in edit mode and uses the display after message, so end users should never see this message.

We are working to get these issues resolved as solutions become available.  We'll keep you posted on any new developments.  Thanks again!

Candace