Inconsistent behavior when you synchronize postal codes between Microsoft Dynamics NAV 2009 SP1 and Microsoft Office Outlook

Applies to: Microsoft Dynamics NAV 2009 Service Pack 1

This article applies to Microsoft Dynamics NAV for all countries and all language locales.

Symptoms


When you set a contact card, Microsoft Dynamics NAV 2009 with Service Pack 1 (SP1) allows you to set a postal code that does not exist in the Post Code table (225). If this contact is synced to Microsoft Office Outlook, the synchronization process removes the postal code from the contact card in Outlook. Then, when you run the synchronization process next time, the postal code that is blank in Outlook is removed from Microsoft Dynamics NAV. In the synchronization process, the OSYNCH feature makes changes on the data without any notice.

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 service pack or the next 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, but 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 install this hotfix, drop the table relation for Post Code and City. To do this, follow these steps for the existing company in Microsoft Dynamics NAV:
  1. Click Administration, expand Application Setup, expand Microsoft Office Outlook Integration, and then click Outlook Synch. Entities.
  2. In the Code field, scroll to the "CONT_PERS" entity.
  3. Click Synch Entity, and then click Fields.
  4. Locate the BusinessAddressPostalCity row, clear the Table No. field, and then set the Field No. field to "7" or "City".
  5. Locate the BusinessAddressPostalCode row, clear the Table No. field, and then set the Field No. field to "91" or "Post Code".
In order to have the same setup by default, when you create a new company, change the code in the CreateDefaultContPers function in the codeunit (5300):


Existing code 1
InsertOSynchField(OSynchEntity.Code,0,OSynchEntity."Table No.",OSynchEntity."Outlook Item",'BusinessAddressCity',
FALSE,FALSE,225,2,'',0);OSynchField.RESET;
OSynchField.SETRANGE("Synch. Entity Code",OSynchEntity.Code);
OSynchField.SETRANGE("Element No.",0);IF OSynchField.FINDLAST THEN BEGIN
InsertOSycnhFilter(OSynchField."Record GUID",OSynchFilter."Filter Type"::"Table Relation",OSynchField."Table No.",
2,OSynchFilter.Type::FIELD,OSynchField."Master Table No.",7,'');
OSynchField."Table Relation" := ComposeFilterExpression(OSynchField."Record GUID",1);
OSynchField.MODIFY;END;
Replacement code 1
InsertOSynchField(OSynchEntity.Code,0,OSynchEntity."Table No.",OSynchEntity."Outlook Item",'BusinessAddressCity',
FALSE,FALSE,0,7,'',0);


Existing code 2
 InsertOSynchField(OSynchEntity.Code,0,OSynchEntity."Table No.",OSynchEntity."Outlook Item",'BusinessAddressPostalCode',
FALSE,FALSE,225,1,'',0);
OSynchField.RESET;
OSynchField.SETRANGE("Synch. Entity Code",OSynchEntity.Code);
OSynchField.SETRANGE("Element No.",0);
IF OSynchField.FINDLAST THEN BEGIN
InsertOSycnhFilter(OSynchField."Record GUID",OSynchFilter."Filter Type"::"Table Relation",OSynchField."Table No.",
1,OSynchFilter.Type::FIELD,OSynchField."Master Table No.",91,'');

OSynchField."Table Relation" := ComposeFilterExpression(OSynchField."Record GUID",1);
OSynchField.MODIFY;
END;

Replacement code 2
InsertOSynchField(OSynchEntity.Code,0,OSynchEntity."Table No.",OSynchEntity."Outlook Item",'BusinessAddressPostalCode',
FALSE,FALSE,0,91,'',0);

Prerequisites

You must have Microsoft Dynamics NAV 2009 SP1 installed to apply this hotfix.

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.

References


vstfnav DynamicsNAVSE 209766
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.