Slow performance writing to Excel in RTC.

MrBill1962

Hi All. I'm experiencing a strange situation. I know that the RTC environment does things differently than classic but this one has me quite puzzeled. First, background.

I am developing this report in NAV 2009 R2. Report has a option to Export to Excel which utilizes the standard Excel buffer and logic. If the report is previewed without exporting to Excel is renders about 380 records (10 columns) in seconds in both Classic and RTC. However, when including the Excel option and clicking preview it produces completely different speeds in performance. In classic the Excel sheet is rendered in a few seconds. However in RTC this same report with the exact same data and filters takes over 5 minutes to render the Excel spreadsheet and about 3 minutes to then render the preview. While 8 minutes of hardly the end of the world, it is unreasonable when considering it is only 380 rows of data and the extreme difference when compared to classic. ](*,)

I do realize that I could break the Excel out as a separate object. But not only is this a waste of an object, there isn't any guarantee that the Excel part will be any better.

Anyone see anything like this? Any suggestions?

Once more question. Is there anyway to disable the window that RTC automatically pops up that shows how many rows have been processed? The window is big and blocks the Excel dialog which at least show accurately the progress of building the spreadsheet.

geordie

Yes, there is a performance decrease with Excel Buffer in NAV 2009 RTC. The possible solution are:

1) Run the export in a report without RDLC in order to force the code to be execute in classic mode.
2) Generate a .csv instead of an Excel file (some suggestion here).
3) Apply some code modification to increase the speed (see here, sorry for German link :oops: ).
4) Make Excel Buffer table working with .NET Interoperability, in my opinion the best solution, following this guideline.

MrBill1962

Has this issue been corrected in NAV 2013?

geordie

Yes, because .NET Interoperability is used in the out-of-box version instead of Automations, with the only disadvantage that they are wrappers of Excel interface (implies that the possibilities to expand standard Excel Buffer functionality in NAV 2013 are quite limited, unless you switch to ClosedXML).