Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.6K 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
- 298 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
New Outlook integration with NAV5.00 - Does not work !
theo.s
Member Posts: 24
Has anybody tried to use this? I get some nasty NAS errors, due a text overflow when a Hash is calcualted.
In fact there are quite a few places this happens, and you dicover them as you start modifying the NAS Code..
The Hash destination fields are 32 characters long and the hashes returned are much longer than that. There are many instance of calls similar to this, using the ..Base64:
// EntryIDHash := HashCalculator.CalculateFromLongTextBase64(Container);
I modified them all to this, and actually got the Integration to work..
EntryIDHash := HashCalculator.CalculateFromLongText(Container);
I did this all these codeunits:
Type ID Name Modified Version List Date Time BLOB Size Compiled
5 5304 Outlook Synch. Outlook Mgt. Yes NAVW15.00,SBS5.02 07/01/08 15:20:40 22716 Yes
5 5305 Outlook Synch. Process Line Yes NAVW15.00,SBS5.02 07/01/08 15:23:02 127612 Yes
5 5306 Outlook Synch. Export Schema Yes NAVW15.00,SBS5.02 07/01/08 14:28:52 30836 Yes
5 5309 Outlook Synch. Process Links Yes NAVW15.00,SBS5.02 07/01/08 15:17:25 20420 Yes
The Question is, are we doing something strange here in ZA, or was this integratio nnever tested in the final release?
In fact there are quite a few places this happens, and you dicover them as you start modifying the NAS Code..
The Hash destination fields are 32 characters long and the hashes returned are much longer than that. There are many instance of calls similar to this, using the ..Base64:
// EntryIDHash := HashCalculator.CalculateFromLongTextBase64(Container);
I modified them all to this, and actually got the Integration to work..
EntryIDHash := HashCalculator.CalculateFromLongText(Container);
I did this all these codeunits:
Type ID Name Modified Version List Date Time BLOB Size Compiled
5 5304 Outlook Synch. Outlook Mgt. Yes NAVW15.00,SBS5.02 07/01/08 15:20:40 22716 Yes
5 5305 Outlook Synch. Process Line Yes NAVW15.00,SBS5.02 07/01/08 15:23:02 127612 Yes
5 5306 Outlook Synch. Export Schema Yes NAVW15.00,SBS5.02 07/01/08 14:28:52 30836 Yes
5 5309 Outlook Synch. Process Links Yes NAVW15.00,SBS5.02 07/01/08 15:17:25 20420 Yes
The Question is, are we doing something strange here in ZA, or was this integratio nnever tested in the final release?
0
Comments
There is update for Outlook synchronization released.
Look in partnersource for KB KB 945879. You can download it from there.