Filter Analysis Data

Should be possible with views. For small datasets, try the views pivot table module. The views crosstab module is faster on large datasets but only works on simple sql. Use raw data fields.

My thoughts are that this is going in the opposite direction of where I see webform going. I have eliminated all the hard-coded tables other than analysis by creating views and enhancing the views integration to support that. Analysis is much harder, but eventually I'd like to see views handle it.

If one had substantial development time or money, I'd like to see the techniques in Views Crosstab rolled into a webform-specific handler(s) and plug-in(s). These would adapt to the components in the webform (like the current results field which expands to display all components as additional fields). Challenging, but the right direction, I think.

I think then that each component would have view which would analyze the data, each of which could be overridden on a component type or webform node + component id way.

I've marked this as postponed because it will take a patch from a contributor or some serious sponsorship to achieve it.

Closing for lack of activity. Please feel free to re-open if there is progress toward using Views for analysis.

I require this functionality as well. Looking back through the closed issues for this module it seems many others have requested this in the past.

I was considering writing a module to expose a filter on the hard coded Analysis page but it sounds like you are opposed to adding any new features to it and want it removed.

Can you please clarify?

I can't imagine it would be very difficult to add a filter by date or filter by submission number to the already hard coded Analysis page but doing a complete rewrite of it just to add that functionality seems way too difficult for someone without a serious amount of time.

If each person writes his/her own filter on the analysis, it helps that one person. If someone takes on the task of using Views for the analysis, then it enables every site builder to be able to customize the analysis as they desire. I've already done this for the submission tab, table tab, and the administrative list of webforms.

There is a Views Crosstab module which attempts (not super successfully) to add crosstabs (which is what the analysis is) to any view. I'm pretty sure that if the problem space is reduced to the webform_submissions and webform_submissions_data tables, that it should be possible to do this. Someone with the skills or funding needs to step up and make this happen, though.

Make sense?

Re-opening this. I'm thinking that one could write a view which simply limits the submissions to the set of submissions desired.

function webform_results_analysis contains a parameter for an array of sid's, but it isn't currently used by webform. This array is passed to each component's analysis function.

It would be pretty easy to use a view to generate this list of sids, and display the view's exposed filter. The problem, however is that an array of sid's will become inefficient at about 10,000 submissions, and probably not viable above 100,000 (for memory alone, if not time). In my testing, I found that IN has O(n^2) performance.

So what I think we want to do is either join the view's query or extract the filters out of a view (which might be tricky if they are on other tables, such as user or webfrom_submissions_data.

Here's a patch for testing. I have not yet tried the analysis filtering on every component. Non-core components will need updating. Clear the cache after patching so the view will be recognized.

You will find a new view (webform_analysis, human name Webform Analysis). You can clone this view. Append _NID or _CONTENTTYPE to limit the view to a particular node or content type). For example, to customize the analysis of node 12, name the view webform_analysis_12.

Add whatever exposed filters you want to the view. Be SURE the view doesn't duplicate any data. It should display one sids. You can add relationships to filter on data in the webform. You can filter by user directly.

Let me know how it works for you. Getting this to work was quite a bit harder than you'd think. :)

Updated patch. I missed adding the join to number components and I improved some comments.

Committed to 7.x-4.x and 8.x.

Note: Clear the cache to cause the view to be recognized.