Messages

1

Suggest new features / Export to XLSX

« on: July 12, 2017, 09:19:27 pm »

The Excel file that is exported from the grid will open in Excel 2010.
It will not open with some 3rd party tools (such as ClosedXML).
It will not open when connecting to it VIA OleDB (using the Microsoft.ACE.OLEDB.12.0 provider - it errors saying "External table is not in the expected format").
I can open it/read it with the OpenXml API.
If I run it through the OpenXMLSdk v2.5 tool and use the validation function it says it is valid.
If I open the document in Excel and do a "save as", (no other changes)... then the new version of the file will open in ClosedXML and through the OleDB provider.
Using the OpenXMLSdk v2.5 tool to compare the two versions of the file (original compared the the "save as" version), the version generated by the grid is structurally different than the version created by Excel (file locations, number of files, shared strings, etc).

Is there a way to get more compliant version? Or are there plans to make the export more closely resemble a file generated by Excel so that it will play nice with the rest of the Excel eco-system?

Thanks

-Cam

2

Help for ParamQuery Pro / Re: exportData and Hidden Columns

« on: July 12, 2017, 08:13:20 pm »

Thanks.... I will try toggling that flag.
I have been trying to read the Excel file with ClosedXML but it can't read the file at all. I will have to try another library.

Is there a way to send a different format sent to the server than what is sent back to the client?

3

Help for ParamQuery Pro / exportData and Hidden Columns

« on: July 12, 2017, 12:55:53 am »

Hi there,

I am attempting to export data from the grid. I need to do a pile of queries and what not before the export, since they client wants the view on the screen and the export to be dramatically different. We want the same records, just way more columns, and child records, and, and, and.... So I added a url to the exportData function and I have it posting to the server. I need the data from the grid to know which rows of data to include in the new export. To this end I have added a hidden column to the grid and it contains the ID I need for the server side processing.

My Id is never sent in the export to the server. The mark up looks like:
              {
                  title: "MyId", width: 50, dataType: "integer", dataIndx: "MyId",
                  hidden: true, exportRender: true, copy: true
              },
I have set all of my other columns to be "exportRender: false, copy: false" and they are not included (as expected in the export). The server side method is currently getting a blank spreadsheet. I have tried setting the "render" argument of the exportData to true and false but it doesn't seem to have an impact on this. How do I get a hidden column to be included in the export?

The pq_data argument contains a spreadsheet or a CSV or an HTML file.... I want a format that is easy to chew on server side so that I can build out my new export, so I set it to CSV, but as soon as I set the format, then that is what the client writes the file as - no matter what I set the return content type and filename to. I want CSV sent to the server and XLSX sent to the client. The exportData function doesn't seem to allow different data formats to be sent than received. Is there away around this?

Thanks

-Cam