Troubleshooting issues with form reports in the WFFM module


Description

This article describes step-by-step scenarios for troubleshooting the most frequent issues with form reports in the Web Forms for Marketers module.

Scenario 1 - Data Is Not Collected To The Formdata Collection

Symptoms

Data does not appear in the FormData collection of the Analytics database (xDB) after submitting a form. As a consequence, field values are missing in the exported Excel or XML file.

Please note that data does not appear in the database collection until the session timeout is reached. It is specified as 20 minutes by default in the web.config file.

You can change the "timeout" attribute value, for example, to "1" in order to decrease the session timeout:

<sessionState mode="InProc" cookieless="false" timeout="1" sessionIDManagerType="Sitecore.FXM.SessionManagement.ConditionalSessionIdManager">

Troubleshooting steps

  1. Refer to the troubleshooting steps described in the following article: KB0977445
    (Scenario 1 -  Data is not collected to the Collection database)
  2. Try to use some clean xDB databases by changing the related connection strings, for example:
<add name="analytics" connectionString="mongodb://localhost/analytics_temporary"/>
<add name="tracking.live" connectionString="mongodb://localhost/tracking_live_temporary"/>
<add name="tracking.history" connectionString="mongodb://localhost/tracking_history_temporary"/>
<add name="tracking.contact" connectionString="mongodb://localhost/tracking_contact_temporary"/>

Scenario 2 -  Data Is Not Aggregated To The Reporting Database

Symptoms

  1. Data does not aggregate to the FormFieldValues, Fact_FormEvents, Fact_FormStatisticsByContact, Fact_FormSummary tables of the Reporting database (SQL). As a consequence, form details are missing in the Form Reports application.
  2. Data in the exported Excel or XML file may differ from the data displayed in the Form Reports application.

Troubleshooting steps

  1. Ensure that you have run the [site root]\Website\Data\WFFM_Analytics.sql script on the Reporting database of your current instance.
  2. Rebuild the Reporting database as described in the following documentation:
  3. Check the description and solution from the following article (valid for WFFM 8.0 only):
    KB0282795