Tuesday, September 5, 2017

Sitecore WFFM form reports are empty

On a Sitecore instance running version 8.1 and the web forms for marketers module, the form reports were coming up empty.

Sitecore WFFM form reports empty
Looking at the console on the form reports page (as shown above) there were three 500 errors returned for services used to build up data on the page. The error messages for these three services were as follows:
The parameters dictionary contains a null entry for parameter 'id' of non-nullable type 'System.Guid' for method 'System.Web.Mvc.ActionResult GetFormFieldsStatistics(System.Guid)' in 'Sitecore.WFFM.Services.Requests.Controllers.FormReportsController'. An optional parameter must be a reference type, a nullable type, or be declared as an optional parameter.
Parameter name: parameters

The parameters dictionary contains a null entry for parameter 'id' of non-nullable type 'System.Guid' for method 'System.Web.Mvc.ActionResult GetFormContactsPage(System.Guid, Sitecore.WFFM.Abstractions.Data.PageCriteria)' in 'Sitecore.WFFM.Services.Requests.Controllers.FormReportsController'. An optional parameter must be a reference type, a nullable type, or be declared as an optional parameter.
Parameter name: parameters

The parameters dictionary contains a null entry for parameter 'id' of non-nullable type 'System.Guid' for method 'System.Web.Mvc.ActionResult GetFormSummary(System.Guid)' in 'Sitecore.WFFM.Services.Requests.Controllers.FormReportsController'. An optional parameter must be a reference type, a nullable type, or be declared as an optional parameter.
Parameter name: parameters
The first step is to check that the settings items required for the WFFM report queries have been installed correctly. The item at the "/sitecore/system/Settings/Analytics/Report Queries/WFFM" path should have 4 child items.

Sitecore WFFM report queries settings
The next step is to ensure that the WFFM_Analytics.sql file was run on the SQL reporting database at the time of package installation. The following four databases are expected on the reporting/analytics database, if they are not present the SQL file needs to be run:

  1. Fact_FormEvents
  2. Fact_FormStatisticsByContact
  3. Fact_FormSummary
  4. FormFieldValues
Running this script removed the three service errors for me and the form reports started logging/showing data as expected. 

No comments:

Post a Comment