Hello everyone,We have a client requirement where we need to export Client and Employee data recieved from document extraction in a PM to an Excel template provided by the client, where client data should be inserted in their respective positions in sheet 1 and the multiple employee data should be inserted accordingly in its desginated cells in sheet 2.
Attached are pictures of the Excel template formats for both sheets, as well as the format of the data we are receiving.
We tried using the Export Data Store Entity to Excel smart service in the process model, but the results were unsatisfactory.
We also used Appian RPA Excel operations, which provided a solution, but it took 25 minutes, which is not viable in all conditions.
We are looking for a more efficient solution to export data into Excel. Any tips or assistance would be greatly appreciated.
Discussion posts and replies are publicly visible
RithwinV2000 said:I was not sure on how to configure the "CDT" field
It should literally be an array of the CDT (data) you want to be inserted into the generated Excel. Usually we just pre-populate this into a PV - that is, query some data into a PV value containing an array of that CDT. For some reason you've pointed this at a constant, which I expect won't do anything useful. Maybe you're confusing it with the "Export DSE to Excel" smart service, where you pass in a Data Store Entity and it does the querying for you? Not sure - but in any case this is incorrect and won't do anything (other than crash).
Instead what I'd expect to see there would be like "pv!myData" where that PV is an array of the CDT you want, into which you've queried that data already (with the added bonus that you can, if needed, iterate over it after it's queried and adjust values as needed). The "cdt fields to export" value, determines what fields from the CDT will be actually pulled into the generated document (assuming your field names match, your configuration on that one looks like it's probably already correct).