What is a dynamic form?

A dynamic form is essentially a form that allows insertion of text elements containing bindings.

From that binding with in the text element, you can now bring in dynamic content, which before was only possible from user profile selection.

With the support of dynamic forms you can now configure a form that enables conditional choices, meaning you can make a choice in a form and then have a dynamic text element inserted and display a new form based on the binding in the text element.

The form field from the text element is added below the form field that the text element was dependent upon, which means that based on previous choices you can have a new dropdown displayed upon document creation. 

Dynamic forms only work when text element binding is based on a dropdown in the document form.

Dynamic forms have previously been supported, but only if a text element was bound to a User profile form field. We now support dynamic forms if a text element is bound to a document form field. This feature allows template admins to create templates where the user can make selections and based on their selection, new questions (form fields) will appear, allowing the user to customize the document created to an even greater degree.

Supported scenarios

• A non-Dynamics (static) text element, bound to a drop down
• A Dynamics enabled text element with no form fields, bound to a drop down
• A Dynamics enabled text element with form fields, bound to a drop down
• A Dynamics enabled text element with form fields, bound to a drop down filtered based on another drop down

Pre requisite and limitations

• Doesn't require a new Dynamics version. 
• This feature is only supported for drop downs, and not e.g comboboxes or other form field types. The text element selection needs to be a dropdown but you can easily have fields within the text element that are linked to a textbox.
• Works with DCU and offline. However, to work with both Offline and DCU it requires VSTO version 5.7.5.1837.
• Not supported with nested text element. The form fields that show up, cannot include drop downs that triggers additional form fields to show up. This means we only support two levels of gating questions: The inital question, and the additional questions shown depending on the user's choice in the first question.
• It only works with Word processing templates. This is because it's a feature coupled to text element insertion, which is only available in word processing templates. This also means it's not available for text element templates, i.e. when you create a text element directly from the text element library.
• The form fields added dynamically will show up at the end of the form. We don't currently have any way for the template admin to specify where form fields will be inserted, and while it makes sense to insert the form fields directly after the drop down triggering them to appear, we currently don't support this.  
• Only support two levels of gating questions