When you deploy ClickOnce for Dynamics NAV 2015, there is an inconsistency related to SQL Server 2014 support tools. The product DVD does have SQL Server installation files in the Prerequisite Components folder:
– \Microsoft Report Viewer 2014\ReportViewer.msi
– \Microsoft Report Viewer 2014\SQLSysClrTypes.msi

The ClickOnce template to be found in the folder \ClickOnceInstallerTools\Program Files\Microsoft Dynamics NAV\80\ClickOnce Installer Tools\TemplateFiles\NAVClientInstallation.html still refers to SQL Server 2012.

The Microsoft Report Viewer 2014 and the CLR Types for Microsoft SQL Server 2014 will not be officially released until Visual Studio 2014 ships. Until that happens the partners have these two options for resolving this issue:

1. Either the partner can take the .msi files from the NAV 2015 installation media and place these on a files hare and update the ClickOnce landing page accordingly
2. Or the partner can modify the configuration file for the RTC client to load the 2012 version of the assemblies. This is done by adding the following section to the file: Microsoft.Dynamics.Nav.Client.exe.config, which is included in the ClickOnce application package. The section is:

<dependentAssembly>
  <assemblyIdentity name=”Microsoft.ReportViewer.WinForms” publicKeyToken=”89845dcd8080cc91″ culture=”neutral”/>
  <bindingRedirect oldVersion=”12.0.0.0″ newVersion=”11.0.0.0″/>
</dependentAssembly>

For an example of how to add the dependentAssembly configuration element, please refer to this page on msdn: http://msdn.microsoft.com/en-us/library/0ash1ksb(v=vs.110).aspx

For the time being, this is sufficient to deploy ClickOnce for Dynamics NAV 2015.

Kindest regards,

Marco Mels
Support Escalation Engineer, CSS
Microsoft

These postings are provided “AS IS” with no warranties and confer no rights. You assume all risk for your use. The Netherlands

The post ClickOnce template in Dynamics NAV 2015 still contain references to SQL Server 2012 appeared first on Microsoft Dynamics 365 Blog.

Unfortunately, it is not possible to select multiple filter values for an option field on a request page of a report in the Web Client. This is however possible in the Windows Client. In the GUI of the Web Client it is possible to select a range as a filter though there is no underlying coding that supports this. Documentation around limitations of Web Client can be found here.

The Web Client was originally designed for an occasional use as opposed to intensive use for which we have the Windows Client. Partner and Customer feedback has clearly indicated that the strengths of the Web Client (e.g., easy to deploy, runs in major browsers) have pushed adoption well beyond its’ intended use. In feature releases we will therefore address the functionality of the Web Client further.

These postings are provided “AS IS” with no warranties and confer no rights. You assume all risk for your use.

Marco Mels
Microsoft Dynamics NAV

The post Select multiple filter values on a request page for an option field in Web client compared to Windows Client appeared first on Microsoft Dynamics 365 Blog.

On MSDN it is written that the Owner ID field became obsolete and should be removed from specific pages. This means that anyone can start up the Windows Client and configure a Role Center without any restrictions. Reasoning behind this is explained in this small blog posting among a new approach that does give a better handling of this.

The Owner ID was removed from the profile table during the multitenant work. The Profiles are in the application table and can’t have references to users which are in the tenants. The feature itself was not that well thought through. On all other records we have a last person saving wins.

The proposed workaround / solution is to use a permission set per profile and use record level security to restrict access to that particular profile ID.

To resolve the issue and get the old behavior back, you need to create a new Permission Set. E.g.:

TEST PROFILE
Following details:
Object Type   Object ID        Object Name         R/I/M/D   Security FIlter
Table Data     2000000072  Profile Metadata     Yes          Profile: Profile ID=ACCOUNTING MANAGER

After logging on with a user in configuration mode that has two permission sets applied (BASIC and TEST PROFILE) with a profile called IT Manager, it is no longer possible to change the role center and make changes.

Kindest regards,

Marco Mels
Microsoft Dynamics Netherlands

Microsoft Customer Service and Support (CSS) EMEA

The post Owner ID field became obsolete in Dynamics NAV appeared first on Microsoft Dynamics 365 Blog.

It has been a while since I last wrote a posting about the SMTP Server component that we first shipped with Dynamics NAV 5.0. Let’s recap the older posting first as it does list a complete list of patches that one should have applied already and let me take the opportunity to also discuss some previous support cases that were filed at our support service regarding specific Italian localization that only applies to Italian partners / customers. Last but not least some support cases were filed at our support service in regards to Office 365. Let’s also discuss these.

The previous posting can be found here: Double impersonation within a three tier environment and the SMTP Server setup in Microsoft Dynamics NAV. A later patch did came out as well: 2811780 where we added some code to code unit 400 to allow a timer to be configured via C/AL. Previous support cases were filed by Italian partners requesting if they could use our SMTP Server component with Posta Elettronica Certificata which is an alternate connection configuration via SMTP/SSL over port 465. More information about PEC can be found here: IETF and Wikipedia

The SmtpClient.EnableSsl property is responsible for this and is discussed on MSDN. Here you can read the following:

An alternate connection method is where an SSL session is established up front before any protocol commands are sent. This connection method is sometimes called SMTP/SSL, SMTP over SSL, or SMTPS and by default uses port 465. This alternate connection method using SSL is not currently supported.

Last but not least Microsoft Support received several requests from partners how they should configure Dynamics NAV SMTP Server component in combination with Office 365. The good news is that this is possible, but there are some challenges, especially when you use the SMTP Server component in combination with Document Approval system that we shipped with Dynamics NAV. Let’s assume the latter. The prerequisites are:

• You need to apply all patches listed on Double impersonation within a three tier environment and the SMTP Server setup in Microsoft Dynamics NAV
• You need to have administrative access to Office 365 in combination with administrative access to Exchange Online if you also want to setup Document Approval
• You need to download the PowerShell commands from here  to configure the SendAs permissions for the accounts because “Any e-mails sent by the application / device must be from the authenticated account above“
• You then need to follow instructions written here

Let’s show you how this does work. When you start the PowerShell, a box is shown to you with the following line: “PS C:\Windows\system32>”. After that line, you can type the commands one at a time.

First command:

PS C:\Windows\system32> Set-Executionpolicy -ExecutionPolicy Unrestricted

Execution Policy Change
The execution policy helps protect you from scripts that you do not trust. Changing the execution policy might expose
you to the security risks described in the about_Execution_Policies help topic at
http://go.microsoft.com/fwlink/?LinkID=135170. Do you want to change the execution policy?

[Y] Yes  [N] No  [S] Suspend  [?] Help (default is “Y”): y

Second command:

PS C:\Windows\system32> $LiveCred = Get-Credential

cmdlet Get-Credential at command pipeline position 1
Supply values for the following parameters:
Credential

Third command:

PS C:\Windows\system32> $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic -AllowRedirection

WARNING: Your connection has been redirected to the following URI:
“https://pod51014psh.outlook.com/powershell-liveid?PSVersion=3.0 ”
WARNING: Your connection has been redirected to the following URI:
“https://db3prd0411psh.outlook.com/powershell-liveid?PSVersion=3.0 ”

Fourth command:

PS C:\Windows\system32> Import-PSSession $Session

ModuleType Name                                ExportedCommands

———- —-                                —————-

Script     tmp_2b2tb1qp.44s                    {Add-AvailabilityAddressSpace, Add-DistributionGroupMember, Add-Mailb…

Fifth command:

PS C:\Windows\system32> Add-RecipientPermission “Kevin Mels” -AccessRights SendAs -Trustee “Marco Mels”

Confirm
Are you sure you want to perform this action?
Adding recipient permission ‘SendAs’ for user or group ‘Marco Mels’ on recipient ‘Kevin Mels’.
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [?] Help (default is “Y”): Y

Identity                Trustee                 AccessControlType       AccessRights            Inherited
——–                ——-                 —————–       ————            ———
kevinmels               marcomels               Allow                   {SendAs}                False

Sixth command:

PS C:\Windows\system32> Add-RecipientPermission “Sean Bentley” -AccessRights SendAs -Trustee “Marco Mels”

Confirm
Are you sure you want to perform this action?
Adding recipient permission ‘SendAs’ for user or group ‘Marco Mels’ on recipient ‘Sean Bentley’.
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [?] Help (default is “Y”): Y

Identity                Trustee                 AccessControlType       AccessRights            Inherited
——–                ——-                 —————–       ————            ———
seanbentley             marcomels               Allow                   {SendAs}                False

PS C:\Windows\system32>

Document Approval setup looks like this:

PS C:\Windows\system32> Remove-PSSession $Session

To summarize, Marco Mels (marcomels@bergmanz.onmicrosoft.com) configured in the SMTP settings is the trustee and you need to add SendAs recipient for all users that are in the Approval User Setup form.

Some other commands to verify the setup if needed:

PS C:\Windows\system32> Get-RecipientPermission “Sean Bentley” -AccessRights SendAs

Identity                     Trustee                               AccessControlType       AccessRights            Inherited
——–                        ——-                                  —————–       ————            ———
seanbentley             NT AUTHORITY\SELF       Allow                   {SendAs}                False
seanbentley             marcomels                        Allow                   {SendAs}                False

The Windows Powershell must be started via “Run as Administrator”and you need to specify user credentials within Office365 that does have Administrator permissions. Truly hope this does help you to configure SMTP Server component in Dynamics NAV in combination with Office 365.

Regards,

Marco Mels
CSS EMEA

This posting is provided “AS IS” with no warranties, and confers no rights

The post SMTP Server component in Dynamics NAV, latest news, latest patches and some configuration challenges with Office 365 appeared first on Microsoft Dynamics 365 Blog.

During one of the conferences I attended where I spoke about Outlook Synchronization, the request was to talk about the creation of new entities and extending the solution with new fields. Let’s do this now with a new blog. First of all, you need to ensure you have applied latest patches and fixes. For this you can use my earlier blog I created Baseline implementation utilizing Outlook Synchronization in Dynamics NAV 2009 R2, especially we must apply the following code adjustment discussed in the following KB article 2703500 Empty contacts are created in dedicated Outlook Synch folder when you perform the Outlook synchronization in Microsoft Dynamics NAV 2009

The scenario is as follows. We want to split the Dynamics NAV contacts of person type in Belgium ones and Dutch ones. We first delete the CONT_PERS entity. To do so, start up RTC and select CRONUS International Ltd./Departments/Administration/Application Setup/Microsoft Office Outlook Integration/Outlook Synch. User Setup. Manually select all lines and either press CTRL+DEL or right click and select Delete. Second step is to delete the CONT_PERS entity. To do so, follow these steps. In RTC, select CRONUS International Ltd./Departments/Administration/Application Setup/Microsoft Office Outlook Integration/Outlook Synch. Entities, select CONT_SP and press CTRL+SHIFT+E or right click the entity and select Delete. Confirm the deletion that collections will be updated automatically.

Result of this is that we now have the following standard entities: CONT_SP, CONT_COMP, TASK and APP. Let us now create a two new entities. In RTC, select CRONUS International Ltd./Departments/Administration/Application Setup/Microsoft Office Outlook Integration/Outlook Synch. Entities, press New and type in a unique code and a unique description. E.g.:

After that select Related Information, Synch. Entity, Reset to defaults, select Microsoft Dynamics NAV Contacts of the Person type and press OK.

NOTE: you should do similar steps to create another entity for the Dutch contacts of person type.

Now it is time to add dependencies for APP entity and TASK entity. To do so, in RTC select CRONUS International Ltd./Departments/Administration/Application Setup/Microsoft Office Outlook Integration/Outlook Synch. Entities, select APP entity, press Actions, select Edit or right click on the entity and select Edit. You could also select the entity and press CTRL+SHIFT+E. Now select the first line and select Recipients under Outlook Collection. Press SHIFT+F8 or right click on Recipients and select DrillDown.

Now ensure the Table Relations do look like the following:

We also need to change Table Relations for the Links of the TASK entity. To do so, in RTC select CRONUS International Ltd./Departments/Administration/Application Setup/Microsoft Office Outlook Integration/Outlook Synch. Entities, select TASK entity, press Actions, select Edit or right click on the entity and select Edit. You could also select the entity and press CTRL+SHIFT+E. Now select the first line and select Links under Outlook Collection. Press SHIFT+F8 or right click on Links and select DrillDown.

Now ensure the Table Relations do look like the following:

Last but not least we need to add the Outlook Synchronization Users. In RTC, select CRONUS International Ltd./Departments/Administration/Application Setup/Microsoft Office Outlook Integration/Outlook Synch. User Setup. For every entity, add a line. E.g.:

To test this new configuration, you could try the following.

1. (Re)Configure the Outlook Add-In so that they are populated with new folders
2. Ensure there are contacts where Country/Region Code do have NL / BE set
3. Perform a synchronization

Result:
The Dynamics NAV contacts of company type assigned to salesperson Marco Mels do synchronize correctly.
The Belgium Dynamics NAV contacts of person type do synchronize correctly.
The Belgium Dynamics NAV contacts of person type do synchronize correctly.

4. Create a To-Do of meeting type and add two attendees where one attendee is a Dutch contact of person type and the other attendee is a Belgium contact of person type
5. Perform a synchronization

Result:
A calendar entry is created in Outlook with the meeting organizer which is the salesperson Marco Mels and the Belgium and Dutch contact of person type

Regards,

Marco Mels
CSS EMEA

This posting is provided "AS IS" with no warranties, and confers no rights

The post Complicating the synchronization setup with newly created entities appeared first on Microsoft Dynamics 365 Blog.

Not that long ago I was involved with a very interesting escalation stating that it was not possible to send out E-mails via CU400 utilizing NTLM in a three tier environment with the Role Tailored Client only in an Exchange Server 2007 / 2010 environment. When using the CSIDE Client, everything worked perfectly. The cause is that the Role Tailored Client in a three tier environment sent the E-mail to the NST box that uses impersonation to send out an E-mail. What happens from technical side of view is that some sort of double impersonation had to take place.

The solution is too easy to implement but let me first try to explain this with the scenario I worked on. For the test I did use Document Approval scenario. This does utilize CU400. Before actually describing the scenario, I reviewed the following patches for SMTP:

2499881    You cannot configure the TLS settings for SMTP communication in Microsoft Dynamics NAV 2009
https://mbs.microsoft.com/knowledgebase/KBDisplay.aspx?scid=kb;EN-US;2499881

2345735    You cannot change the default port for SMTP Communication in Microsoft Dynamics NAV
https://mbs.microsoft.com/knowledgebase/KBDisplay.aspx?scid=kb;EN-US;2345735

2479702    The email message body is incorrect when you create an email message by using the AppendBody method in Microsoft Dynamics NAV 2009 Service Pack 1
https://mbs.microsoft.com/knowledgebase/KBDisplay.aspx?scid=kb;EN-US;2479702

2280492    Attachments are not released until the Microsoft Dynamics NAV client is closed when you use the SMTP Mail codeunit (400) to send email messages that have attachments
https://mbs.microsoft.com/knowledgebase/KBDisplay.aspx?scid=kb;EN-US;2280492

2516144    You receive malformed email messages if you use a specific version 7 release of the Microsoft.Navision.Mail.dll file in Microsoft Dynamics NAV 2009
https://mbs.microsoft.com/knowledgebase/KBDisplay.aspx?scid=kb;EN-US;2516144

1. install Exchange 2007 SP1 on Windows Server 2008 R2
2. install SQL Server 2008 R2 on Windows Server 200x R2
3. install ServiceTier + RTC on Windows Server 2088 R2
4. install CC and RTC on Windows 7

NOTE: for the test all relevant Windows Updates were installed, latest service packs and latest builds of Dynamics

5. create a new account called NAVSRV which will be used to start up SQL / NST
6. configure Document Approval according to the attached PPT

NOTE: for the test we will primarily use the accounts called Susan, Navsrv and Kevin which is a newly created Salesperson
NOTE: for the test all user accounts are SUPER users in Dynamics NAV, Local Administrators on all machines being used and member of Domain Admin
NOTE: the following machine names are being used:

=> EX2K7-1 : Exchange 2007 SP3
=> WIN2K3-3 : SQL 2008 R2
=> WIN2K3-4 : NST + RTC
=> WIN7-2 : CC + RTC

NOTE: the following spn’s were used and set to the NAVSrv user account:

userPrincipalName: navsrv@mels.com
servicePrincipalName: MSSQLSvc/win2k3-3.mels.com:1433
servicePrincipalName: MSSQLSvc/win2k3-3.mels.com
servicePrincipalName: http/WIN2K3-4.mels.com
servicePrincipalName: http/WIN2K3-4
servicePrincipalName: DynamicsNAV/WIN2K3-4:7046
servicePrincipalName: DynamicsNAV/WIN2K3-4.mels.com:7046

NOTE: the following Delegations were setup for NAVSrv account:

Trust this user for delegation to specified services only:

– Use any authentication protocol

MSSQLSvc win2k3-3.mels.com 1433

7. follow MSDN to ensure the three tier environment is configured correctly

Test:
=> start up RTC on Windows 7 using user account Susan [OK}

8. review the above mentioned patches for SMTP and modify the code where needed
9. run the following command regasm /codebase microsoft.navision.mail.dll /tlb:microsoft.navision.mail.tlb using build v7.03.1
10. compile the non compiled objects
11. configure CU400 with the following values:

EX2K7-1
NTLM
25

12. start up Exchange 2007 MMC and create a new Receive Connector, to do so follow these steps:

=> select Microsoft Exchange / Server Configuration / Hub Transport
=> select an empty area under button Receive Connectors and right click, New Receive Connector

13. configure the newly created connector with the following values:

General tab:
=> Name: CRM Connector
=> mail.mels.com

Network tab:
=> local IP address of EX2K7-1, port 25
=> remote IP address of WIN2K3-4
=> Authentication: Integrated Windows Authentication

Permissions Groups:
=> Exchange servers

14. create a new Send Connector, to do so, follow these steps:
=> select Microsoft Exchange / Organization Configuration / Hub Transport
=> select Send Connectors
=> select an empty area under button Send Connectors and right click, New Send Connector

15. configure the newly created connector with the following values:

General tab:
=> Name: SMTP Send connector
=> Address Space: SMTP * 1

Network tab:
=> Route mail through the following smart hosts
=> Smarthost: IP address of remote Exchange 2003 server (not part of this test)

Source Server tab:
EX2K7-1 Default-First-Site-Name Mailbox, Client Access, Hub Transport

Test:
=> log on to WIN7-2 with user account Susan using CC and create a Purchase Quote so that an approval request needs to be done (> 5000)
=> the approval request is created and an E-mail is sent to Kevin

Test:
=> log on to WIN7-2 with user account Susan using RTC and create a Purchase Quote so that an approval request needs to be done (> 5000)

Error on the client:

The SMTP mail system returned the following error: The SMTP server requires a secure connection or the client was not authenticated. The server respones was: 5.71. Client was not authenticated.

Error on EX2K7-1 application event log file:
The account ‘NT AUTHORITY\ANONYMOUS LOGON’ provided valid credentials, but is not authorized to use the server; failing authentication

NOTE: The errors are well known and described in the MS Exchange 2007 Transport whitepaper (http://approjects.co.za/?big=download/en/details.aspx?id=975):

530 5.7.1 Client was not authenticated

The sender specified in the MAIL FROM field of the SMTP protocol doesn’t have permission to submit to this server. The ms-Exch-SMTP-Submit permission must be granted to the sender.

16. add extended permissions to the newly created connector:

Get-ReceiveConnector “CRM Connector” | Add-ADPermission -User “NT AUTHORITY\ANONYMOUS LOGON” -ExtendedRights “ms-Exch-SMTP-Accept-Submit”

Test:
=> log on to WIN7-2 with user account Susan using RTC and create a Purchase Quote so that an approval request needs to be done (> 5000)

Error on the client (described in the whitepaper):
550 5.7.1 Client does not have permission to send as this sender

The sender specified in the MAIL FROM field of the SMTP protocol conversation is an address in an authoritative domain. However, the session doesn’t have the ms-Exch-SMTP-Accept-Authoritative-Domain-Sender permission. This might occur if a message was submitted from the Internet to an Edge Transport server from a sender address for which the Exchange organization is authoritative.

17. add extended permissions to the newly created connector:

Get-ReceiveConnector “CRM Connector” | Add-ADPermission -User “NT AUTHORITY\ANONYMOUS LOGON” -ExtendedRights “ms-Exch-SMTP-Accept-Authoritative-Domain-Sender”

Test:
=> log on to WIN7-2 with user account Susan using RTC and create a Purchase Quote so that an approval request needs to be done (> 5000)

Error on the client (described in the whitepaper):
550 5.7.1. Unable to relay

The recipient domain to which the message is addressed isn’t within any of the accepted domains defined for this organization. Also, the session doesn’t have the ms-Exch-SMTP-Accept-Any-Recipient permission.

18. add extended permissions to the newly created connector:

Get-ReceiveConnector “CRM Connector” | Add-ADPermission -User “NT AUTHORITY\ANONYMOUS LOGON” -ExtendedRights “ms-Exch-SMTP-Accept-Any-Recipient ”

Test:
=> log on to WIN7-2 with user account Susan using RTC and create a Purchase Quote so that an approval request needs to be done (> 5000)
=> the approval request is created and an E-mail is sent to Kevin

19. change SMTP Mail Setup in Dynamics NAV to Anonymous

Test:
=> log on to WIN7-2 with user account Susan using RTC and create a Purchase Quote so that an approval request needs to be done (> 5000)
=> the approval request is created and an E-mail is sent to Kevin

NOTE: when using RTC with user account NAVSrv on the NST box, switching between Anonymous and NTLM does produce the correct behavior. Mail cannot be sent with error 530 5.7.1 Client was not authenticated and mail can be sent without error.

Along the way we had quite a lot of fun while testing. If you run in this kind of scenario, the way to fix this is via code in CU400 where you instruct the RTC to directly contact the Exchange Server in stead of via the NST box. This will ensure the Role Tailored Client behaves similar as the CSIDE Client:
2618652 Double impersonation and the SMTP Server setup in Dynamics NAV
http://support.microsoft.com/kb/2618652

Regards,

Marco Mels
CSS EMEA

This posting is provided “AS IS” with no warranties, and confers no rights

The post Double impersonation within a three tier environment and the SMTP Server setup in Microsoft Dynamics NAV appeared first on Microsoft Dynamics 365 Blog.

After setting up a new synchronization entity in Dynamics NAV 2009 SP1 to synchronize a specific Dynamics NAV table to Microsoft Outlook, the result of the first synchronization is that empty records are being created. E.g.:

The reason for this is that table 5304, field 15, contains a Read-Only Status field set to Read-Only in Outlook:

These fields are not synchronized because they are marked as Read-Only in Outlook. This property is retrieved from MAPI for each field. The default entities are generated via CU5300 where the fields are inserted via code. As a work around we suggest one of these 2 options:

1) remove the validation in COD5300 in ValidateOItemPropertyName trigger

[BEFORE]

IF TempOSynchLookupName.FINDFIRST THEN BEGIN
  InputString := TempOSynchLookupName.Name;
  OPropertyInfo := OObjInfo.GetProperty(TempOSynchLookupName."Entry No.");
  IsReadOnly := OPropertyInfo.IsReadOnly;
  EXIT(TRUE);
END;

[AFTER]

IF TempOSynchLookupName.FINDFIRST THEN BEGIN
  InputString := TempOSynchLookupName.Name;
  OPropertyInfo := OObjInfo.GetProperty(TempOSynchLookupName."Entry No.");
  //IsReadOnly := OPropertyInfo.IsReadOnly;
  EXIT(TRUE);
END;

2) Add default customization through code, the same as it is done for the default entries APP, CONT_SP, etc.

For instance, please do have a look at COD5300 triggers :

CreateDefaultContPers
CreateDefaultContComp
CreateDefaultContSp
CreateDefaultTask
CreateDefaultApp

Lines like the below one are used for inserting the fields in table 5304:

InsertOSynchField(OSynchEntity.Code,0,OSynchEntity."Table No.",OSynchEntity."Outlook Item",’BusinnessAddress’,
  FALSE,FALSE,0,2,”,0);

NOTE: any entities created before this code adjustment will have to be recreated.

This issue does not occur in Dynamics NAV 5.0 SP1.

Regards,

Marco Mels
CSS EMEA

This posting is provided "AS IS" with no warranties, and confers no rights

The post Creating new entities for the Outlook Synchronization solution results in empty synchronized entries appeared first on Microsoft Dynamics 365 Blog.

There have been many requests for some weeks if it is possible to synchronize contacts of Company type and contacts of Person type in Dynamics NAV to one single folder in Outlook. The answer is: Yes, this is possible. The question is: How should we do this? This blog posting will describe how this can be done. It is not difficult, but some steps needs to be done very careful.

First of all, ensure the Outlook Synch User Setup form is empty. To do so, follow steps below:

• Go to Administration, Application Setup, Microsoft Office Outlook Integration
• Select Outlook Synch. User Setup
• Select all rows and press F4 to delete the lines
• Press Yes to confirm deletion

Second, I would reset all demo entities to default values. To do so, follow steps below:

• Go to Administration, Application Setup, Microsoft Office Outlook Integration
• Select Outlook Synch. Entities
• Select Code and press F5
• Select CONT_SP
• Press Sync. Entity button and select Reset to defaults
• Select Microsoft Dynamics NAV Salespeople
• Press OK
• Repeat the above steps for the other entities taking the following order into account: CONT_COMP, CONT_PERS, TASK and finally repeat the steps for APP entity

Now it is time to create a new entity. To do so, follow steps below:

• Go to Administration, Application Setup, Microsoft Office Outlook Integration
• Select Outlook Synch. Entities
• Select Code and press F3
• Type a name in the Code field, e.g.: CONT_ALL
• Press Sync. Entity button and select Reset to defaults
• Select Microsoft Dynamics NAV Contacts of the Company type
• Press OK
• Select Description and remove Microsoft Dynamics NAV Contacts of the Company type
• Type in a new name, e.g.: Microsoft Dynamics NAV Contacts

Another step that needs to be done is to create the correct dependencies for the TASK entity. To do so, follow steps below:

• Go to Administration, Application Setup, Microsoft Office Outlook Integration
• Select Outlook Synch. Entities
• Select Code and press F5
• Select TASK
• Select No. of Dependencies next to the Outlook Collection Links and press F6

The following will be shown:

• Select a new line to add CONT_ALL as a new Depend. Synch. Entity Code
• Select Table Relation for CONT_ALL and press F6
• Ensure the following line is added  WHERE(No.=FIELD(Contact No.))
• Close the Outlook Synch. Entity Element Task 10000 – Outlook Synch. Dependencies form

Similar steps that need to be done are to create the correct dependencies for the APP entity. To do so, follow steps below:

• Go to Administration, Application Setup, Microsoft Office Outlook Integration
• Select Outlook Synch. Entities
• Select Code and press F5
• Select APP
• Select No. of Dependencies next to Recipients and press F6

The following will be shown:

• Select a new line to add CONT_ALL as a new Depend. Synch. Entity Code
• Select Condition for CONT_ALL and press F6
• Ensure the following line is added  WHERE(Attendee Type=CONST(Contact))
• Select Table Relation for CONT_ALL and press F6
• Ensure the following line is added  WHERE(No.=FIELD(Contact No.))
• Close the Outlook Synch. Entity Element APP 20000 – Outlook Synch. Dependencies form
• Select No. of Dependencies next to Links and press F6

The following will be shown:

• Select a new line to add CONT_ALL as a new Depend. Synch. Entity Code
• Select Condition for CONT_ALL and press F6
• Ensure the following line is added  WHERE(Attendee Type=CONST(Contact))
• Select Table Relation for CONT_ALL and press F6
• Ensure the following line is added  WHERE(No.=FIELD(Contact No.))
• Close the Outlook Synch. Entity Element APP 30000 – Outlook Synch. Dependencies form

Now, it is time to delete the original demo entities. To do so, follow steps below:

• Go to Administration, Application Setup, Microsoft Office Outlook Integration
• Select Outlook Synch. Entities
• Select Code and press F5
• Select CONT_COMP
• Press F4 to delete the entity
• Press Yes twice to confirm deletion
• Select Code and press F5
• Select CONT_PERS
• Press F4 to delete the entity
• Press Yes twice to confirm deletion

The entity list now looks like this:

Last but not least, the Outlook Synch. User Setup form will have to be filled in with correct date.

The following could be setup in Dynamics NAV:

The following could be setup in Microsoft Outlook:

Regards,

Marco Mels
CSS EMEA

This posting is provided “AS IS” with no warranties, and confers no rights

The post Synchronizing Company contacts and Person contacts to one dedicated Contacts folder using a new Outlook Synch. Entity appeared first on Microsoft Dynamics 365 Blog.