Howdy, Stranger!
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
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 305 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Long running processes/reports in NAV and unexpected errors
Developer101
Member Posts: 553
Hello,
I have been working with NAV as technical long time now. I never had chance to into this in detail but what we need to do when user gets some unexpected error after long running reports or processes.
Recently a colleague of mine was running a monthly report which ran for 1hr and 20 mins and it supposed to send result by email from outlook but then there was error something saying CreateItem method failed (it was outlook related). I believe she didn't have outlook open on the computer she was running report from. Now she has to do again.
But how to stop this happening? How to anticipate any issues before hand so that user be careful? How to develop something in NAV that should check everything is fine as pre-requisites and then run the process.
Note: The report I am talking about is the customized one. It produces an excel sheet which then is sent by email.
We been using that report for some time now regularly.
Please help.
I have been working with NAV as technical long time now. I never had chance to into this in detail but what we need to do when user gets some unexpected error after long running reports or processes.
Recently a colleague of mine was running a monthly report which ran for 1hr and 20 mins and it supposed to send result by email from outlook but then there was error something saying CreateItem method failed (it was outlook related). I believe she didn't have outlook open on the computer she was running report from. Now she has to do again.
But how to stop this happening? How to anticipate any issues before hand so that user be careful? How to develop something in NAV that should check everything is fine as pre-requisites and then run the process.
Note: The report I am talking about is the customized one. It produces an excel sheet which then is sent by email.
We been using that report for some time now regularly.
Please help.
United Kingdom
0
Comments
- Executing the process and, in case of errors, save the result somewhere (table for example) in order to use it again in a new execution, with the risk of providing inconsistent data.
- Performing as much check as possible at the beginning of the process, before starting any business logic; I usually prefer this one since follows the usual streamline of posting routines.
Just my 2 cents