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
- 300 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Is this an outlook integration bug NAV2017
Mauddib
Member Posts: 269
Just testing Navision 2017 before upgrading Navision 2015 at the end of this month.
I got an error about a non-initialized Variable when using Outlook integration however. I was told "Microsoft.Dynamics.Nav.Exchange.ExchangeServiceWrapper.LastError" was not initialized.
Looking at Codeunit 5320 I find the following code in two places:
IF ISNULL(ServiceOnServer) THEN BEGIN
IF ServiceOnServer.LastError <> '' THEN
MESSAGE(ServiceOnServer.LastError);
END ELSE
IF ServiceOnServer.LastError <> '' THEN
MESSAGE(ServiceOnServer.LastError);
The code in both cases is identical. It looks to me that one of them (the first one I am guessing) should by MESSAGE(ServiceOnclient.LastError) right? Would I be safe to change it myself until MS fix the bug?
I got an error about a non-initialized Variable when using Outlook integration however. I was told "Microsoft.Dynamics.Nav.Exchange.ExchangeServiceWrapper.LastError" was not initialized.
Looking at Codeunit 5320 I find the following code in two places:
IF ISNULL(ServiceOnServer) THEN BEGIN
IF ServiceOnServer.LastError <> '' THEN
MESSAGE(ServiceOnServer.LastError);
END ELSE
IF ServiceOnServer.LastError <> '' THEN
MESSAGE(ServiceOnServer.LastError);
The code in both cases is identical. It looks to me that one of them (the first one I am guessing) should by MESSAGE(ServiceOnclient.LastError) right? Would I be safe to change it myself until MS fix the bug?
0