How to Export data from Editable grid {excel}

The editable grid has no such OOTB functionality.

Is there any other work around to do it. I have a requirement while clicking on the button it should download an excel file to the local system with the editable grid data.

Well, the typical more or less ugly Excel export things. A simple one might be to create a CSV file instead of an Excel.

But how to achieve it with editable grid.

hi aradhana ganabady  may I know your complete use case, please?

I want to have button above the editable grid while clicking on the editable grid I want a excel file to be downloaded to my local system with the editable grid data.

OK, I think we need a bit more details about your specific use case.

- Where is the data coming from?

- Is that data stored in DB and just displayed in that grid?

- Is the data only entered, but not stored?

Editable Grid

1 : Take comes from no where
2: Data will be store in Record Type.
3: Data is only entered and at the time frame its store in rule input.

OK. So you could submit, store the data, create the file, and return to the same interface showing the link to download the file.

The "official" way of handling this would be to write that data to a data store or record.  Then you could do various things, including having your button launch a Start Process (function) calling a process model that invokes an Export DSE to Excel node, generates an Excel, then pass that document ID back to the interface to show in a Download link.  This requires 2 clicks (not just 1) and there is no current good work-around.

Dose DSE to Excel accept record type as input because we don't use Data store over here we are completely in Record type.

As far as I know you'd have to use a workaround to make this work - like creating a DSE just for the record type in question (though that's a lot of work). 

Alternatively, I actually prefer the smart services still found in the Excel Tools plug-in, such as "CDT to Excel", which is deprecated but still works fine as of my last check.  With CDT to Excel, you would merely query your record type data, and use an expression rule to cast the columns of data you want into a "generic" CDT you create (you'd just create a generic CDT not linked to any table, with X number of plaintext columns), and use that within the CDT to Excel smart service node in your process. 

It takes a little bit of setup but is very easy to use, and as a bonus, you can use a pre-formatted template Excel document (with pre-sized columns and formatted column headers with pre-enabled filtering, if you like).

As far as I know you'd have to use a workaround to make this work - like creating a DSE just for the record type in question (though that's a lot of work). 

Alternatively, I actually prefer the smart services still found in the Excel Tools plug-in, such as "CDT to Excel", which is deprecated but still works fine as of my last check.  With CDT to Excel, you would merely query your record type data, and use an expression rule to cast the columns of data you want into a "generic" CDT you create (you'd just create a generic CDT not linked to any table, with X number of plaintext columns), and use that within the CDT to Excel smart service node in your process. 

It takes a little bit of setup but is very easy to use, and as a bonus, you can use a pre-formatted template Excel document (with pre-sized columns and formatted column headers with pre-enabled filtering, if you like).

I also continue to use the deprecated "Export CDT to Excel" service, as we have not seen any replacement function that allows the use of a base template.  No issues with this service in my 24.4 environment. 

can you let me know what file need to be uploaded here Excel_base_template - can you share any sample file.

For the base template you can simply construct a blank Excel file with your columns pre-configured (and pre-named) with customized widths, formatting (i.e. make the column names bold, add background color if you want, etc), and pre-enable filtering on one, many or all columns if you want the generated file to automatically have it available.  Then you configure the smart service to start its output in the second row. 

You can't do much pre-formatting of the cells that will actually contain data, as everything in the data cells gets overwritten; but it's nice to have a friendly format instantly in your generated excel document.  Hence why I've been so insistent that Appian eventually fix the Export DSE to Excel smart service (though at this point I doubt it'll ever happen).