RTC - Excel Buffer Slow

lucab

Hi all
I've created a simple codeunit that import data from an excel using excel buffer, and insert data in NAV.

When I run this codeunit from classic client everithing works fine, and excel is readed in 30 sec. (10.000 rows).
But when I try tu run from RTC, read time grows to 30 min.

Is ExcelBuffer the right way to load data from excel in RTC?
Is there any way to load data from excel faster?

Thank you

rksaurabh

Hi,
you can use Automation server also to import and export data to/from excel sheet. it is bit faster than using excel buffer.

Marije_Brummel

I run the Excel buffer code in a report without RDLC layout. This way the C/AL code executed in classic mode and is fast.

If you export to Excel I advise to use a RDLC report with REPORT.SaveAsExcel

lucab

It works!
Thank you

Rob_Hansen

I am experiencing this issue as well. Does anyone know if it was improved in R2?

julkifli33

once i have developed import from excel
and it quite fast
now when moving to RTC, it still ok
but the issue is .... very slow...
how to make it better?
any idea?

mohana_cse06

check whether this blog fit for you
http://blogs.msdn.com/b/nav/archive/2011/08/18/dynamics-nav-export-to-excel-running-on-rtc.aspx

jayleferm

Sorry, I know this is about 2 years old but I have currently the same problem and I'm looking for a good solution without installing any DLLs on the Server.

I tried to used this solution:

mohana_cse06 wrote:

check whether this blog fit for you
http://blogs.msdn.com/b/nav/archive/2011/08/18/dynamics-nav-export-to-excel-running-on-rtc.aspx

Does anyone tried this blog entry in their system and get it working? I got so many compile errors because of code that could not fit.

Examples:
- The variable RecNo (Integer) from the copied trigger CreateSheet() will be assigned to a Text variable without EVALUATE

RecNo := xlRowID;

- Comparing Text with Integer

IF xlRowID <> RecNo

- Evaluating integer with an integer variable

EVALUATE(CurrXlRow,RecNo);

- Using a CONVERTSTR with a char variable, where a string is needed

Line[1] := CONVERTSTR(Line[1],CharsNavision,CharsWindows);

From the last point, I gave up, but to be honest, I can't imagine that a microsoft developer blog entry is defective like this. :-k

Nonetheless, how did you solve the problem with the slow Excel Buffer in the RTC NAV 2009 R2?