Hello,
We are using the "Export Data Store Entity to Excel" smart service. Our datetime values in the database are all saved as GMT, but when we export to Excel, we want the users to see the datetimes in their local timezone. In the queryEntity within this smart service, is it possible to query the datetimes and have them appear in the Excel as the users' local times? The only information we have on the user is the username who started the process.
Thank you!
Discussion posts and replies are publicly visible
This illustrates my big issue with the EDSEtE smart service and the recent unannounced deprecation/removal of the Export CDT to Excel smart service from the Excel Tools plug-in: we are left with basically no way by which to transform data in-process between database querying and writing to the Excel file. Another good example of a need for this is displaying a user's full name when the DB holds only their username, etc - there's no way to necessarily do that via a DB view, and no workarounds that don't get pretty silly pretty quickly.
Hi Mike,
Do you mean Export data store entity to excel smart service support paging?
Yes.
Many thanks Mike!!
We are on 18.1 version and I am using EDETE , I want to use excel template to generate report but getting error.
Is that due to smart service not supporting EXCEL template.
If yes, What is the best to use for this?
Please help.
That depends, what error are you getting? How do you have it configured? It's true that it doesn't support an Excel template, but as far as I know it just isn't a possibility, it doesn't cause any errors that I know of.
Hi Mike ,
i do not see any way of passing the paging info to the export data store to smart service if i want to fetch the data in bathes. I am on 18.1 and trying to create an export of large amount of data ( around 500K records or more). Any suggestions for this .
Thank you.
The Export Data Store Entity to Excel smart service was introduced in Appian 18.2, as best I remember - so I'm unclear what you're currently trying to use, but batching would need to be handled manually which will probably be difficult.