• Microsoft Dynamics NAV Team Blog

    Update Rollups and Project Considerations for Upgrade, Maintenance and New Implementations

    • 29 Comments

    More and more partners are beginning to work with the update rollups. They find a lot of value in applying the latest application and platform fixes up front, instead of waiting for a customer to report those. Update rollups also simplify the way fixes are discovered and surfaced.

    So with this blog post, we want to provide a more detailed picture of the update rollups, their purpose, and their usage scenarios so that you are aware of the rollup release process and components, and so that more of you start using them. We would also like to provide our look at how to adopt and use the update rollups within various stages of the implementation project lifecycle.

    What is an update rollup?

    Update rollups are released monthly for Microsoft Dynamics NAV 2013 and Microsoft Dynamics NAV 2013 R2: 

    Released update rollups for Microsoft Dynamics NAV 2013 R2

    Released update rollups for Microsoft Dynamics NAV 2013

    An update rollup is a set of files that includes all hotfixes (application and platform) and regulatory features that have been released for the versions of Microsoft Dynamics NAV that are listed above. 

    They are cumulative, meaning that they include hotfixes and regulatory features that were released in the earlier update rollups for the specific product version.

    Each rollup contains the following:

    • Accumulated application change log (TXT format) compared to the originally release of the specific product version (the RTM release).
    • Application change log (TXT format) compared to the previous rollup - the “delta”.
    • Only the application objects that changed since the RTM version are included in the FOB and TXT files provided with the rollup.
    • Each application object is marked with rollup version number (version number + build number) to make it possible to see which objects have been changed in which rollup.
    • The latest version of all (not only the changed ones) platform components (executables and .dll assemblies). These components are also stamped with a version number and a build number.

    Application changes:

    Platform components:

    Hotfixes that are included in the update rollups do not always include translation. In that case, the translation for such changes are provided with the next RTM version of  Microsoft Dynamics NAV (major releases or minor release). Regulatory features included in the rollup are almost always translated; however, in rare cases the translation is provided with the following monthly update rollup.   

    Update rollups are currently released for 10 countries: Australia, Germany, Denmark, France, Italy, North America (Canada, US, Mexico), Netherlands, New Zealand, Sweden, United Kingdom.

    Local hotfixes for the following countries are currently not included in update rollups: Austria, Belgium, Switzerland, Spain, Finland, India, Iceland, Norway.

    Scenarios

    Maintenance. Applying rollups for the countries/regions where they are available.

    If you have a version of the running application for which you would like to apply the update rollup, you can follow this high level flow:

    • Find the latest rollup available for your application version here:
    • See the KB article for the UR to find the full list of application and platform changes as well as regulatory updates included in it. The list is divided by country/region. For instance, here are the KB articles for the latest available rollups:
    • Based on the urgency and relevance of the application and platform changes, current project stage, customer situation and other surrounding factors decide whether you want to apply the UR now, or wait for the next one. We strongly recommend that you always apply the latest UR to gradually reduce the amount of regressions, merging, issues and to be compliant with the latest regulatory requirements. 
    • If you are on the RTM version merge your application objects with all objects included with the latest rollup.
    • If you are on the URn version – filter out the objects which were changed since URn till the latest available UR and merge your application objects with those objects. You can use the Version List field to see in which rollup (build) they were changed. 

    Maintenance. Applying hotfixes for the countries where update rollups are not available.

    For these cases the process of applying the hotfixes and regulatory updates is the same as it was before the UR concept was introduced, namely the changes relevant to all countries/regions (W1 changes) should be applied one by one.

    However, URs can aid this process as well as you can obtain all W1 changes by downloading the latest W1 UR and merge them into your country version. You can find W1 URs by clicking at “Show additional information” and looking at their Fix Name which you can see when you download the UR:

    Platform components are country independent, therefore the platform updates can also be obtained from W1 UR and deployed for any country/region-specific version of Microsoft Dynamics NAV.

    Major releases, minor releases, and update rollups

    URs are different from the major and minor releases. Every major and minor release contains new application and platform features and functionality as well as hotfixes, while the URs only contain hotfixes and regulatory updates. So when a major release or minor release has been released, we create a new branch for the next release and continue to maintain both branches.

    Let’s dissect the process based on the Microsoft Dynamics NAV 2013 version as an example (see the illustration below).

    When Microsoft Dynamics NAV 2013 version was released, we created a new branch for Microsoft Dynamics NAV 2013 R2 development. As we’ve been building Microsoft Dynamics NAV 2013 R2 functionality, we kept fixing Microsoft Dynamics NAV 2013 and kept releasing URs for it.

    Relevant fixes from the Microsoft Dynamics NAV 2013 version were merged into the Microsoft Dynamics NAV 2013 R2 version in the course of its development. In many cases they had to be redesigned to fit the new code and new functionality of Microsoft Dynamics NAV 2013 R2.

    Therefore, when Microsoft Dynamics NAV 2013 R2 was released, not all fixes included in the latest available Microsoft Dynamics NAV 2013 UR were included in it. The process of finding and merging relevant fixes into the latest branch is a continuous process, and there will be a certain lead time until the fixes from the releases are synchronized between branches. So, for instance, the majority of the fixes which were available in Microsoft Dynamics NAV 2013 UR7 were included into Microsoft Dynamics NAV 2013 R2 UR1, and the process of merging of relevant fixes will go on.

    When considering upgrade or a new implementation of the new major release or minor release, we recommend that you always upgrade to (or start from) the latest available UR for it. If there is a particular hotfix which is available in the previous version of Microsoft Dynamics NAV, but it not yet available in the latest release, you can always request it to be merged there using the normal support process “How to create a new support case”.  It is also always possible to only update the platform components with the updated ones coming from a corresponding UR (technical upgrade), although the best practice would be to keep the application objects updated to the latest UR as well.

    Microsoft Dynamics NAV 2013 R2 hotfixes are also periodically merged into Microsoft Dynamics NAV 2013 and will be eventually available in the upcoming URs. Similarly, if there is a particular hotfix which is available in the current version of Microsoft Dynamics NAV, but it not yet available in the previous release, you can also request it to be merged there using the same support process “How to create a new support case”. 

    We will continue to release URs for the Microsoft Dynamics NAV 2013 release and future releases periodically, synchronizing relevant fixes between them over time.

    Microsoft Dynamics NAV 2009 SP1 and Microsoft Dynamics NAV 2009 R2 are maintained following the old process - you can request hotfixes on case by case basis, no update rollups available for those product versions. 

    The following timeline illustrates the process.

     

    Conclusion

    It is highly recommended to implement the update rollups. We look forward to hearing your feedback and suggestions to how this process could be made more convenient for you to assess and absorb the changes.

     

    Kind regards,

    Microsoft Dynamics NAV Team

     

    Updated on January 16, 2014: We removed two sentences that were misleading around the upgrade rollups and the Upgrade Toolkit. We apologize for the confusion.

  • Microsoft Dynamics NAV Team Blog

    Delivering more choice with Zetadocs Express

    • 0 Comments

    Equisys has released a new version of Zetadocs Express for Microsoft Dynamics NAV that not only supports Microsoft Dynamics NAV 2013 R2, but also includes the ability for customers to archive documents to network folders on their file servers.

    Connects people to documents

    For those that don’t know, Zetadocs Express provides the ability to send Microsoft Dynamics NAV reports by email.  It also enables you to use ‘drag and drop’ to store any document, such as an invoice from a supplier, alongside its corresponding Microsoft Dynamics NAV record. These documents can be retrieved via the Document FactBox in Microsoft Dynamics NAV, or from the document archive by business users without Microsoft Dynamics NAV.

    The new release allows customers to store these documents in SharePoint Online, SharePoint Server or network folders on your file server. Customers not ready to deploy SharePoint can use network folders initially and then switch to SharePoint later for advanced search features and filtered views.

    Windows 8.1, Windows Server 2012 R2 and Microsoft Dynamics NAV 2013 R2

    There’s also more platform choice with support for Windows 8.1, Windows Server 2012 R2, and Microsoft Dynamics NAV 2013 R2 Windows client. A future update will add support for the Microsoft Dynamics NAV 2013 R2 Web client. You can see a brief preview video of this on YouTube

    Download Zetadocs Express

    Zetadocs Express is the foundation member of the Zetadocs for NAV document management family. It is available at no additional cost to Microsoft Dynamics NAV 2013 & Microsoft Dynamics NAV 2009 customers on a Business Ready Enhancement Plan.

    The new version of Zetadocs Express can be downloaded from CustomerSource, PartnerSource and the Zetadocs website.

  • Microsoft Dynamics NAV Team Blog

    Convergence 2014 Customer Excellence Awards Nominations – Last Call!

    • 0 Comments

    Evangelize successful Microsoft Dynamics NAV customers at Convergence 2014! Check out the details and submission process for Customer Excellence Awards here:

    http://www.microsoft.com/dynamics/convergence/atlanta14/Customer-Excellence.aspx.

    Customer Excellence Awards recognize, honor, and celebrate customer organizations that are achieving outstanding success with their Microsoft solutions. In each award category, finalists and, subsequently, award winners, will be chosen on their ability to provide amazing experiences for their customers through the use of their Microsoft Dynamics solution. Nominations will be closing January 13.

  • Microsoft Dynamics NAV Team Blog

    Now Available: New How Do I Videos for Microsoft Dynamics NAV 2013 R2 on MSDN

    • 2 Comments

    Check out the latest videos on the Microsoft Dynamics NAV Developer Center. We've added to the How Do I Series to support the latest release: http://msdn.microsoft.com/en-us/dynamics/nav/dn524022

    These videos target the developer audience for Microsoft Dynamics NAV. Here is a sampling of the more than 20 titles that have been released to help you get started with Microsoft Dynamics NAV 2013 R2:

    • How Do I: Do Full SQL Tracing for Microsoft Dynamics NAV 2013 R2
    • How Do I: Use the Debugger in Microsoft Dynamics NAV 2013 R2
    • How Do I: Get Started with Windows PowerShell for Microsoft Dynamics NAV 2013 R2
    • How Do I: Migrate from Multiple Companies to a Multi-tenant Architecture in Microsoft Dynamics NAV 2013 R2

    More videos are in the works and will target both the platform and the application, so check back often to see what’s been added. All videos are in English.

     

  • Microsoft Dynamics NAV Team Blog

    Update Rollup 2 for Microsoft Dynamics NAV 2013 R2 has been released

    • 3 Comments

    Update rollup 2 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2013 R2 and includes hotfixes that apply to all countries and hotfixes specific to the following local versions:

    • AU – Australia
    • DE - Germany
    • DK - Denmark
    • FR - France
    • IT - Italy
    • NA – North America
    • NL – Netherlands
    • NZ – New Zealand
    • SE - Sweden
    • UK - United Kingdom

    Also, update rollup 2 includes Cumulative Update 1 for Microsoft Dynamics NAV 2013 R2.

    Where to find update rollup 2

    You can download update rollup 2 from KB 2913982 - Update Rollup 2 for Microsoft Dynamics NAV 2013 R2 (Build 35800).

    The hotfixes that have been released since update rollup 1 are listed in KB 2913982. For a full list of all hotfixes included in the update rollup, see the following CustomerSource and PartnerSource pages:

    CustomerSource:

    PartnerSource

     

    More Information

    For more information about update rollups for Microsoft Dynamics NAV 2013 R2, see Announcement of update rollups for Microsoft Dynamics NAV 2013 R2.

  • Microsoft Dynamics NAV Team Blog

    Microsoft Visual Studio 2013 Now Supported for RDLC Report Design

    • 1 Comments

    We are happy to announce that we have added support for using Microsoft Visual Studio 2013 (Professional, Premium, and Ultimate editions) to create and modify RDLC reports. This lets you use the latest version of Microsoft Visual Studio when designing reports for Microsoft Dynamics NAV 2013 R2.

    To enable Microsoft Visual Studio 2013 support, you must install the hotfix from the Knowledge Base article 2907585. After the hotfix is installed, when you design reports from the Microsoft Dynamics NAV Development Environment, Microsoft Visual Studio 2013 is automatically used if it is available on the computer running the development environment; otherwise, Microsoft Visual Studio 2012 is used if it is available. There is no option to choose which version of Microsoft Visual Studio to use if both Microsoft Visual Studio 2013 and Microsoft Visual Studio 2012 are installed on the development environment computer. With regard to editing RDLC reports for Microsoft Dynamics 2013 R2, there is no functional difference between using Microsoft Visual Studio 2012 or Microsoft Visual Studio 2013, and RDLC reports that are edited with Microsoft Visual Studio 2013 can be edited later with Microsoft Visual Studio 2012 if needed.

     

    Best regards,

    the Microsoft Dynamics NAV team

  • Microsoft Dynamics NAV Team Blog

    How to: Set up your Microsoft Dynamics NAV installation for Single Sign-on with Office 365 using Windows PowerShell

    • 0 Comments

    // Copyright © Microsoft Corporation. All Rights Reserved.

    // This code released under the terms of the

    // Microsoft Public License (MS-PL, http://opensource.org/licenses/ms-pl.html.)

    In our blog post How to: Validate that Microsoft Dynamics NAV 2013 R2 is correctly configured to support Single Sign-on with Office 365, we presented the Microsoft Dynamics NAV Best Practices Analyzer, a tool that you can use in order to validate your single sign-on (SSO) configuration of Microsoft Dynamics NAV. Not only does it validate your Microsoft Dynamics NAV and Windows Azure Active Directory (WAAD) configuration, it has another big advantage of assisting you in setting up your environment for SSO by providing meaningful and suggestive error messages which help you build your way through this lengthy process. The entire list of steps needed for setting up SSO with Office 365 in Microsoft Dynamics NAV is completely described in this how-to video

    In the previous paragraph I have just mentioned that this is a “lengthy process” which many times can become a rather unpleasant troubleshooting experience. We have collected this feedback and addressed this problem by providing the system administrators willing to set this environment up with a powerful Windows PowerShell cmdlet.

    This cmdlet is called Set-NavSingleSignOnWithOffice365 and it can completely automate the process of configuring your Microsoft Dynamics NAV Web Client to support SSO with Office 365. For more information on the usage of this cmdlet and all the possible scenarios where its power can be leveraged, refer to the official Microsoft Dynamics NAV Help topic, which will be released with the next MSDN Library refresh: Walkthrough: Setting up your Microsoft Dynamics NAV installation for Single Sign-on with Office 365 using Windows PowerShell.

    Note: The cmdlet can fully automate the configuration process provided that the needed parameters are specified when executing it. Generating and importing the security certificates that secure the Client – Server communication channel is performed separately and is subject to another upcoming topic with the next MSDN Library refresh: How to: Create a Self-signed Security Certificate Using PowerShell Script.

    In the following section, you will find information about setting up your Microsoft Dynamics NAV installation for single sign-on with Office 365 using Windows PowerShell.

    Setting up your Microsoft Dynamics NAV Installation for Single Sign-on with Office 365 using Windows PowerShell

    Microsoft Dynamics NAV supports federated user authentication with Windows Azure Active Directory (Windows Azure AD). This is the Identity Provider service used by Office 365. As a matter of fact, every time a new Office 365 subscription is provisioned, the Windows Azure AD tenant for this subscription is also created. Thus, when Microsoft Dynamics NAV is configured for federated authentication with a WAAD tenant, a single sign-on (SSO) user experience is achieved between Microsoft Dynamics NAV and the Office 365 Web Applications and any other applications that leverage the single sign-on capability provided by the Windows Azure AD tenant. 

    The Set-NavSingleSignOnWithOffice365 cmdlet can help you perform this configuration task by automating all the steps of this process. To sum up, this cmdlet performs the following operations: 

    1. It first validates that both your Microsoft Dynamics NAV Server and Microsoft Dynamics NAV Web Server are ready for this change. 
    2. It validates that your Office 365 credentials are valid.
    3. Once the validation steps are performed, the cmdlet starts the configuration:
      1. It links your Microsoft Dynamics NAV User account to your Office 365 account by providing your Office 365 email address as the AuthenticationEmail for the Microsoft Dynamics NAV User account.
      2. It configures the Microsoft Dynamics NAV Server by changing the values of the following configuration settings: ClientServicesFederationMetadataLocation, ClientServicesCredentialType and ServicesCertificateThumbprint.
      3. It configures the Microsoft Dynamics NAV Web Server by changing the values for the following configuration settings: ClientServicesCredentialType, ACSUri and DnsIdentity.
      4. It configures the WAAD tenant by creating a Service Principal that represents the Microsoft Dynamics NAV Web Client.
    4. If any of the configuration sub-steps of step 3 fail, the cmdlet reverts all the changes made to your Microsoft Dynamics NAV Server and Web Server up until that point. 

    Prerequisites

    • Office 365 subscription
      If you already have your Office 365 subscription, you can ignore this step. Otherwise, sign up for a free trial Office 365 plan. We recommend that you use a plan such as Office 365 Enterprise E1 as your test site, or that you sign up for a trial developer plan. A trial plan includes an administrative account whose credentials you will need to provide for the WAAD configuration. For example, if your Office 365 site is Solutions.onmicrosoft.com, your administrative account can be admin@solutions.onmicrosoft.com. For more information, see Select an Office 365 plan for business.
    • Azure Active Directory Tenant Management Components
      The cmdlet relies on the presence of the following components on your system:

      Microsoft Online Services Sign-In Assistant for IT Professionals

      Windows Azure Active Directory Module for Windows PowerShell

      You can download and install these components from the links provided above. If you have to choose between 32-bit and 64-bit versions of components, then download the version that matches your Windows Operating System type. To determine the operating system type, open File Explorer, and then choose This PC in the navigation pane. On the ribbon, in the System group, choose System properties. The operating system type appears next to System type in the System section.
    • Microsoft Dynamics NAV user account
      You have to  have a valid NAV user account. For more information, see How to: Create Microsoft Dynamics NAV Users in the MSDN Library.
    • Microsoft Dynamics NAV environment
      Setting up SSO requires that you have both the Microsoft Dynamics NAV Server and Web Server installed. 
    • Security Certificate Used to Secure the Server – Web Server Communication Channel
      Setting up user authentication types other than Windows for the Microsoft Dynamics NAV environment requires securing the Server – Client (or Web Server in this case) communication. This can be done using a security certificate. The Set-NavSingleSignOnWithOffice365 cmdlet assumes that you have already imported the security certificate in your certificate store. You can either use a security certificate issued by a trusted certificate authority (see Walkthrough: Implementing Security Certificates in a Test Environment) or you can use a self-signed certificate (see How to: Configure User Authentication for the Microsoft Dynamics NAV Web Client). The latter approach is not recommended in a production environment; however, it is an alternative to consider when testing your environment.

    Importing the Automated Configuration Module 

    In order to run the Set-NavSingleSignOnWithOffice365 cmdlet, you first need to open Windows PowerShell as an administrator. This can be done by right-clicking on the Windows PowerShell program and choosing “Run as administrator”.

    Then navigate to your Microsoft Dynamics NAV DVD, then to the WindowsPowerShellScripts\ NAVOffice365Administration folder. 

    Next, run the following cmdlet in order to import the NAVOffice365Administration PowerShell module:

    Import-Module .\NAVOffice365Administration.psm1 

    Automating the Single Sign-on Configuration in a One-Computer Microsoft Dynamics NAV Environment

    Once the prerequisites are fulfilled and the Office 365 Administration module is imported, the sufficient condition for setting up SSO with Office 365 is satisfied by simply running the Set-NavSingleSignOnWithOffice365 cmdlet with the following parameter set on the computer that hosts the Microsoft Dynamics NAV components:

    Set-NavSingleSignOnWithOffice365-NavServerInstance “ServerInstanceName” -NavWebServerInstanceName “WebServerInstanceName” -NavUser “YourNavUser” -AuthenticationEmail “YourOffice365Email” -NavServerCertificateThumbprint “SecurityCertificateThumbprint”

    ServerInstanceName represents the name of your Microsoft Dynamics NAV Server instance. You can find the names for the Microsoft Dynamics NAV Server instances running on your computer by running the Get-NAVServerInstance cmdlet.

    WebServerInstanceName represents the name of your Microsoft Dynamics NAV Web Server instance. You can find the names for the Microsoft Dynamics NAV Web Server instances running in your IIS by running the Get-NAVWebServerInstance cmdlet. 

    YourNavUser represents the name of your NAV User account.

    YourOffice365Email represents the email address of your Office 365 User account. It is in the form username@o365tenant.onmicrosoft.com. This user should have administrative privileges.

    SecurityCertificateThumbprint represents the thumbprint for the security certificate used for securing the Client – Server communication channel. For more information, refer to the “Prerequisites” section of this article. You can get the list of thumbprints for your certificates by issuing this Windows PowerShell command:

     Get-ChildItem -Path "Cert:\LocalMachine\My"

    Note: You can avoid providing this parameter if you already have your Microsoft Dynamics NAV Server configured with a security certificate. This applies to Microsoft Dynamics NAV installations in the Windows Azure environment, and other environments where any credential type other than Windows is active and functional.

    Once the Set-NavSingleSignOnWithOffice365 cmdlet is run, a dialog box will open, requesting your Office 365 account user name and password. 

    Automating the Single Sign-on Configuration in a Multi-Computer Microsoft Dynamics NAV Environment

    This configuration type assumes that your Microsoft Dynamics NAV Server and Web Server are on different computers. This means that you need to run the Set-NavSingleSignOnWithOffice365 cmdlet on each of these computers separately with a different parameter set in order to correctly configure your Microsoft Dynamics NAV Web Client for SSO with Office 365.

    Running the cmdlet on the Microsoft Dynamics NAV Server computer 

    To configure your Microsoft Dynamics NAV Server for SSO, you need to run the cmdlet with the following parameter set:

    Set-NavSingleSignOnWithOffice365-NavServerInstance “ServerInstanceName” -NavUser “YourNavUser” -NavServerCertificateThumbprint “SecurityCertificateThumbprint” -SkipWebServerConfiguration

    Notice the SkipWebServerConfiguration switch, which specifies that the Microsoft Dynamics NAV Web Server components should not be configured at all.  

    Running the cmdlet on the Microsoft Dynamics NAV Web Server computer

    To configure your Microsoft Dynamics NAV Web Server for SSO, you need to run the cmdlet with the following parameter set:

    Set-NavSingleSignOnWithOffice365-NavWebServerInstanceName “WebServerInstanceName” -AuthenticationEmail “YourOffice365Email” -SkipNavServerConfiguration

    Notice the SkipNavServerConfiguration switch, which specifies that the Microsoft Dynamics NAV Server should not be configured at all.  

    Additional Remarks and Considerations 

    Running the cmdlet fails because the NAV Server fails to start / restart

    You can find more information about the Microsoft Dynamics NAV Server failure reason in the event log. This error most likely occurs because of the impossibility of the Microsoft Dynamics NAV Server to properly configure the ACL for the ports used by the server’s communication endpoints. In some situations, when there are URLACL entries for the same ports but reserved by other services (including other installed Microsoft Dynamics NAV Servers), the removal procedure fails because of insufficient privileges. The user account running the Microsoft Dynamics NAV Server needs to have administrative permissions for the modification of the URLACL to succeed. That is why, in order to overcome this issue, you can try one of the following:

    1. Remove the URL ACL entries manually (see Walkthrough: Configuring Web Services to Use SSL (SOAP and OData) for more information) or
    2. Set your Microsoft Dynamics NAV Service to run as on Administrator account on your computer.

    Running the cmdlet in a multitenant Microsoft Dynamics NAV environment 

    Only one tenant can be automatically configured at a time, so the Microsoft Dynamics NAV Tenant name needs to be provided as the NavTenant parameter to the Set-NavSingleSignOnWithOffice365 cmdlet.

    Avoiding the Office 365 Credentials dialog box

    You can fully automate the script, and thus avoid the Office 365 Credentials dialog box by providing the credentials as parameters:

    You use the AuthenticationEmail parameter to specify the Office 365 account email and the AuthenticationEmailPassword parameter to specify the Office 365 account password. Be aware that the latter parameter should be a SecureString.  

    Running the cmdlet for a Microsoft Dynamics NAV Web Server that is hosted in complex network topology

    Setting the trust relationship between the Microsoft Dynamics NAV Web Client and Windows Azure AD requires specifying a remote endpoint for the Microsoft Dynamics NAV Web Client in the Windows Azure AD Service Principal that is created for this web application.

    If the Microsoft Dynamics NAV Web Server runs behind a DNS or another network component that changes / rewrites the Web Client’s address, the Set-NavSingleSignOnWithOffice365 cmdlet is not able to compute this address, since it only runs on the local computer. 

    You can overcome this situation by providing the cmdlet the address as seen remotely for your Microsoft Dynamics NAV Web Client. The parameter you need to pass this address to is NavWebAddress.

     

    Best regards

    The Microsoft Dynamics NAV Office 365 team.

  • Microsoft Dynamics NAV Team Blog

    Validating Single Sign-on with Office 365 and Microsoft Dynamics NAV 2013 R2

    • 5 Comments

    // Copyright © Microsoft Corporation. All Rights Reserved.

    // This code released under the terms of the

    // Microsoft Public License (MS-PL, http://opensource.org/licenses/ms-pl.html.)

    How to: Validate that Microsoft Dynamics NAV 2013 R2 is correctly configured to support Single Sign-on with Office 365

    In Microsoft Dynamics NAV 2013 R2, we introduce the ability to set up single sign-on (SSO) between an Office 365 account and a Microsoft Dynamics NAV 2013 R2 account. More precisely, the Office 365 user account is linked to a Microsoft Dynamics NAV 2013 R2 user account.

    Implementing SSO requires that you correctly set up various elements, including a Windows Azure account for managing the Windows Azure Active Directory (Windows Azure AD) tenant, the Microsoft Dynamics NAV Server, and the Microsoft Dynamics NAV Web Server.

    As part of a hotfix for Microsoft Dynamics NAV 2013 R2, we have provided an extension to the Best Practices Analyzer (BPA) tool. The extension can be used to validate the setup for your single sign-on application. The approach is as follows: you provide a simple set of parameters, and then the tool validates the setup to see whether it is correct for single sign-on. 

    About this blog post

    This blog post describes the principles of single sign-on between Office 365 and Microsoft Dynamics NAV 2013 R2. It provides a short introduction to setting up SSO, information about how to use the BPA tool for validation, and a list of resources for additional information, including videos and Help documentation.

    The elements of the Single Sign-On functionality

    The authentication for SSO is handled by three parties. It is based on the first party being Office 365, the second being Microsoft Dynamics NAV 2013 R2 and the third party being the Windows Azure Active Directory (Windows Azure AD) service. Microsoft Dynamics NAV 2013 R2 trusts Windows Azure AD and Office 365 trusts Windows Azure AD, however, Microsoft Dynamics NAV 2013 R2 and Office 365 do not trust each other.

    The Windows Azure AD is the identity management service for Office 365. The credentials that you use to sign in to Office 365 are the same credentials that you use to sign in to the Windows Azure Management Portal (http://manage.windowsazure.com). By definition, Office 365 trusts Windows Azure AD and if Microsoft Dynamics NAV 2013 R2 trusts Windows Azure AD, we indirectly establish a trust between Microsoft Dynamics NAV 2013 R2 and Office 365 by letting Windows Azure AD provide its trust to Office 365 to Microsoft Dynamics NAV 2013 R2. This is done in the following way:

    To start with, we need to get the federation metadata from Windows Azure AD specifically for the given Office 365 subscription. An Office 365 subscription is an Office 365 account, which is sometimes referred to as an Office 365 tenant. We also need to let Windows Azure AD know about the Microsoft Dynamics NAV Web Server address. After providing the right information to Windows Azure AD, it knows enough about the Microsoft Dynamics NAV Web Server, but now Microsoft Dynamics NAV Web Server and Microsoft Dynamics NAV Server need to know about Office 365 and Windows Azure AD.

    Microsoft Dynamics 2013 R2 is based on a multi-tier architecture. This architecture consists of an SQL Server, Microsoft Dynamics NAV Server, and the Microsoft Dynamics NAV Web Server. For SSO, we do not have to configure anything special on the SQL Server but we do need to modify both the Microsoft Dynamics NAV Server instance and the Microsoft Dynamics NAV Web Server instance configuration. The Microsoft Dynamics NAV Server must be configured to run in the credential type AccessControlService, and it must also know the URL for Windows Azure AD for retrieving the federation metadata. The Microsoft Dynamics NAV Web Server, which is hosted by Internet Information Services (IIS), must be configured to run in the credential type AccessControlService, and it must also know the path to the Windows Azure AD authentication endpoint. The final configuration setting is that each Office 365 email account has to be mapped to each user in Microsoft Dynamics NAV that is expected to use SSO.

    For more details, see the references in the Appendix section. 

    The Best Practices Analyzer tool

    With Microsoft Dynamics NAV 2013, we introduced the Best Practices Analyzer (BPA) to analyze the configuration of Microsoft Dynamics NAV Server and SQL Server in order to determine whether these components are configured correctly or not. In Microsoft Dynamics NAV 2013 R2, we have extended the BPA to include an analysis of the SSO configuration.

    The BPA tool can be used by copying the BPA folder from the Microsoft Dynamics NAV 2013 R2 installation media (DVD) to your computer or by running the tool directly from the DVD. (Note: The DVD must be newer than November 25, 2013 – hotfix number 35727.) To run the BPA tool, we recommend that you copy the files to a local folder (if you do not need to use the Helper files you can run the tool from the DVD), enable Desktop Services, and then choose “Run As Administrator”.

    To proceed with the BPA tool, we assume the following:

    1. You have a Microsoft Dynamics NAV Web Client running.
      • You know the URL of the Microsoft Dynamics NAV Web Client.
      • You know the name of the Microsoft Dynamics NAV Server.
    2. You have an Office 365 account (SMB SKU or higher - see http://office.microsoft.com for information on options for business).
      • You have the administrator credentials for your Office 365 account.
      • You know the domain for your Office 365 account, such as mysolution.onmicrosoft.com, where your email can be admin@mysolution.onmicrosoft.com.
      • You are familiar with signing in and out of Office 365.

     The BPA tool includes several steps that perform the analysis of your configuration. The following figure shows the Start a new Best Practices scan screen. The new analysis for SSO is enabled by choosing Yes for the “Would you like to verify that the environment is configured for Single Sign-On with Office 365”? option.

    The parameters that you can set are described in the following table:

    Field

    Description

    Example

     Active Directory Server

    This is automatically determined and is optional.

      

     Server Instance Name

     This specifies the name of the Microsoft Dynamics NAV Server instance, which can be found under Services on the computer. In the example, the Server Instance Name is “DynamicsNAV71”

     

     

     It is also specified in the Microsoft Management Console:

     

     Web Server Instance Name

    This specifies the name of the web server instance for the Microsoft Dynamics NAV 2013 R2 Web Client, which can be found in Internet Information Service (IIS) Manager.

    In the example, the web server instance name is the name of the virtual folder under Microsoft Dynamics NAV 2013 R2 Web Client.

     

     Microsoft Dynamics NAV Tenant

    This is only needed in a multitenant environment – the value “default” is the name of the first and only tenant in a single tenant configuration

     

     Office 365 User Account Email 

    This is the user name for Office 365 (and Windows Azure AD). This looks similar to admin@myO365.onmicrosoft.com.

     

    When you have filled out the parameters, you choose Start scanning. Shortly after, you will get a request for the password for your Office 365 account so that the BPA tool can connect to your Windows Azure AD tenant in order to verify your configuration:

    Within half a minute or so, the Scanning Completed message appears.

    You then choose View a report of this Best Practices scan. (You can only see List reports if you have not enabled Desktop Services. Otherwise use Tree reports.)

    The tool shows a number of errors. If you choose the first error in the list, then more details and some guidance are shown.

    If you choose Tell me more about this issue and how to resolve it, then the documentation will open, where you can see even more guidance on what you need to do in order to fix the problems.

    You can also see this information in the Tree Reports.

    As you can see, this tool can be really helpful when you need to get through the configuration of SSO. You can keep the BPA tool open as you resolve problems, and once you are done, you can choose to scan again to see whether issues are resolved.

    As a final check, verify that the SSO actually works. If it is the first time that you sign in, the credentials are needed.

    Final remarks

    With this extension to the BPA, we hope that you will have an easier time validating that Microsoft Dynamics NAV is correctly set up for single sign-on with Office 365. To get a better understanding, take a look at the references provided in the appendix.

    Appendix

    References to videos 

    How Do I: Enable Single Sign-On with Office 365 in Microsoft Dynamics NAV 2013 R2 is available on MSDN and in the Microsoft Dynamics NAV Community.

    More information about Windows Azure Active Directory 

    Windows Azure Active Directory

    Manage Windows Azure AD using Windows PowerShell

    More information about Microsoft Dynamics NAV 2013 R2

    Authenticate Users with Windows Azure Active Directory

    Users and Credential Types

    Configuring Microsoft Dynamics NAV Web Client by Modifying the web.config File

    How to: Configure User Authentication for the Microsoft Dynamics NAV Web Client

    Configuring Microsoft Dynamics NAV Server

    How to: Configure the Microsoft Dynamics NAV Web Client for ACS

    More information about certificates

    Test environment

    Production environment

     

    Best regards

    Eric Beran, Mike Borg Cardona, Vlad Precup, Steffen Balslev, and John Swymer - Microsoft Dynamics NAV Office 365 team.

  • Microsoft Dynamics NAV Team Blog

    New NAV Design Patterns

    • 0 Comments

    The NAV Design Patterns Wiki site was announced in November, as a repository containing the first NAV design pattern descriptions, together with a call for contributions.

    We would like to say “welcome to the team”, to our new design patterns authors. Their patterns are linked below. If you want to learn from the experience of other Microsoft Dynamics NAV partners and from some of the designs they have implemented or used, then read on.

    Posting Routine - Select behaviour

    By waldo at ifacto

    Meet the Pattern

    Send information (parameters) to a processing framework/routine so that it knows what to do, how to behave, .. .

    Know the Pattern

    For a processing routine to behave correctly, it needs sometimes input of a user to know what it has to do, check or avoid doing.  To do this, usually a piece of UI is getting called (STRMENU) with the question what to do. These input needs to get to the routine.

    Continue reading on the NAV Patterns Wiki...

    Conditional Cascading Update

    by Jan Hoek at IDYN 

    Meet the Pattern

    The Conditional Cascading Update pattern is used to intelligently populate fields whose values depend on other field values. In this pattern description, the field triggering the update will be called “source field”, and the depending field will be called “target field”. 

    Know the Pattern

    The value of one table field sometimes depends on the value of another field, typically following an application-defined transformation (note that we're talking about transformations of field values here. This has nothing to do with e.g. form transformation), such as conversion to uppercase, removal of certain characters etc.

    If the target field is non-editable, ...

    Read more about Conditional Cascading Update on the Wiki...

    Setup Specificity Fallback

    by Jan Hoek at IDYN 

    Meet the Pattern

    The Setup Specificity Fallback pattern allows users to efficiently define a potentially complex setup in terms of rules and exceptions to these rules, exceptions to the exceptions, etc.

    Know the Pattern

    The pattern involves a setup table with a compound (i.e. consisting of more than one field) primary key, where each record in the table maps a combination of primary key values to a particular setup value. However, setting up and maintaining each and every combination could prove to be rather labour-intensive.

    Read more on the NAV Design Patterns Wiki...

     

    With best regards from the NAV Design Patterns team.

  • Microsoft Dynamics NAV Team Blog

    Update Rollup 9 for Microsoft Dynamics NAV 2013 has been released

    • 0 Comments

    Update rollup 9 for Microsoft Dynamics NAV 2013 (Build 35782) has been released.

    Update rollup 9 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2013 and includes hotfixes that apply to all countries and hotfixes specific to the following local versions:

    • AU - Australia
    • DE - Germany
    • DK - Denmark
    • FR - France
    • IT   - Italy
    • NA - North America
    • NL - Netherlands
    • NZ - New Zealand
    • SE - Sweden
    • UK - United Kingdom

    Where to find update rollup 9

    You can download update rollup 9 from KB 2913980 - Update Rollup 9 for Microsoft Dynamics NAV 2013 (Build 35782).

    The hotfixes that have been released since update rollup 8 are listed in KB 2913980. For a full list of all hotfixes included in the update rollup, see the following CustomerSource and PartnerSource pages:

    CustomerSource:

    PartnerSource:

    More Information

    For more information about update rollups for Microsoft Dynamics NAV 2013, see Announcement of new hotfix process for Microsoft Dynamics NAV 2013.

  • Microsoft Dynamics NAV Team Blog

    Announcement of update rollups for Microsoft Dynamics NAV 2013 R2

    • 6 Comments

    Update rollup 1 for Microsoft Dynamics NAV 2013 R2 has been released.

    What is an update rollup

    An update rollup is a cumulative set of files that includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2013 R2, including hotfixes and regulatory features released in previous update rollups.

    Where to find update rollups

    You can download update rollup 1 from KB 2901573- Update Rollup 1 for Microsoft Dynamics NAV 2013 R2 (Build 35701). The hotfixes that are included in this update rollup are listed in the KB article.

    You can find a list of all update rollups released for Microsoft Dynamics NAV 2013 R2 in KB 2914930 - Released update rollups for Microsoft Dynamics NAV 2013 R2.

    You can find a list of all hotfixes included in update rollups for Microsoft Dynamics NAV 2013 R2 on the following CustomerSource and PartnerSource pages:

    CustomerSource

    PartnerSource

    Which countries are included in the update rollups

    Update rollups for Microsoft Dynamics NAV 2013 R2 includes hotfixes that apply to all countries (W1) and local hotfixes for the following countries:

    • AU - Australia
    • AT - Austria (first included in Update Rollup 5) 
    • BE - Belgium (first included in Update Rollup 5) 
    • CH - Switzerland (first included in Update Rollup 5) 
    • DE - Germany
    • DK - Denmark
    • ES - Spain (first included in Update Rollup 5) 
    • FI - Finland (first included in Update Rollup 5) 
    • FR - France
    • IS – Iceland (first included in Update Rollup 5) 
    • IT – Italy
    • NA – North America
    • NL – Netherlands
    • NO - Norway (first included in Update Rollup 5) 
    • NZ - New Zealand
    • SE - Sweden
    • UK – United Kingdom

    Weekly platform rollups

    To ensure early access to platform hotfixes, weekly platform rollups will be released between monthly update rollups.

    Access to update rollups

    Please note that a CustomerSource or PartnerSource login is required to access the update rollups and all links in this blog post.

  • Microsoft Dynamics NAV Team Blog

    Hotfix overview pages for Microsoft Dynamics NAV 2013 R2 now available

    • 0 Comments

    Overview pages of released platform hotfixes and application hotfixes for Microsoft Dynamics NAV 2013 R2 are now available on PartnerSource and CustomerSource at the following links:

    PartnerSource:

    CustomerSource:

    ==================================================================================== 

    Hotfix overview pages for Microsoft Dynamics NAV 2013 can be found here:

    PartnerSource:

    CustomerSource:

     ==================================================================================== 

     Hotfix overview pages for Microsoft Dynamics NAV 2009 SP1/R2 and Microsoft Dynamics NAV 5.0 SP1 can be found here:

    PartnerSource:

     CustomerSource:

     

    Please note that a CustomerSource or PartnerSource login is required to access the links in this blog post. 

  • Microsoft Dynamics NAV Team Blog

    Update Rollup 8 for Microsoft Dynamics NAV 2013 has been released

    • 0 Comments

    Update rollup 8 for Microsoft Dynamics NAV 2013 (Build 35670) has been released.

    Update rollup 8 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2013. Local hotfixes for Sweden have been added to update rollup 8 and the update rollups now include hotfixes that apply to all countries and hotfixes specific to the following local versions:

    • AU – Australia
    • DE - Germany
    • DK - Denmark
    • FR - France
    • IT - Italy
    • NA – North America
    • NL – Netherlands
    • NZ – New Zealand
    • SE – Sweden (NEW)
    • UK - United Kingdom

    Where to find update rollup 8

    You can download update rollup 8 from KB 2901572 - Update Rollup 8 for Microsoft Dynamics NAV 2013 (Build 35670).

    The hotfixes that have been released since update rollup 7 are listed in KB 2901572. For a full list of all hotfixes included in the update rollup, see the following CustomerSource and PartnerSource pages:

    CustomerSource:

    PartnerSource:

    More Information

    For more information about update rollups for Microsoft Dynamics NAV 2013, see Announcement of new hotfix process for Microsoft Dynamics NAV 2013.

     

  • Microsoft Dynamics NAV Team Blog

    Announcing Microsoft Dynamics NAV 2013 R2 Cumulative Update 1

    • 16 Comments

    We are happy to announce that the Cash Management team has shipped Microsoft Dynamics NAV 2013 R2 Cumulative Update 1. The cumulative update is available for download on PartnerSource/CustomerSource.

    The cumulative update is an application update only. It mainly contains Cash Management features, such as:

    • UI for the Data Exchange Framework
    • Import of SEPA CAMT bank statements in W1 (all countries can use it) and in NL and BE in integration with existing localizations
    • SEPA Direct Debit in FR, IT, ES, BE, and CH in integration with existing localizations

    As a new service, Microsoft Dynamics NAV 2013 R2 Cumulative Update 1 contains the "CU1Help" folder with selected topics for W1 and six country versions that have changed since Microsoft Dynamics NAV 2013 R2. The Help content is in English language only.

    For more information about features in the cumulative update, see What’s New in Microsoft Dynamics 2013 R2 Cumulative Update 1, which is available from the download page or the country-specific What's New topics in the "CU1Help" folder.

    To learn about known issues, of which the first has a prerequisite hotfix, see Release Notes for Microsoft Dynamics 2013 R2 Cumulative Update 1, which is available from the download page.

    To follow installation steps and steps required to use the Data Exchange Framework and to update Help, see How to Update to Microsoft Dynamics 2013 R2 Cumulative Update 1, which is available from the download page. 

    To help customers and partners get an overview of SEPA functionality released in different countries during the calendar year 2013, we have released the “SEPA Functionality in Microsoft Dynamics NAV” white paper on the Getting Ready site for Microsoft Dynamics NAV 2013 R2 on PartnerSource/CustomerSource.

    Note: The product downloads, Help download, and links to supporting documents are presented in a separate section for Microsoft Dynamics NAV 2013 R2 Cumulative Update 1 on the download page on PartnerSource/CustomerSource.

  • Microsoft Dynamics NAV Team Blog

    Upgrade Toolkit for Upgrading Data from Microsoft Dynamics NAV 2009 R2 and Microsoft Dynamics NAV 2009 SP1 to Microsoft Dynamics NAV 2013 R2

    • 44 Comments

    The components needed to upgrade data directly from Microsoft Dynamics NAV 2009 R2 to Microsoft Dynamics NAV 2013 R2 are now available for download.

    Download the upgrade toolkit from PartnerSource or from CustomerSource

    In order to use the toolkit to upgrade data from Microsoft Dynamics 2009 R2 or Microsoft Dynamics NAV 2009 SP1, you will also need the Microsoft Dynamics NAV 2013 development environment and Microsoft Dynamics NAV 2013 R2.

    At the Directions EMEA conference in Vienna and the Directions US conference in Nashville, we said that we have a team that is focusing on the Microsoft Dynamics NAV upgrade story. Going through the big transformation from the classic stack to the new product architecture in Microsoft Dynamics NAV 2009 was not easy and is challenging many customers and partners. So for our team, it is essential that the final outcome of our work is that each upgrade is easier, requires significantly less effort, and that it does not disrupt the daily business for our customers.

    In Microsoft Dynamics NAV 2013 R2, we introduced support for converting a Microsoft Dynamics NAV 2013 database so that you can run an application that was created in Microsoft Dynamics NAV 2013 on the Microsoft Dynamics NAV 2013 R2 platform, also known as a technical upgrade.

    Note: We strongly recommend that you upgrade the application objects as well so that your solution includes the important application fixes and new functionality that is introduced in Microsoft Dynamics NAV 2013 R2.

    Secondly, you can fully automate the data upgrade process using the Windows PowerShell scripts that we included in the Microsoft Dynamics NAV 2013 R2 product media. Historically, this process has been known for its tediousness and high risk of human error when multiple operations had to be executed consecutively in all companies of the database that you were upgrading. The scripts automate this work so that you can test and execute your data upgrades more reliably.

    Now with this delivery, we introduce an upgrade toolkit for upgrading the data from Microsoft Dynamics NAV 2009 R2 to Microsoft Dynamics NAV 2013 R2. This significantly simplifies the upgrade process for those of you coming from Microsoft Dynamics NAV 2009 R2 – or Microsoft Dynamics NAV 2009 SP1.

    Included in the new upgrade toolkit are all known data upgrade-related application hotfixes that we are aware of, and we also addressed several platform issues that affected the upgrade scenario.

    Note: You must download the latest Microsoft Dynamics NAV platform hotfixes before you start using the upgrade toolkit. The required hotfixes for Microsoft Dynamics NAV 2013 are available in the latest hotfix rollup, which you can download from PartnerSource or CustomerSource. For Microsoft Dynamics NAV 2013 R2, you can download the required hotfixes from PartnerSource or CustomerSource.

    When you download the new upgrade toolkit from the link above, you can use it to simply your upgrade process. Here are the main steps in upgrading from Microsoft Dynamics NAV 2009 R2 (or Microsoft Dynamics NAV 2009 SP1) by using the new upgrade toolkit.

    Note

    Before you start, make sure that you use the latest platform binaries for all versions of Microsoft Dynamics NAV in this process. For more information, see the following pages for the latest updates to the versions of Microsoft Dynamics NAV:

    Microsoft Dynamics NAV 2009 R2: Overview of Released Platform Hotfixes for Microsoft Dynamics NAV 2009 SP1 and Microsoft Dynamics NAV 2009 R2.

    Microsoft Dynamics NAV 2013: Released Cumulative Updates for Microsoft Dynamics NAV 2013.

    Microsoft Dynamics NAV 2013 R2: Released Cumulative Updates for Microsoft Dynamics NAV 2013 R2.

    To upgrade data from a Microsoft Dynamics NAV 2009 R2 or Microsoft Dynamics NAV 2009 SP1 database

    1. In the Microsoft Dynamics NAV  2009 R2 or Microsoft Dynamics NAV  2009 SP1 development environment (Classic client):
      1. Make sure that all table objects have compiled successfully. During compilation, Microsoft Dynamics NAV generates or regenerates the BLOB content in the Object Metadata table that is used in the later steps.  In the Tools menu, choose Build Server Application Objects.
        Note: You must also do this if you upgrade from Microsoft Dynamics NAV 2013 to Microsoft Dynamics NAV 2013 R2 . All tables must be compiled Microsoft Dynamics in NAV 2013 before you start upgrading to Microsoft Dynamics NAV 2013 R2.
      2. Create a copy or a backup of your old Microsoft Dynamics NAV 2009 R2 database, and open it in the Microsoft Dynamics NAV 2009 R2 development environment.
      3. Add your partner license to the database.
        You can do this by selecting the Save License in Database field in the Alter Database window. If the field was not already selected, a dialog box opens so you can specify the location of your partner license.
        If the field was already selected, upload the partner license from the License Information window.
      4. Open the Object Designer, and then import Upgrade601701.1.fob. If the .fob file contains objects with conflicting versions that are already in the database, the Import Worksheet window opens. Choose Replace All.
      5. For each company in the database, open the company, and make the relevant changes to data. For more information, see Task 3: Data/Object Changes Prior to Step 1 in the MSDN Library.
    2. Then, from the Object Designer, run form 104001, Upgrade - Old Version. Choose the Transfer Data button. Repeat this action for each company in the database. 
      Note
      We strongly recommend that you back up the database using SQL Server management tools after this step. 
    3. When you have transferred all data for all companies, in the Upgrade - Old Version window, choose the Delete Objects button.
      This action deletes all objects in the database that are not tables, but also obsolete tables that belong to functionality that is not available in Microsoft Dynamics NAV 2013 R2.
    4. Uninstall Microsoft Dynamics NAV 2009 R2, and then install Microsoft Dynamics NAV 2013.
      Note
      You do not have to install the full Microsoft Dynamics NAV 2013 product to perform the following database conversion. Instead, you can create a folder with the following files from the Microsoft Dynamics NAV 2013 product media:
      • Finsql.exe
      • Fin.stx
      • Fin.etx
      • CRONUS.FLF
      • Ndbcs.dll

      You can then use the Finsql.exe file to perform the conversion.  

    5. Change the compatibility level of your database. For SQL Server 2008 and SQL Server 2008 R2, verify that the compatibility level of the database is set to 100. For SQL Server 2012, set the compatibility level to 110.
    6. In the Microsoft Dynamics NAV 2013 development environment, open the Microsoft Dynamics NAV 2009 R2 database and agree to convert the database. The database has now been technically upgraded to Microsoft Dynamics NAV 2013.

      Note 
      During this step, Microsoft Dynamics NAV converts all text and code fields to Unicode format by changing their SQL Server data type. This conversion requires more disk space than usual, since both the database and the log file will grow in size considerably. It can also be a lengthy process.

      If your Microsoft Dynamics NAV 2009 R2 database is using SQL Server Collation, within the same step the collation will be changed to a suitable Windows collation. This is because Microsoft Dynamics NAV 2013 and higher versions only support Windows Collation. If you converted your database using the RTM version of Microsoft Dynamics NAV 2013, you may be experiencing collation-related issues after this conversion. Therefore it is strongly recommended to use the latest available version of Microsoft Dynamics NAV 2013 development environment to perform this step.

      Note
      We strongly recommend that you take a full SQL Server backup at this stage when the database conversion has completed.

    7. Uninstall Microsoft Dynamics NAV 2013, and then install Microsoft Dynamics NAV 2013 R2.
    8. In the Microsoft Dynamics NAV 2013 R2 development environment:
      1. Open the Microsoft Dynamics NAV 2013 database and agree to convert the database.
      2. Compile the system tables. You can find the tables by setting a filter for table ID 2000000004..2000000130.
        In the following step, you will be connecting a Microsoft Dynamics NAV Server instance to the database. 
    9. Make sure that the service account that the Microsoft Dynamics NAV Server instance uses has the db_owner role for the database. 

      Note 
      If you are upgrading a large database, such as a database size of more than 20-25 GB, make sure that you increase the timeout value in the Microsoft Dynamics NAV Server configuration file. In the CustomSettings.config file, the value is defined in the SQL Command Timeout node. The default value is 10 minutes, which is sufficient in the normal day-to-day work. However, during an upgrade that can take several hours depending on the size of the tables, you must increase the timeout period.

    10. Connect the Microsoft Dynamics NAV Server instance to the database, and then start the service instance.
    11. In the Microsoft Dynamics NAV 2013 R2 development environment:
      1. On the Tools menu, open Options, and then, make sure that the Prevent data loss from table changes field is set to Yes.You must also make sure that the Server Name, Server Instance, and Server Port fields are filled in.
        This ensures that the Microsoft Dynamics NAV Server instance that is connected to the database will verify that no operation will cause loss of data in the development environment.
      2. Import all customized objects in .fob format into the upgraded database. If the .fob file contains objects with conflicting versions that are already in the database, the Import Worksheet window opens. Choose Replace All.
      3. Make sure all objects are compiled.

        Important
        It is very important that at least all table objects have successfully compiled before you proceed.

      4. Import Upgrade Step 2 objects from the Upgrade601701.2.fob file.If the .fob file contains objects with conflicting versions that are already in the database, the Import Worksheet window opens. Choose Replace All.
    12. Perform the database schema synchronization by running the Sync-NAVTenant Windows PowerShell cmdlet in the Microsoft Dynamics NAV 2013 R2 Administration Shell (run as administrator).

      Note
      When you upgrade from one version to another, this typically involves numerous changes in the structure of the Microsoft Dynamics NAV tables (the object metadata). Database synchronization ensures that these changes in the metadata are applied to the corresponding tables in SQL Server. For example, it changes columns dimensions and data types, drops and create indices, drops and creates indexed views (V-SIFT), creates new tables, columns, and so on.

      When the number of changes is high, such as comparing Microsoft Dynamics NAV 2009 R2 to Microsoft Dynamics NAV 2013 R2, this synchronization can become a lengthy and resource consuming task.

      Database synchronization is triggered upon any request to Microsoft Dynamics NAV Server, such as when you start a client or run a windows Powershell cmdlet. Microsoft Dynamics NAV Server checks if metadata has changed since the last synchronization by comparing the content of the Object Metadata and Object Metadata Snapshot system tables. If a change is found, the synchronization procedure is initiated.  

      When the synchronization process has started, it is essential that you wait for it to complete or rollback (in case of an error or time-out). If you’re running a client, do not confirm or click anything client side. If you’re running the Sync-NAVTenant cmdlet, wait for it to complete and return control to the Windows PowerShell command prompt.

      Do NOT stop the Microsoft Dynamics NAV Server service at this point since there are high chances that the database synchronization transaction is still running.

      1. Run Microsoft Dynamics NAV 2013 R2 Administration Shell as Administrator. This opens a PowerShell prompt where the Microsoft Dynamics NAV cmdlets are available.

      2. Run the synchronization command against your upgrade database as follows: 

        Sync-NAVTenant –ServerInstance <MyNAVServerInstance> 

      3. Wait until the cmdlet returns control to the Windows PowerShell window.

    13. Open the Microsoft Dynamics NAV 2013 R2 Windows client to verify that you are connected to the Microsoft Dynamics NAV Server instance that is connected to the database being upgraded. 
      Next, you will run Upgrade Step 2 in each company in the upgraded database. You can get a list of all existing companies in the database by running the Get-NAVCompany cmdlet and passing as an argument the Microsoft Dynamics NAV Server instance which is connected to the upgraded database. 
      You will run objects directly from the development environment, so you must specify the company that the objects must run in in the Options window.
    14. In the Microsoft Dynamics NAV 2013 R2 development environment:
      1. On the Tools menu, open Options, and then, in the Company field, specify the name of the first company.
      2. In the Object Designer, find page 104002 Upgrade - New Version, and then choose Run.
      3. In the Upgrade - New Version window, choose Test Database Connection to make sure that the C/AL code that is triggered by the actions on the page has access to the database.
        If your database is on a named SQL Server instance, you must specify the full name in the SQL Server Name field.  
      4. Choose Transfer Data.
        If the process is successful, and you don't have to revisit the upgrade logs, you can clean the content of the Upgrade Time Log  table. 
      5. On the Navigate tab, choose Time Log, and then, in the Upgrade Time Log page, delete all records.
      6. Close the Upgrade - New Version window, and then close the Microsoft Dynamics NAV Windows client.
    15. Repeat step 14 for each remaining company in the database.
    16. When you have successfully transferred data in the last company, you must upgrade data that is common to all companies in the database, such as permissions, permission sets, web services, profiles and control add-ins.
    17. Upgrade data common to all companies such as permissions, permission sets, web services, profiles and control add-ins.
      If the customer has changed the Read/Write/Modify/Delete/Execute settings for any of the standard permissions, or customized default permission sets in any way, you must merge these changes into the default permissions sets and permissions that are included in Microsoft Dynamics NAV 2013 R2. You can use XMLport 104001 Import/Export Roles and XMLport 104002 Import/Export Permissions to export the new default roles and permissions from the CRONUS International Ltd. demonstration database in Microsoft Dynamics NAV 2013 R2. You can add control add-ins in the Control Add-ins window in the Microsoft Dynamics NAV Windows client. For more information, see How to: Register a Windows Client Control Add-in. For example, the following client control add-ins are available from the Microsoft Dynamics NAV 2013 R2 product media:
      • Microsoft.Dynamics.Nav.Client.BusinessChart
      • Microsoft.Dynamics.Nav.Client.PageReady
      • Microsoft.Dynamics.Nav.Client.PingPong
      • Microsoft.Dynamics.Nav.Client.VideoPlayer
    18. Delete the upgrade toolkit objects.
      1. In the Upgrade - New Version window, choose Mark/Delete Upgrade Toolkit.
        This deletes all upgrade toolkit objects, except tables
      2. In the Microsoft Dynamics NAV development environment, delete the upgrade tables by setting a field filter for objects where the Version List contains Upgrade Toolkit Table - marked for deletion.

    The database has now been through a data upgrade to Microsoft Dynamics NAV 2013 R2.

    Best regards,

    The Microsoft Dynamics NAV Service Experience team

    -----Blog post updated in May 2014-----

     

Page 4 of 43 (637 items) «23456»