Using eForm Export to SQL is pretty straight forward. Once you are done installing, simply create a new form and edit an existing one. All export related settings are there inside the form builder.
As of version 1.0.0 you can not change the table name. We have made the system in this way to prevent accidental data overriding. But there are other options which you can change.
m0
: MCQ 0f10
:Freetype 10o12
: Other 12.m0,f10,o12
.30
, then exports from last 30 days would be saved. When new exports are made, only then expired/older exports would be deleted. If you want the system to force check, then please perform Check Missing Submission operation.::
/
~
That’s all about activation. In the next tutorial learn about some basic and advanced SQL operations you can perform from inside the system.
While most of the process is automatic with FSQM Export to SQL addon, yet some de-synchronization may occur between export table and FSQM table. This may be due to the following reasons:
To overcome such abnormality, we have provided an easy to use tool which would check for data consistency automatically and would import or delete records if needed.
Our system has an built in tool using which you can browse the export table directly and perform some SQL operations. To do so, please follow the procedure below:
Do note that, currently the system would not delete records from the export table even if it is deleted from FSQM table. If you want to, then you’d need to manually delete them.
eForm Export to SQL has a built-in tool to export records to a XLSX spreadsheet file. Doing so is easy and requires just a few clicks.
max_execution_time
directive.Starting version 1.2.0, Easy SQL provides a way to have revision control for user driven submission edits. To enable, simply follow the steps.
Now when user edits and updates a form the previous entry will be kept in the database.
You can use the admin backend to view the revisions side-by-side.
You can also get the revisions in the downloadable XLSX file.