Is it possible to export more than one lakh records using records approach

Hi buddy,
try to use english terms that everyone can support you. lakh is indian ;)

you can use multiple other approaches:
you can add a view as data store entity.
https://docs.appian.com/suite/help/22.3/Export_To_Excel_Smart_Service.html
or
https://docs.appian.com/suite/help/22.3/Export_To_CSV_Smart_Service.html

and for the record export, you can fine some best practices here:
https://docs.appian.com/suite/help/22.2/Optimizing_Record_Lists_for_Export_to_Excel.html

is this helping you?

Just as a side note, we don't have the term "lakh" most other english-speaking places that I know of, so your question will probably be clearest to the most number of other users here if you just write out "hundred thousand" or "100,000", etc.

To your question: you have 2 potential approaches that I know of which might work.

1. use the old Excel Tools plug-in and CDT to Excel, and batch your export (i.e. 1000 rows at a time); or
2. use the newer Export DSE to Excel smart service which handles paging (but has several other sorely-missing features).

Hi Richard Michaelis

Thanks for your immediate response.

This was an existing project , we are not getting all values into database view.

-> we used stored proc to get required data, but while using CDT to excel plugin , it is occupying much java heap memory .

did you just one of the mentioned smart services?

and another question: what is the deeper sense to export that many lines into an excel? doesn't feel 100% senseful....

yes Richard Michaelis

Mr_AR said:

but while using CDT to excel plugin , it is occupying much java heap memory

As I mentioned below, you would need to manually implement paging while using this technique - i.e. only loading a certain amount of information into the process per pass, and updating the same file with your iterative passes.

I feel the same as you,

But business wants that functionality Richard Michaelis

Hi Mike Schmitt

Thanks for your immediate response.

I have used first approach, where I get data from stored proc , using loop concept and passing batches(10000) of data to CDT to Excel smart service,

but faced java heap issue and my environment get shut down:)

Any suggestions on how to use SQL to Excel plugin (How to call stored proc using this plugin)

I'd suggest maybe smaller batches.  And maybe clearing out your process variables data between iterations, if you didn't already try that.  And sadly, the CDT to Excel smart service may just be prone to this - i think that's one of the reasons it was deprecated.

I don't think SQL to Excel can deal with a stored procedure.  Your best bet would be probably to abandon the stored procedure concept and instead query from a view.  If your logic can't be accomplished by a view, then i'd bet that the proper alternative approach would be to have your stored procedure populate a temporary staging table, then query from that.  It looks like you may have already said you don't want to do this approach, but if it's the only working approach, the fact that you don't want to won't change things much ;-)