I spent more than 15 minutes on Phabricator to look for the Export to spreadsheet feature without success. I have seen there that this feature exist. My goal is to migrate away from Phabricator.
You need to implement PHPExcel and add it into your php config include_path.
Then you can use the Export To Excel on each Maniphest page with the built ind queries and your custom queries.
If you need a custom format you need to customize the existing ones. Therefore see files in ./t/phabricator/src/applications/maniphest/export/
Related
I am looking to build a simple, one page app that does the following (the users who would be utilizing this tool would need this to involve zero code, and as little "clicks" as possible):
a worker who has taken samples could import data (in an excel format) to a database, ideally a SQL server.
after import is complete, the user could use drop downs and filters to set parameters for what report they want to see.
with the "export data button," the user could then export a report to an excel file for their download and use.
I am not very familiar with PowerApps - by the looks of it, this seems like something that can be done, but I don't want to waste time if this is not worth the effort and won't have the functionality I am looking for. If this IS impossible, any suggestions on where I could build out something like this?
I was wondering if there is any way to export data from the Parse.com database (based on conditions) to a PDF format. There does not seem to be any built-in functionality for this but I may be missing something.
The purpose of this is to create a monthly report of new entries into the database.
The only solution I can find is to pull out ParseObjects using a query against a condition (in this case, creation date) and then having to manually extract fields and construct a PDF document using a third-party library.
Although I cannot find any solutions, I feel that this sort of functionality would be commonly required and perhaps I am missing something.
Any help would be appreciated! Thank you.
There is no built in function, you could try to use a JavaScript library in a Cloud Code Background Job to write the file and schedule the job to run once a month, or like you already said, query the data using the API and write the file on your own server/client. That's pretty much your only option at the moment.
I want to export my GridPanel to Excel. I searched too many times but I couldn't find any acceptable solution.
Can you help me about this problem?
P.S.: I use ExtJS 3.2 and 3.3.1
There isn't any good solution to generate xls/xlsx in javascript.
Your best catch is to do it server-side.
Send ajax request to http://your-website.com/generate_xls containing all the data, and return xls headers and then body.
Here is a good PHP library, in case that you are using PHP: http://phpexcel.codeplex.com/
This is a server side job. Here is what I use for generating tabular reports which are based on Grid data: http://xmlgraphics.apache.org/fop/
Also, you can generate a very nice, fully functional Excel spreadsheet from tabular data: http://msdn2.microsoft.com/en-us/lib...ffice.10).aspx
.With the launch of ExtJS 5, it's probably better to start porting your application to a newer version of ExtJS, at least 4.
We have created a front-end XLS(X) and CSV import and export tool that you can use in ExtJS 4 applications with a few lines of code. The user just drags the file on the grid and done. We just launched it, here is a description: http://2gears.com/2014/08/ext-js-excel-import-export-easy/
As said, the import and export is done ENTIRELY client side, so in applications with many concurrent users, this relieves the server from excessive load. In the next weeks also an import wizard will be added, that guides less capable users in importing files.
Hope it helps
There's the need to send data to an external interface - a financial statutory report to be sent periodically for some country's government which expects data as text files with no separator between fields: fixed width, left-padded with zeros or blank spaces (depending on data type) to fill the space.
So we created an RDL with the required fields and were looking at adding an export option in for this.
Can an export option be created to export in this format?
We'd like to avoid having to CAST all appropriate fields to NVARCHAR in the stored procedure that feeds the report, left-pad them there and finally concatenate everything - unless that's the only option to accomplish it.
Also, we definitely don't want to code an ad-hoc export method in .NET, there won't be much reports with this exporting option so it's not worth it. Besides it's not so easy to convince the server team to deploy DLLs to servers - if there's something already coded, open source or shareware, we could have a look onto it though wouldn't be the preferred solution.
Previously we had been able to configure the XML configuration file for Reporting Services 2008 to add a new export option for export to Text with fields separated by pipes, so were thinking to try this first. Unfortunately discovered if you use the Text or CSV export motors but specify no separator, comma is used by default.
Any ideas?
In my opinion, Reporting Services isn't the right tool for this job. You're trying to bend a reporting tool into a data migration tool. While on the surface I guess it looks similar - outputing formatted data - the structure of the fixed length text file isn't really what Reporting Services is good at producing out of the box. We do a similar fixed length export using a scheduled SQL Server Agent job. You could also write a console app and run it manually or use Windows Scheduled Tasks to run it.
If you're determined to use Reporting Services for some functionality reason (for example, the export has to use the same parameters to filter the data as the report that is being viewed) then I'd simply create a second report based on the first with no header or footer, just a detail section with a table containing one wide field with an expression in it that creates the formatted text you need for your export. Put a link in the header of the main report called "Create export file" that links to this new report and passes the parameters across then export it to some non-paginating format like CSV.
Otherwise, you're looking at creating a custom renderer which you don't want to do and I agree is overkill for this.
I ran bulkloader with parameters to export my bigtable to a csv file, and it spent a lot of time downloading the table (it's large). It failed to export do to a problem with one of the lambda expressions in the Exporter class. I fixed that, can I run bulkloader.py again without having to redownload all of the data from GAE? I'd like to point it back at the .sql file it downloads and just tell it to export again to CSV.
No. If you use the same progress database, it may pick up from where it left off, though.