Provides the following custom smart services and functions for handling data in Excel. An example usage application for Export SQL to Flat File is also included.
Smart Services included are:
Functions included are:
NOTE: When deploying this plug-in, please delete all old versions of the ExportableDataSubset CDT AND update your model to point to the new version {urn:com:appian:ps:excel:types}ExportableDataSubset
Share:
Hi Bhargav,
Is this plugin not compatible with 19.4 yet? I'm trying to use it in 19.4. When I executes the process, it completes successfully, but data doesn't seem to import into DB.
I tried both 'Import Excel to database' and 'Import CSV to database' with no success.
Not sure if anyone facing similar issues.
Hi,
Thanks for confirming - as far as I remember, I'd tried it both ways (i figured dictionary syntax wouldn't work but also didn't produce specific errors).
Also as a side note, Community doesn't seem to send any sort of notification of a reply here even though you had replied directly to me (this seems to hold true for any sort of comment activity within the App Market space).
Hi April. When I execute the excel import task in my work flow, it errors out with the above mentioned error. The error hints at the smart service not correctly reading the column names in the first row of the excel. Similar to trying to run this query on a DB: select "" from [table].
Hi johnh0011 - can you please provide some more context for when you're getting this error and what's not working?
Hi Vadivelan - this should work with any supported databases.
Is there an issue with the excel import smart service in 19.4? Was working fine in 18.2. I get the following error: ???ORA-01741: illegal zero-length identifier???
- Added LOAD CSV to DB Smart Service - fast CSV import for MySQL database that are not hosted on Appian Cloud
Sanchita GuptaDoes that mean Load CSV to DB Smart Service will work only for databases that are not hosted on Appian Cloud?
So the first issue here is the syntax for calling the function. You cannot use keyword syntax when calling a plugin, you must use position syntax: docs.appian.com/.../Expressions.html
An example syntax would be queryAppianLogs("select * from login-audit",null,{"String", "String", "String","String","String","String"},null,false) to fill out the inputs for sqlStatement, subFolder, columnTypes, timestampFormat, and hasHeader respectively.
Testing using this syntax produces more expected results however passing false for hasHeader seems to skip the first row of data in the file so we will look into fixing that. In the meantime, the Log Reader plugin can also pull csv data.
Can we update the ReadExcelFile function so we can pass paginationData? If I have large data sets in excel, I'd like to control how many rows I read at at time.
Hi Jesse Knight - you can request permission from the author to update the plug-in using the AppMarket Submissions site: https://forum.appian.com/suite/sites/appmarket-submissions/page/home
There appear to be two unused arguments for the Import Excel To CSV smart service. Drilling into the plugin, it appears that ExcelHelperUtils.java::convertExcelToCSV does not use numberOfColumnsToReadInRow or rowNumberToReadFrom . It appears that implementation of either would be straightforward, given that they modify iterator start or exit conditions. Would it be possible to get this fixed in the next version of the Excel Tools plugin? Is there a way I can contribute these changes?
Hi April,
Yeah, I posted in discussion excel-generation-with-base-template also requested feature update in feature-request-update-the-export-data-store-entity-to-excel-smart-service-to-accept-an-excel-base-template
Thanks for your reply.