Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

First 2 are for end-users mainly and second 2 are for further data processing, as it depends how the data for complex fields is exported. JSON and XML formats export internal representation of the data, that means you will see IDs for dropdowns, GUIDs for smart classifiers, page IDs for pages and blogposts, date and time fields exported as timestamps (epoch) and also IDs for database-backed fields

 


Let's consider an example. Here is a form with 3 fields

...

  • mytf - text fied
  • mydf - dropdown field (contains 3 choices)

    IDLABEL
    1one
    2two
    3three
  • mydate - is of type date

 


Export is enabled by default in the Admin UI for the form

...

We will add couple of records and will show how the exported result for each format look like

 


 Exported as CSV

Code Block
Id,Created By,Owned By,Created,Created,My text field,My Dropdown Field,My date field
f4ea4796-0dd2-455c-a1b4-926209260a02,sash,sash,1465197019719,2016-06-06 03:10,hello export,one,"Jun 04, 2016"
66cee179-2f33-4fd1-b8b8-bb889043e06f,sash,sash,1465197038331,2016-06-06 03:10,confiforms tutorial,three,"Jun 07, 2016"

...

Code Block
<?xml version="1.0" encoding="UTF-8"?>
<list>
   <entry>
      <id>f4ea4796-0dd2-455c-a1b4-926209260a02</id>
      <recordId>1</recordId>
      <ownedBy>sash</ownedBy>
      <createdBy>sash</createdBy>
      <created>1465197019719</created>
      <deleted>0</deleted>
      <fields class="fields">
         <mytf>hello export</mytf>
         <mydf>1</mydf>
         <mydate>1465012800000</mydate>
      </fields>
   </entry>
   <entry>
      <id>66cee179-2f33-4fd1-b8b8-bb889043e06f</id>
      <recordId>2</recordId>
      <ownedBy>sash</ownedBy>
      <createdBy>sash</createdBy>
      <created>1465197038331</created>
      <deleted>0</deleted>
      <fields class="fields">
         <mytf>confiforms tutorial</mytf>
         <mydf>3</mydf>
         <mydate>1465272000000</mydate>
      </fields>
   </entry>
</list>

 


In the examples above you can see the difference in how the data differs (for non-text fields, see "mydf" and "mydate" fields)

Info

Form Admin UI also provides a way to see the structure of the form dataset, providing RAW data format.

This is mainly used for troubleshooting and data recovery

...


What about flattened views?

...

Code Block
https://wiki.vertuna.com/ajax/confiforms/export.action?t=csv&pageId=8159450&fd=f:8159450&fields=&filter=

It expects:

Parameter nameValue
t

Could be:

  • csv
  • flatten.csv
  • xml
  • json
  • xls
  • text
  • flatten.xls
 


pageIdPage Id of the page where ConfiForms is configured
fd

form name and again page ID where form is defined (some backward compatibility parameter, but still is required). It sould be given in a format

formname:pageId

In the example above we have a form named "f" and it is located on the page with id "8159450"

fields

Field names to export. This is interesting, as you can limit the fields in your export and also use the techniques from Accessing field values and properties to customize the export.

For example:

to export just user-defined fields, without metadata fields

Code Block
https://wiki.vertuna.com/ajax/confiforms/export.action?t=csv&pageId=8159450&fd=f:8159450&fields=mytf,mydf,mydate,mymf&filter=

result:

Code Block
My text field,My Dropdown Field,My date field,My multi field
hello export,one,"Jun 04, 2016",select B
confiforms tutorial,three,"Jun 07,2016",select A select C

 


to export date field as timestamp in CSV format and dropdown field's ID (not label)

Code Block
https://wiki.vertuna.com/ajax/confiforms/export.action?t=csv&pageId=8159450&fd=f:8159450&fields=mydf.id,mydate.timestamp&filter=

result:

Code Block
mydf.id,mydate.timestamp 
1,146501
3,146527
Info

For fields, you can use Virtual functions and format or transform the values as needed!

filterSame as ConfiForms Filters. To limit the exported dataset

 

 

...