pepperstreet VIP
Total posts: 3,834
22 Aug 2013 08:07

Since import feature is already there... is it possible to get an export formatter for .CSV ? A very common format and basic feature, that shouldn't be missing, IMHO.

Thanks in advance.


EDIT - 14th April 2014

Further ideas and feature requests

  • Do not open in browser window
    Force a "download" or "save file as..."? Currently, the formatted content is displayed in the browser window. Confusing for some DAU's. As far as I know, other form-builder extensions like "Fabrik" or "BreezingForms" send the file to the browser download window. I think the most wanted behavior for a CSV file.

  • Limit field output
    include or exclude fields. So, one can focus on particular and the most important fields. i.e. exclude secondary infos, internals and statistics like hits, catIDs, access etc.

Last Modified: 30 Mar 2016

Tags Cobalt 9


Sergey
Total posts: 13,748
22 Aug 2013 09:13

yes. I agree. We will add it.


Sergey
Total posts: 13,748
02 Dec 2013 00:34

Кнопки нет. Это форматтеры. Что бы сделать экспорт надо просто активировать плагин форматера и добавить к урл

&formatter=json

или любой другой который есть.


pepperstreet VIP
Total posts: 3,834
02 Dec 2013 05:49

yes. I agree. We will add it.

Any news about CSV formatter and security/restriction question that has been raised by "Sackgesicht"?


pepperstreet VIP
Total posts: 3,834
28 Jan 2014 19:35

Bumping my own topic for notification. Any news?


pepperstreet VIP
Total posts: 3,834
14 Apr 2014 16:11

pepperstreet Any news about CSV formatter and security/restriction question that has been raised by "Sackgesicht"?

Plugin parameter "Access" restricts execution of formatter/URL. :)


pepperstreet VIP
Total posts: 3,834
14 Apr 2014 22:48

pepperstreet - Do not open in browser window - Limit field output

Added ideas to initial post.


pepperstreet VIP
Total posts: 3,834
15 Apr 2014 18:27

pepperstreet Further ideas and feature requests

Topic status was changed to "solved"?


Sackgesicht VIP
Total posts: 1,636
15 Apr 2014 20:02

Actually a CSV exporter should be part of every list template. An optional button to export all the list result records with the respective displayed fields


Sergey
Total posts: 13,748
16 Apr 2014 06:15

pepperstreet Topic status was changed to "solved"?

Yes, because in generald CSV exporter is implemented.

Sackgesicht Actually a CSV exporter should be part of every list template. An optional button to export all the list result records with the respective displayed fields

You can apply CSV to any template already. What do you mean?


Sackgesicht VIP
Total posts: 1,636
16 Apr 2014 06:42

Sergey What do you mean?

If i apply a filter/search to a list, i would like to export only the result (listed articles) with only the fields of this list. Therefore an optional button, exporting only the article list would be a good addition to every list template.

Example: A list of cars, but i only want to export Volvo.


Sergey
Total posts: 13,748
16 Apr 2014 06:50

I think formatter=csv parameter is only view change. It means that it list the same article that would be returned in normal view. I mean if you apply filter and then add formatter=csv you will get filtered list there. Of course in custom template you can create a special button for that.


pepperstreet VIP
Total posts: 3,834
16 Apr 2014 15:44

Sergey

pepperstreet Topic status was changed to "solved"?

Yes, because in generald CSV exporter is implemented.

;-) yes, i know. But i did't want to add a topic for the other (possible) features. Should I change the topic title then? And re-open it?


Sackgesicht VIP
Total posts: 1,636
18 Apr 2014 03:37

Sergey I think formatter=csv parameter is only view change. It means that it list the same article that would be returned in normal view.

One issue here is the pagination. It will only return the number of articles on the screen. Pagination allows only up to 100 records. Another issue is security. Anyone can export all intro fields (plus additional info like hits, rating etc) of ALL sections by just adding "&formatter=csv" to the URL (provided the plugin is activated).
A list of fields should be considered per exportable section to allow the inclusion of full view fields as well. I would suggest to add a parameter "Allow Export" under "General properties" of field parameters.

Beside this, the export is not working properly for some field types. Most target systems for import (like Excel) can not recognize the cobalt csv output. Output should be generated based on CSV specifications. I would recommend to follow the very simple rules of RFC 4180 for highest level of compatibility.


Sergey
Total posts: 13,748
18 Apr 2014 04:25

Sackgesicht A list of fields should be considered per exportable section to allow the inclusion of full view fields as well. I would suggest to add a parameter "Allow Export" under "General properties" of field parameters.

Or sections list parameter in plugin.

Sackgesicht Beside this, the export is not working properly for some field types

Thank you for RFC link. I have added changes and tested. It opens well in MAC version of Excel. And i update plugin.


Sackgesicht VIP
Total posts: 1,636
18 Apr 2014 05:32

Sergey It opens well in MAC version of Excel

I had problems with the old CSV plugin version ... Especially the gallery field (several pictures), upload field with several files ..

I would suggest to export the multi-level-field optional as only the field value, not the additional ids.

Example : HUGHES 369 HS -- not [{"427":"HUGHES","428":"369","429":"HS"}]"

A Radio button field should just contain the value (or escaped with ") not like "["F79GA"]"


Sackgesicht VIP
Total posts: 1,636
18 Apr 2014 05:39

Sergey Or sections list parameter in plugin.

With a section parameter in plugin it will still be the same regarding the fields (as of now it exports the intro fields plus additional core fields)., but with a field parameter we can easily define it when we add fields , or even just mark them in the field overview with all the checkboxes (intro, full view, searchable in compare view, etc) and it can also apply to all formatter plugins ...


Sergey
Total posts: 13,748
18 Apr 2014 05:51

I use JSON syntax for easie to use. When you create import script you can json_decode it.

I have added another parameter to insert fields values as string or JSON. And also string glue parameter for stringified values. And updated plugin.


Sackgesicht VIP
Total posts: 1,636
18 Apr 2014 06:15

Getting better ... ;-)

With a multilevel field, we would need control over the separator. Now it is the ",", but there are cases where we dont want it.

Example: Car --> Porsche 944 S2 -- and not Porsche, 944, S2

Another field to consider a different (optional) content, is the child field. Instead of the record ID, the title would be helpful here. I believe that most of the time, the exported data will be used in another application like Excel to better organize and present the data.

Field relations would not be helpful in this case.

Sergey When you create import script you can json_decode it.

the export should be as "flat" as possible .. no need to consider json_decode on it. In your import, you also dont expect json_decoded csv files, right?

Anyway, there is a JSON formatter as well... ,-)


Sergey
Total posts: 13,748
18 Apr 2014 09:41

Sackgesicht With a multilevel field, we would need control over the separator. Now it is the ",", but there are cases where we dont want it.

You mean difefrent glue for just this field?


Sackgesicht VIP
Total posts: 1,636
18 Apr 2014 10:46

MultiLevel Field I believe it should be exported the same way as it is displayed. The most logical approach would be to follow the field settings under "General Parameters"-> "Level Separator"

Powered by Cobalt