Grid export to CSV and excel questions

Suite and Optimus Suite 7
#1

Hi I have some questions about exporting grid into excel or csv

  1. Exporting to csv
    All my application work in UTF-8
    All accents are showing fine in the dhtmlx grid.
    However, when i export it with grid.export.csv , i can open it in excel but accents are wrong because Excel side is ANSI.

i don’t have the option to convert UTF-8 to Ansi

Is there a way to do it ?

  1. Exporting to excel
    Can you confirm that to export to excel :
  • I need the PRO version of DHTMLX Suite
  • I need to install an export module on a server (an docker image) which must be purchased separetely
    (there is no public export module to test it ?)

in this case :

  • will we have the same accents issue in xlsx than for csv ?
  • is the export module included in dhtmlx PRO evaluation ? (so we can test it before buying it)
  1. Exporting to excel or csv - other (minor) question

Is it possible to add header data to csv and xlxs export ? (by example all the filtering value applied to a grid)
or the only way is to add rows in grid, export it, and delete rows.
(note that i am manipulating 50000 rows grid)

Best regards

#2

Unfortunately, there is no possibility to configure the format of the exported csv data.

You are able to use the export to excel functionality in non-PRO version of the grid. PRO version is required only if you need to launch the export service locally on your backend.
You may test the export functionality in your local app using the GPL sources of the dtmlxSuite, or you can test right in the online snippet tool:
https://snippet.dhtmlx.com/58oqij47

Unfortunately, it is not available to format the exporting data any way. THe only solution, as you’ve mentioned, is to modify the data in your grid, export it, change it back again.

#3

Hi sematik,

  1. ok, perhaps a future evolution ?

  2. in fact if i use the following url in snippet
    url: “//export.dhtmlx.com/excel”
    that don’t work
    (it’s why i thought i can’t test it outside snippet)
    but if i put “http://export.dhtmlx.com/excel”
    that’s work (perhaps you could modify snippet, this may help other)
    so it’s working.

Note that i don’t have issue with accents in excel ! so it’s different from csv export

So the reason to use the docker image is for security & performance & availability ?
(are we allowed to use it with PRO version in PRODUCTION ?)

Note that i have an issue with footer, (i will create another ticket for that)

  1. OK

Thx, best regards

#4

Unfortunately in the near future we’re not planning to add the possibility to configure the encoding type of the exported csv, as the UTF-8 pretty common solution.

  1. in fact if i use the following url in snippet
    url: “//export.dhtmlx.com/excel”
    that don’t work
    (it’s why i thought i can’t test it outside snippet)
    but if i put “http://export.dhtmlx.com/excel”
    that’s work (perhaps you could modify snippet, this may help other)
    so it’s working.

Pretty strange, as the “https://export.dhtmlx.com/excel” should be used, not "http://export.dhtmlx.com/excel”. We’ve updated the snippet, so it should work well now. Please, check:
https://snippet.dhtmlx.com/58oqij47

Note that i don’t have issue with accents in excel ! so it’s different from csv export

Could you please, provide a complete demo, where the problem could be reconstructerd, as locally your scenario seem to work well for me:
https://snippet.dhtmlx.com/4uyctw1x

So the reason to use the docker image is for security & performance & availability ?
(are we allowed to use it with PRO version in PRODUCTION ?)

Yes, that’s right.

#5

Hi sematik,

  1. Ok that work with https://export.dhtmlx.com/excel

  2. For the csv export, the downloaded file is correct in UTF-8

The file is naturally opened by Excel in ANSI. so showing accents error

If i download the file, open excel and then import the downlloaded csv, I can choose UTf-8 and it’s fine, no accents isssue

I search a solution for avoiding data manipulation from users :

  • either exporting csv in ANSI : not allowed by dhtmlx
  • either using excel export (without docker) : security constraints
  • either using excel export (docker) : need internal team acceptance (will open another topic for that)
  • either finding a way to naturally open utf-8 csv in excel : i will search that solution

Thx for all your responses (support team is top :wink: )

best regards