Empty contacts are created in dedicated Outlook Synch folder when you perform the Outlook synchronization in Microsoft Dynamics NAV 2009

Article translations Article translations
Article ID: 2703500 - View products that this article applies to.
This article applies to Microsoft Dynamics NAV for all countries and all language locales.
Expand all | Collapse all

On This Page

Symptoms

Assume that you create a new entity in Microsoft Dynamics NAV 2009 R2 and in Microsoft Dynamics NAV 2009 Service Pack 1 (SP1). When you perform the Outlook synchronization for the entity, empty contacts are created in dedicated Outlook Sync folder.

Cause

This problem occurs because the contacts are read-only in Outlook after you create the new entity.

Resolution

Hotfix information

A supported hotfix is now available from Microsoft. However, it is only intended to correct the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Dynamics NAV 2009 service pack or the next Microsoft Dynamics NAV version that contains this hotfix.

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Installation information

Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure. However, they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.

Note Before you install this hotfix, verify that all Microsoft Navision client users are logged off the system. This includes Microsoft Navision Application Services (NAS) client users. You should be the only client user who is logged on when you implement this hotfix.

To implement this hotfix, you must have a developer license.

We recommend that the user account in the Windows Logins window or in the Database Logins window be assigned the "SUPER" role ID. If the user account cannot be assigned the "SUPER" role ID, you must verify that the user account has the following permissions:
  • The Modify permission for the object that you will be changing.
  • The Execute permission for the System Object ID 5210 object and for the System Object ID 9015 object.


Note You do not have to have rights to the data stores unless you have to perform data repair.

Code changes

Note Always test code fixes in a controlled environment before you apply the fixes to your production computers.
To resolve this problem, use one of the following methods:
  • Change the code in the ValidateOItemPropertyName function in the Outlook Synch. Setup Mgt. Codeunit (5300) as follows:
    Existing code
    ...
    IF TempOSynchLookupName.FINDFIRST THEN BEGIN
    InputString := TempOSynchLookupName.Name;
    OPropertyInfo := OObjInfo.GetProperty(TempOSynchLookupName."Entry No.");
    IsReadOnly := OPropertyInfo.IsReadOnly;
    EXIT(TRUE);
    END;
    ...
    
    Replacement code
    ...
    IF TempOSynchLookupName.FINDFIRST THEN BEGIN
    InputString := TempOSynchLookupName.Name;
    OPropertyInfo := OObjInfo.GetProperty(TempOSynchLookupName."Entry No.");
    // IsReadOnly := OPropertyInfo.IsReadOnly;
    EXIT(TRUE);
    END;
    ...
    
  • Change the code in the following functions in the Outlook Synch. Setup Mgt. Codeunit (5300):
    • CreateDefaultContPers
    • CreateDefaultContComp
    • CreateDefaultContSp
    • CreateDefaultTask
    • CreateDefaultApp
    To do this, add the following line in the code in the functions as the one that is used for inserting the fields in table 5304:
    InsertOSynchField(OSynchEntity.Code,0,OSynchEntity."Table No.",OSynchEntity."Outlook Item",'BusinnessAddress',
    FALSE,FALSE,0,2,'',0);
    

Prerequisites

You must have one of the following products installed to apply this hotfix:
  • Microsoft Dynamics NAV 2009 R2
  • Microsoft Dynamics NAV 2009 Service Pack 1

Removal information

You cannot remove this hotfix.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 2703500 - Last Review: June 21, 2014 - Revision: 3.0
Applies to
  • Microsoft Dynamics NAV 2009
Keywords: 
kbqfe kbmbspartner kbmbsmigrate kbMBSQuickPub kbsurveynew kbnoloc kbmbscodefix KB2703500

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com