## Activities: Dataform

mod_dataform
The Dataform module allows the course manager to design and construct an entry form from various input elements (text and rich text fields, urls, files, pictures, etc.) in a flexible layout. Users can then add information records to a collection, which can be viewed in various ways and searched for particular items.
706 sites
30 fans
Moodle 2.6

The dataform module is a major enhancement of the standard Database activity module and is meant to offer all the functionality offered by the Database module and much more in a more flexible way.

The module allows the course manager to design and construct an entry form from various input elements (text and rich text fields, urls, files, pictures, etc.) in a flexible layout. Users can then add information records to a collection, which can be viewed in various ways and searched for particular items.

The dataform features include (among other things):

• A multiple views system - allows the instructor to design several different views of the entries in a datform activity. Each view can show a designated subset of the entries in a designated layout.
• Enhanced template tags - A new template tags system allows for exposing many more bits of information and makes it easy to add designated patterns in new field and view types.
• Enhanced entry actions - Bulk edit, duplicate, delete, approve etc. Inline editing. Form editing options such as required fields (via Moodle forms).
• New packaging system - based on Moodle backup/restore and allows for packaing a dataform instance and restoring into an existing instance.
• Enhanced filtering system - allows the instructor to define different filters each of which can determine sort (including nested sort) and search options (various search criteria). Filters can be fixed to particular views or applied on the file from the activity main page (if included in the view template).

New view/field types include (among others):

• Tabular view - a view type which allows for displaying the entries in a table. The design of the entries table has been simplified to drawing the desired table with optional header row and an entry row in the moodle editor.
• Nanogong field - a field type for adding audio content to an entry via the nanogong applet.
• Calculated field - a field type which can display a result of a simple calculation on one or two number fields in the entry.

### Sets

This plugin is part of set Dataform.

### Awards

• Tue, 6 Dec 2016, 8:43 AM
Vernon, dataform 2.7 requires Moodle 2.7. This is set in the $plugin->requires, not the$plugin->version. Since then I also changed the \$plugin->version to reflect the corresponding branch. If you tried to install several times the version errors may be a caching issue which may be tricky to reset. The 2.6 and 2.7 branches are no longer supported. 2.8 is also not supported although there may be an opportunity in the next few weeks to release an updated (albeit not upgradable) version for 2.8. hth
• Mon, 12 Dec 2016, 10:10 PM
Hi Itamar

We're currently testing an upgrade from Moodle 2.5 to 3.1.
We're using a Moodle Partner company to do this for us.
There seems to be a problem with the Dataform that seems not to uninstall properly. Here's the error message they're giving me:
mod_dataform - [!!! required !!! due errors while upgrading either to 2.7 or 3.1 [see error notes below]

Error notes:

Is there a way to uninstall the old Dataform version and reinstall the 3.1 version ?

Thanks

Sébastien
• Mon, 12 Dec 2016, 10:24 PM
Hi Sebastien. The problem is that Dataform 2.5 or earlier doesn't upgrade to 2.6 or later. The 2.6 included significant changes and was in a sense a "new module". Unfortunately there is no simple way to migrate 2.5 or earlier activities to a recent version. If you have many such activities it might be worthwhile to consider writing a migration script. Otherwise migration would require export/import and some manual reconstruction of structure and data.
• Mon, 19 Dec 2016, 6:44 AM
Hi there,
Ive posted in the forums but have gotten no response, I'm getting errors when using the plugin:
"Warning: Parameter 1 to dataformfield_entryauthor_renderer::display_edit() expected to be a reference, value given in /var/www/html/Dev/mod/dataform/classes/pluginbase/entriesform.php on line 68"

"Warning: Parameter 1 to dataformfield_file_renderer::display_edit() expected to be a reference, value given in /var/www/html/Dev/mod/dataform/classes/pluginbase/entriesform.php on line 68"

Any idea what could be going on here?
Im thinking its a PHP7 compatibility issue but any help would be greatly appreciated.
Cheers
• Fri, 13 Jan 2017, 10:08 AM
Hi Itamar

I'm using the entry pattern EAU:edit in a view to display a selectable menu of enrolled users in order to let teachers input a student name.

The teachers have the role "non editing teacher".

We've just ugraded from 2.5 to 3.1.

Previously the EAU:edit pattern enabled this. Since the upgrade, non editing teachers can only see their name during entry. The dropdown menu with a list of all users enrolled in the course displays for other roles, such as editing teacher, but not for the non editing teacher role.

I'm sending you screenshots through e-mail for more clarity.

I don't want these teachers to be editing teachers so I tried to find the one permission that is blocking this action, but I couldn't find it. Do you now what permission should be changed ?

Cheers

Sébastien
• Tue, 31 Jan 2017, 2:27 AM
Hi,

I've just upgraded to 3.2 and the plugin check showed that I was missing the userinfo field.

How do I add this field?

Thanks,
Sharon
• Thu, 2 Feb 2017, 8:54 PM
Hello,
I used this plugin for moodle 2.8 and it worked really well.. Now i'm implementing the same for 3.2 but it does not seem to be working. I can create form and after selecting default view as grid or tabular while i try to add entry empty text boxes do not come. after clicking on add new entry only the lables come.. not the empty area where i can enter the details... Kindly help..
• Thu, 2 Feb 2017, 8:57 PM
Warning: Parameter 1 to dataformfield_text_renderer::display_edit() expected to be a reference, value given in /var/www/html/moodle/mod/dataform/classes/pluginbase/entriesform.php on line 68

Warning: Parameter 1 to dataformfield_number_renderer::display_edit() expected to be a reference, value given in /var/www/html/moodle/mod/dataform/classes/pluginbase/entriesform.php on line 68

this is the error i'm getting... while implementing it for Moodle 3.2... This plugin was of amazing help while i used it for previous versions of moodle
• Thu, 16 Feb 2017, 4:10 PM
Hello,

I have dataform running on a 3.1.4+ PHP version 5.6 without issues, but when I run the same present on a Moodle 3.1.4 with PHP version 7.0.8 I get this error:

Warning: Parameter 1 to dataformfield_number_renderer::display_edit() expected to be a reference, value given in /data/www/elan-learning.nl/public_html/mod/dataform/classes/pluginbase/entriesform.php on line 68

Warning: Parameter 1 to dataformfield_number_renderer::display_edit() expected to be a reference, value given in /data/www/elan-learning.nl/public_html/mod/dataform/classes/pluginbase/entriesform.php on line 68

Warning: Parameter 1 to dataformfield_text_renderer::display_edit() expected to be a reference, value given in /data/www/elan-learning.nl/public_html/mod/dataform/classes/pluginbase/entriesform.php on line 68

Warning: Parameter 1 to dataformfield_select_renderer::display_edit() expected to be a reference, value given in /data/www/elan-learning.nl/public_html/mod/dataform/classes/pluginbase/entriesform.php on line 68

Warning: Parameter 1 to dataformfield_select_renderer::display_edit() expected to be a reference, value given in /data/www/elan-learning.nl/public_html/mod/dataform/classes/pluginbase/entriesform.php on line 68

Warning: Parameter 1 to dataformfield_select_renderer::display_edit() expected to be a reference, value given in /data/www/elan-learning.nl/public_html/mod/dataform/classes/pluginbase/entriesform.php on line 68
• Thu, 16 Feb 2017, 4:19 PM
As an extra note I have the same issue that Alaukik reports: the error appears when I try to make an entry, I can see the header but not the entry boxes.
In the Moodle 3.1.4+ PHP 5.6 I don't have the error and can place the entries.
• Thu, 16 Feb 2017, 8:27 PM
Thank you @Gemma lesterhuis.. I tried what you said... "In the Moodle 3.1.4+ PHP 5.6 I don't have the error and can place the entries." and it actually worked like miracle...

Thank you ... i really needed it
• Sun, 19 Mar 2017, 9:50 PM
Hi

In previous versions (e.g. 2.5) the "more" entry pattern (the magnifier) would call for the default view. Now it displays the current view.

What it does in effect is simply showing you the same view, but only for the selected entry.

It seems to make less sense. If you want to see more, it means you want to display more fields than are displayed in the current view.

My understanding is that the default view is the one you use to create the entry, displaying all fields.

The other views are different ways to display a selection of these fields, according to various contexts, needs and uses.

Is there a way with the current version (3.1.0) to restore the default view as the view displayed by the EAC:more entry pattern?

Thanks,

Sébastien
• Sun, 19 Mar 2017, 10:15 PM
Try the pattern EAC:more:target-view-name. For example, if you have the views List and Single and you want to allow the user to open the entry in the Single view from the List view you can add to the entry template in the List view the pattern EAC:more:Single. hth
• Thu, 18 May 2017, 2:49 AM
Hi, Itamar. Just checking in on roadmap plans for 3.1 and 3.2 compatible versions for a client that wants to upgrade. I see that most are agreeing that the current version is working on 3.1, so that is my current testing target. Just wondering if you have something new on the horizon coming out soon. Thanks!
• Thu, 18 May 2017, 3:14 AM
Hi Lesli. Nothing would make me happier than releasing a 3.2 version. The main issue is that the behat tests need to be adjusted for the new theme in order to validate the release and I need to find time for that. I've started working on that and hoping to be able to complete it sooner than later.