Exporting to an excel template

RE: Exporting to an excel template

Kavitha Thanikanti — Fri, 20 May 2022 07:46:07 GMT

Hii could you please tell me how to add filters to excel so that what ever we are selecting that has to be show in the excel data to dwl

RE: Exporting to an excel template

Mike Schmitt — Thu, 12 Mar 2020 13:05:47 GMT

[quote userid="26683" url="~/discussions/f/plug-ins/18439/exporting-to-an-excel-template/72600"]they deprecated most functions including the most important one, export CDT to excel[/quote]

For what it's worth, even with the latest version of Appian and the latest version of the plug-in, the CDT to Excel and SQL to Excel nodes are still available and working, just marked "deprecated". In my opinion these should be used with caution but can probably still be used when the use case requires, given that no functional alternative has been provided yet.

RE: Exporting to an excel template

Jose H. — Thu, 12 Mar 2020 13:03:52 GMT

, thanks for your response. I didn't realize that was not part of the plugin. Looking at the available options under the plugin it seems they deprecated most functions including the most important one, export CDT to excel which I used in the past and made sense given the higher flexibility.

I looked at your feature request post and knowing Appian, this might not be resolved any time soon, if at all.

RE: Exporting to an excel template

Mike Schmitt — Thu, 12 Mar 2020 11:52:04 GMT

a!exportDataStoreEntityToExcel() is not in Excel Tools (as in the plug-in), but instead it is an out-of-the-box feature added somewhat recently. For whatever reason, they decided to forego the ability to use an excel base template, like you could have done using the "Export CDT to Excel" smart service from the Excel Tools plug-in. In your code above I see you're using the "documentToUpdate", but as far as I've been able to tell, all this does is overwrite that existing document with the unformatted output of the Data Store Entity output. On that note, a word of caution: I expect your above code will probably overwrite the actual template file referenced by cons!EXT_EXCEL_EXPORT_TEMPLATE. This is the expected behavior of the documentToUpdate parameter, anyway - let me know if this has not been your experience.

In my opinion this is a big functional gap (see my previous feature request thread) and once again I'm disappointed that they're not addressing it in the next major release (as far as I can tell from the 20.1 webinar which took place yesterday). The official word from Appian on this has been that if you have a required use case for the Export DSE to Excel functionality to be updated, then you should open a support case with Appian so they can log it with their engineers.