Slow Triggers in Dataport

HalMdy
Member Posts: 429
Hello everybody !!!
First message, first problem, first help needed ... here we are :
I have one Export Dataport based on several tables. This dataport doesn't use a Request Form. Unfortunatelly, it takes a lot of time ( more than 1 minut) between OnInitDataport trigger and OnPreDataport trigger.
:?: Do you have any idea about what's the job done between these triggers and how can I make it more faster ?
:idea: To be complete, I work with a SQL base 3.10 version of Attain.
Thx for help and cheers !
First message, first problem, first help needed ... here we are :
I have one Export Dataport based on several tables. This dataport doesn't use a Request Form. Unfortunatelly, it takes a lot of time ( more than 1 minut) between OnInitDataport trigger and OnPreDataport trigger.
:?: Do you have any idea about what's the job done between these triggers and how can I make it more faster ?
:idea: To be complete, I work with a SQL base 3.10 version of Attain.
Thx for help and cheers !
0
Comments
-
any code there onInitDataPort ?
Where are you exporting on local disk, network... etc.®obi
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯0 -
Here is part of the code, to be more complete ...
OnInitDataport()
Window.OPEN(Text7013464);
Window.UPDATE(1,'1');
...
//File to create is on Client hard disk
CurrDataport.FILENAME:=CurrDataport.FILENAME+COPYSTR(str,1,pos)
CurrFile.QUERYREPLACE:=FALSE;
Window.UPDATE(1,'2');
OnPreDataport()
Window.UPDATE(1,'3');
OnPostDataport()
Window.CLOSE
So time between display '2' and '3' takes more than 1 minut. No difference if I work on a network or if I first delete the file ... :?0 -
Nothing suspicious.
Do you really need this dialog to open in OnInit ?
Maybe to open it on PreDataport ?
Or you just use it to figure it out where the delay comes from ?
What about debugging - same delay ?
What exactly are you doing with filename ?
Doy you have any other code OnInitReport (instead of ...) ?®obi
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯0 -
Finally, I understand !!
There is no other custom code in the triggers. Simply, between OnInit and OnPreDataport, the system prepares the records to compute, with keys and filters defined in the properties of each table called.
In my case, one of the filters is on a flowfied (lookup) wich takes a long time to be computed --> so dataport initialization is very slow.
Hope this can help others in the future ...0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions