HI All,
I am working on 19.3 and have a requirement where I need to filter data from from the view based on the condition that are provided by user and then have to export it to excel.
The total no of column are 59 hence single node of Write Datastore Entity to excel is getting failed.
I tried using the same smart node twice where first node have selection of first 50 fieldsand starting cell value as "A1" and 2nd node have selection for remaining fields and starting cell as "AY" i.e 51st column.
When I am debugging the process the document obtained has only last node column.
Is there anyway by which we can get all the 59 in columns in one sheet of the excel by using Write "Datastore Entity To Excel Smart Service"
Discussion posts and replies are publicly visible
I don't think thats posible. Entry in excel sheet will always get overriden with last node
any idea on custom cell position and custom cell value..?
Have you tried using the Export SQL to Excel Smart Service. Create a SQL View that populates the same data as the CDT and use this service to create the spreadsheet bypassing the CDT.
For what it's worth, last I heard Export SQL to Excel has been officially deprecated from the Excel Tools plug-in, and I expect that anyone who deploys the current version of the plug-in won't even be able to access it.
There was a similar post here within the past few weeks where another user was finding that subsequent writes overwrite any previous data in those same rows. I believe this is an error in the Export DSE to Excel smart service, and I recommended that user open a case with Appian Support (i'm not sure whether that's happened or not, though).
Hi Mike, It may have. We needed to use it a year ago because of limitations we ran into when exporting the DSE. Haven't looked at it since.
I also use it extensively (in a project that's been using it for years and we just can't ever upgrade the plugin version because of this) - when they originally rolled out the EDSEtE smart service it was promoted as a "replacement" for Export SQL to Excel (as well as Export CDT to Excel), but certain things, especially the inability to use an excel base template file, renders it useless to me.
HI Dave,
I have tried it but getting issue while creating the filter Dynamically i,e with Write to data store Entity we can write the filter logic which will only be applied when we pass some value to to filter the result set.
With Export SQl to Excel i m unable to use the filter dynamically as we have write the complete SQL query for it
This isn't too hard to get around. For SQL to excel, in the node itself just pass in a unique expression rule which generates your SQL code. The expression rule would also accept any parameters such as options and filters. There inside the expression rule itself, it's pretty easy to use the different passed-in options to generate slight variations of the same SQL code depending on what you need to do. This method is also really easy to test, since it just generates SELECT statements which you can just run directly in SQL to make sure they work.
Hi,
You can set your filters on the view easily enough. Pass the filter values into the node and use them in the SQL... That's way I had to implement it.