simpleContact Support Forums

1. 

   danielnicollet
   Member

   Hi,
   Unlike the lite version, the form messages are stored in a table (scpro_form_post_data) that doesn't allow the same easy CSV export and use of submissions. Instead of having the form fields as column headers (like sc_messages in lite version), they are row headers and submissions are appended one after another in rows, in two columns.... It doesn't prevent CSV export of couse but try using this for a count of submissions, or a regular table view of your submissions???

   Based on the lite version there should be a table that lays out submissions one row at a time with field lables as column headers... It is misleading to have the lite version with a more advanced feature that doesn't exist in pro.

   What do you propose as a way to fix this? SimpleContact is not very wide in scope, if its data can't be easily ported to something else, it's not very useful at all, is it?

   Rgds
   Dan

   Posted 1 year ago #
2. 

   Alex
   Administrator

   This is not a fault. It is a carefully considered database design choice. The number #1 feature request for simpleContact Pro is custom fields. As you can see, although 'Pro is superficially similar to 'Lite it is a different mechanism (and certainly not less advanced). In building it I had several considerations in mind:

   * The nature of a field is generic. A field is a "Fax number" or "Favourite colour" field because that is what it has been labelled.

   * The user should be able to add a form object and define its meaning.

   * The application should not impose a limit on the number of fields on the form.

   * The user should be able to edit and delete fields without losing data in messages already received.

   * The user should be able to re-order the fields.

   * I should be able to implement new object types (e.g. a message subject field) without having to modify the fundamental database structure.

   * As far as possible, the increased complexity of the application should not be passed on to the user in a more difficult interface.

   This requires a relational database structure where data is stored vertically (in records) rather than horizontally (in predefined field columns).

   Obviously the database structure is not subject to change but I have been considering a CSV export for the inbox that may provide you a solution. I did not think it important enough for the initial release, but I am monitoring demand.

   Posted 1 year ago #
3. 

   danielnicollet
   Member

   Thanks Alex. That makes sense.
   Apart from the fact that relational data models are not always made of vertical tables, and that in nature custom fields can be appended horizontally also, I am just fine if you end up adding a CSV export. That would be great from my POV (if it includes the custom fields of course). This said, if you are going to have to re-combine vertical records into tables listings with column headers for CSV, why not just allowing it in your inbox view also. It has just 3 fields right now.
   Thanks again for your responiveness.
   Dan

   Posted 1 year ago #
4. 

   Alex
   Administrator

   Agreed, but in my experience there is rarely *One True Way* that all developers agree on :)

   I chose to store data vertically rather than deal with manipulating table columns. To my mind, it seems neater the way it is...

   I have discussed inbox CSV export previously with another user. It makes sense because it would not only improve data portability but lend itself better to email list segmentation and mail merge processes.

   Regarding the inbox table view, I'm inclined to keep it simple but I'll reevaluate as time goes on.

   Point of clarification for readers

   This forum thread discusses CSV export of messages from the inbox, which is not implemented in simpleContact Pro 2.0. CSV export of the mailing list is included and is easily done from the admin.

   Posted 1 year ago #
5. 

   cmilitzer
   Member

   Hi,

   I hope that you are still seriously considering a way to export the inbox to csv. I would greatly appreciate that feature!

   Could a csv file have data written to it when the form is first submitted? Then each item from the form could be placed into a separate column? As long as the form keeps the same structure, then the csv file would have a consistent number of columns. Perhaps something similar to this article: http://hubpages.com/hub/PHP-form-inserts-data-into-CSV-file

   Cory

   Posted 1 year ago #
6. 

   Alex
   Administrator

   simpleContact Pro 2.01 will include a CSV export for the inbox. It will be released after a dedicated website for the application goes live.

   In the meantime, you may contact me to request a "beta" copy of the CSV export script.

   Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.