Hi,
I have a read-only grid with a few columns, but there are quite a number of other columns from the other tables which need to be populated in excel.
I have a Data base view where I have joined all the required tables to get the data.
Can someone suggest the best way I can use the SQLServer view to get the data into excel?
Thanks in advance
Discussion posts and replies are publicly visible
You can have "Export to excel" link , clicking on the link , the excel report can be generated.You can use this smart service to export the data to excel.Export Data Store Entity to Excel Smart Service - Appian 22.1
Thanks for your response.
When I have gone through the provided help link, I didn't find a way to call a database view in that.
Can you throw some light on how to call a database view.
Thanks
Create CDT based on the view and map the entity in datastore.Use the entity in the Export to excel smart service and set the other info in the smart service. On Data->Output tab, save the new document AC to process variable.
Thanks for sharing more details.
Is it possible to call a process model when I click on the "Export to Excel" link and use the service instead of using
a!exportDataStoreEntityToExcel()
Yes, you can use start process link to call a process.
Is it not possible to call a process model using a!dynamicLink().
Thanks.
Is it possible to start/trigger process model using a!dynamicLink()
Since you have data in view, you can create a Appian record for that view. This record comes with Appian out of the box export to excel functionality. You can show the data in Appian UI and allow them to export the data.
Right now I am loading the data with a few columns in a read-only grid using the expression rule. But, there were several columns from different tables which needs to join to the main table and eventually load into excel.
Also excel data needs some customization, so not sure whether Record Type with multiple tables joined will support customization.
Rao2022 said:Is it possible to start/trigger process model using a!dynamicLink()
Yes. For this you would include a call to a!startProcess() within the dynamicLink's saveInto parameter. This would launch the referenced process model asynchronously (in other words, in the background exclusively), and the user would stay on the current form.
The good side is that you can have data generated by the process (including a created Document Id) save back into the local data on your original interface - meaning you could have the referenced process model generate a document, then pass that back to your form and expose it via a Document Download Link (i.e. contained in a Rich Text Display Field).