Microsoft Dynamics NAV

Team Blog

  • Microsoft Dynamics NAV Team Blog

    Integrating NAV 2009 R2 with CRM 4.0

    • 19 Comments

    With the release of NAV 2009 R2, we have endeavoured to prioritise features that many customers and partners have requested and this includes the ability to integrate NAV with CRM.

    The approach we have chosen to provide integration between NAV and CRM is to use an existing solution called the Connector for Microsoft Dynamics. This solution enables the integration of NAV 2009 R2 with CRM 4.0 online or on premise.

    As part of R2, we will provide out of the box support for synchronising common data such as customer, contact, sales order, and invoice, while also providing a means to enable synchronisation between any other standard or custom entities or fields that support specific business processes.

    Let's take a typical scenario where integration between CRM and NAV can really support a business process:

    The marketing manager uses CRM to manage her campaigns, opportunities and leads. When the leads are qualified they can be converted into a CRM Account. With integration enabled, this account subsequently becomes a customer in NAV. It's now possible for the sales team or customer service representatives to create orders in either CRM or NAV depending on their business process. The sales order will be integrated to NAV where the planning, payment processes, and shipping are handled, taking advantage of the core strengths of NAV.

    When R2 ships we will be providing as standard, integrations between the following entities:

    The Connector for Microsoft Dynamics uses web services to read and write data from CRM and NAV. It has two adapters for our solution that are designed to integrate with NAV 2009 R2 and with CRM 4.0. During configuration of the adapters, it is possible to specify which entities you want to integrate, which companies will be integrated, etc. so once the adapters are configured you can see a company-to-company integration with all the entities that you plan to integrate between the two systems.

    The entities are synchronised through the use of maps which indicate which field in NAV relates to which field in CRM. For example, Customer Name in the Customer table in NAV may relate to the Customer Name in the Account entity in CRM. The systems can be kept in synch on a schedule that works for each entity. So for example, it might be that you want to synchronise your customer information from NAV to CRM every hour but you may only want to synchronise item data from NAV to create products in CRM on a weekly basis.

    When the Connector runs, changes made to data in NAV that have been identified as data that will be integrated will trigger a field to be updated with a date/time stamp indicating that a change was made. The Connector can then query this date and look for changes via the web services since the last time the integration ran and write those changes to the destination system.

    To view a recorded version of the Hot Topic session about Integrating Microsoft Dynamics NAV 2009 R2 with CRM 4.0, see the Partner Learning Center.

    - Samantha Scott

  • Microsoft Dynamics NAV Team Blog

    Microsoft Dynamics NAV 2013 R2 Now Available

    • 19 Comments

    We are proud to announce that we have shipped Microsoft Dynamics NAV 2013 R2 and that it is now available for download. Yesterday, the announcement was made to the more than 500 partners at the sold-out Directions US event in Nashville, Tennessee. Microsoft Dynamics NAV 2013 R2 adds great new capabilities to the product such as single sign-on with Office 365 and SharePoint Online, a new UI for the Microsoft Dynamics NAV Web client and the Windows client, a new foundation for cash management, a new Help Server, and powerful provisioning and administration tools. Read the announcement on The Edge.

    Best regards,

    The NAV R&D team

  • Microsoft Dynamics NAV Team Blog

    Installing Microsoft Dynamics NAV 2013 R2 side-by-side with Microsoft Dynamics NAV 2013

    • 18 Comments

    A year after Microsoft Dynamics NAV 2013 released, we released a new version of it, Microsoft Dynamics NAV 2013 R2. They share common files, so if you install both versions on the same computer, then they will try to use the same resources, and so you run into problems. This really means that you cannot install the two versions side-by-side.

    We resolved this issue with the fix in KB 2907588 for Microsoft Dynamics NAV 2013 R2 (build number higher than 35850). But there is some manual work that you have to do to apply the fix fully.
    Microsoft Dynamics NAV 2013 and Microsoft Dynamics NAV 2013 R2 use the same Windows registry entries to describe which interface and libraries to use. With the described fix, Microsoft Dynamics NAV 2013 R2 can use new registry entries, but simply installing the hotfix does not generate the registry entries. Windows registry settings are created by installation programs, but creating a new installer for every language is out of scope for hotfix releases.

    To get Microsoft Dynamics NAV 2013 and Microsoft Dynamics NAV 2013 R2 working side-by-side, you can choose to modify some of the existing entries in the Windows registry. But the easiest way is to delete the existing registry entries and create new entries in the registry.

    Depending on the specific machine architecture, your registry settings can include the following entries:
    " HKEY_CLASSES_ROOT\TypeLib\{5020AC1E-A4F0-402B-A920-3FED4E3B05CC}\7.1"
    " HKEY_CLASSES_ROOT\Interface\{14519985-4959-4F7C-AC30-CBBCD9DFBC08}"
    " HKEY_CLASSES_ROOT \Interface\{59521B62-D441-47E6-8224-A07203686BA2}"
    " HKEY_CLASSES_ROOT \Wow6432Node\TypeLib\{5020AC1E-A4F0-402B-A920-3FED4E3B05CC}\7.1"
    " HKEY_CLASSES_ROOT \Wow6432Node\Interface\{14519985-4959-4F7C-AC30-CBBCD9DFBC08}"
    " HKEY_CLASSES_ROOT \Wow6432Node\Interface\{59521B62-D441-47E6-8224-A07203686BA2}"

    Remove the entries.

    To create new correct windows registry entries, open the Command Prompt as an administrator, and then, run the RegAsm.exe /register Microsoft.Dynamics.Nav.Client.WinForms.dll /tlb command for each of the two products.

    For example, for Microsoft Dynamics NAV 2013, enter the following command:

    C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe /register "C:\Program Files (x86)\Microsoft Dynamics NAV\70\RoleTailored Client\Microsoft.Dynamics.Nav.Client.WinForms.dll" /tlb

    And for Microsoft Dynamics NAV 2013 R2, enter the following command:
    C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe /register "C:\Program Files (x86)\Microsoft Dynamics NAV\71\RoleTailored Client\Microsoft.Dynamics.Nav.Client.WinForms.dll" /tlb

    When you have run those two commands on a 32-bit computer, the following entries exist in the registry:

    Microsoft Dynamics NAV 2013:
    HKEY_CLASSES_ROOT\Interface\{14519985-4959-4F7C-AC30-CBBCD9DFBC08} (where \TypeLib\Version == 7.0)
    HKEY_CLASSES_ROOT\TypeLib\{5020AC1E-A4F0-402B-A920-3FED4E3B05CC}\7.0

    Microsoft Dynamics NAV 2013 R2:
    HKEY_CLASSES_ROOT\Interface\{59521B62-D441-47E6-8224-A07203686BA2} (where \TypeLib\Version == 7.1)
    HKEY_CLASSES_ROOT\TypeLib\{95819FD3-CF0A-4706-BE93-35B3DDCB817C}\7.1

    And for 64-bits computers:
    Microsoft Dynamics NAV 2013:
    HKEY_CLASSES_ROOT\Interface\{14519985-4959-4F7C-AC30-CBBCD9DFBC08} (where \TypeLib\Version == 7.0)
    HKEY_CLASSES_ROOT\Wow6432Node\Interface\{14519985-4959-4F7C-AC30-CBBCD9DFBC08} (where \TypeLib\Version == 7.0)
    HKEY_CLASSES_ROOT\TypeLib\{5020AC1E-A4F0-402B-A920-3FED4E3B05CC}\7.0
    HKEY_CLASSES_ROOT\Wow6432Node\TypeLib\{5020AC1E-A4F0-402B-A920-3FED4E3B05CC}\7.0

    Microsoft Dynamics NAV 2013 R2:
    HKEY_CLASSES_ROOT\Interface\{59521B62-D441-47E6-8224-A07203686BA2}(where \TypeLib\Version == 7.1)
    HKEY_CLASSES_ROOT\Wow6432Node\Interface\{59521B62-D441-47E6-8224-A07203686BA2}(where \TypeLib\Version == 7.1)
    HKEY_CLASSES_ROOT\TypeLib\{95819FD3-CF0A-4706-BE93-35B3DDCB817C}\7.1
    HKEY_CLASSES_ROOT\Wow6432Node\TypeLib\{95819FD3-CF0A-4706-BE93-35B3DDCB817C}\7.1

    If you have applied everything correctly, then Microsoft Dynamics NAV 2013 and Microsoft Dynamics NAV 2013 R2 will now both be able to run on the computer.

    If you have only Microsoft Dynamics NAV 2013 R2 installed and any object run from dev env opens new RTC instance, then you can apply the same registry modify (related to 7.1) and issue will be resolved.

    Attached is PowerShell script does all job.
    BTW: If Microsoft Dynamics NAV 2013 R2 is installed alone, you can also use script - it will fix registries. 

     

    Best regards,

    Gedas Busniauskas and Jorge Alberto Torres from the Dynamics NAV team

  • Microsoft Dynamics NAV Team Blog

    Welcome to the Dynamics NAV Team Blog

    • 18 Comments

    Welcome to the Dynamics NAV team blog!! It is critically important for our team to be able to connect with our customers and partners at every opportunity that we can. We are committed to building great products to help you maximize your return on investment with the Dynamics NAV product.

    Sometime last year we passed the 1,000,000 user mark with Dynamics NAV. That is an amazing milestone and we can’t thank you enough for your support of the product and your feedback over the years. Our goal with this blog is to create another place where we can come even closer together as a community, where we can share what we are doing with the product, respond to your questions and concerns, and hopefully pull together around what we believe is our common goal.

    We have been able to get together with some of you at our Convergence Conferences over the years and I cannot describe how much value we have gotten from those experiences. Those countless discussions have resulted in a customer model for your businesses, it has resulted in over 60 personas for different roles in an organization, and it has resulted in one of the core themes of our next release and our role tailored client that we are rolling out across the Dynamics product line. The better we can understand your challenges and dreams the better we can help solve the challenges and make the dreams become a reality.

    Customers and Partners are always at the center of any decisions we make around the direction and functionality of our Product and as we planned for Dynamics NAV 5.0 we also used the customer model very actively, by relating the value of new features to the specific personas. By doing so we find that we as a team are able to more precisely understand and talk about the impact of new features and thereby make them even more relevant to the real users of NAV. Actually since the personas of the customer model all have been given “a name and face”, we today think and talk about our key personas as if they were old familiar members of our team to an extent that we probably wouldn’t be surprised if they one day appeared at our next team meeting in person and just greet them with a, - “Oh, hello Susan, how are you doing today!” (Susan is the name of the Order Processor in the customer model.)

    Today the Dynamics NAV community is incredibly global with over 40 language version and customers in well over 100 countries so far. This diversity provides us tremendous advantages in that we can take our learning from around the world and bring it to the rest of the world. But also means we need to have a deep understanding of what is most important for you to succeed in your local market whether you are a customer using the product, a partner selling and implementing the product, or an ISV building vertical functionality for specific markets.

    I could not be more excited to now be a part of this amazing NAV community. I thought it might be nice to give you some background on the leaders on my team. This way you can connect directly with them and I can show you that we have some very passionate, committed, and experienced people working hard every day to make your investment in Dynamics NAV the best investment you have ever made. This is just the tip of the iceberg and our goal with this blog is to have people from across our team of hundreds of developers, program managers, testers, product managers, user experience experts, content publishing writers, and more to engage with you on this forum.

    Dynamics NAV Leadership

     

    Dynamics NAV Architecture Leadership

     

    We have assembled a leadership team with decades of experience in the software industry, and also decades of experience with the Dynamics NAV product, and we are all committed along with the rest of the fantastic Dynamics NAV team to creating the best possible business solution for all of you.

    Welcome again to the Dynamics NAV team blog, this place will be become better and better if we all use it to share and come together. Thanks in advance for making this a great place to come.

    Darren Laybourn
    General Manager
    Dynamics NAV and Mobility

  • Microsoft Dynamics NAV Team Blog

    Zetadocs Express support for Microsoft Dynamics NAV 2015 is here!

    • 17 Comments

    Equisys announced today, that Zetadocs Express now supports Microsoft Dynamics NAV 2015 and the new Microsoft Dynamics NAV Tablet Client.

    Take a tablet

    Microsoft Dynamics NAV 2015 adds a new touch optimised Tablet client, introduced to improve control of the user experience on various sized tablets (7” is the minimum size really), and is the preferred client for tablets compared to the Web client in a browser.

    The Tablet client is also available as an app on Apple iTunes, Google Play and the Windows Store. Functionality between tablets is largely the same, except iPads do not allow direct access to the file system. However, with Zetadocs Express on the iPad, you can still easily capture photos with the camera or the camera roll. Other tablet operating systems allow access to the tablet file system in order to choose files and other documents on the go.

    Once captured they are then stored permanently in the electronic document archive and shown in context in the Document FactBox.

     

    Works with the Microsoft Dynamics NAV you have

     

    The Tablet client now increases the number of Microsoft Dynamics NAV clients to three; with a Web client and the traditional Windows client (RTC), and Zetadocs Express has them all covered.

     

    In fact, Zetadocs Express offers broad platform support, from the very latest version of Microsoft Dynamics NAV 2015, all the way back to Microsoft Dynamics NAV 2009 SP1 and everything in between.

     

    Proven quality with CfMD

     

    Version 7 of Zetadocs for Microsoft Dynamics NAV was one of the first software solutions worldwide to be awarded Certified for Microsoft Dynamics (CfMD) for Microsoft Dynamics NAV 2015. The Certified for Microsoft Dynamics (CfMD) logo is version specific, giving Microsoft Dynamics customers the confidence that the add-on solution they have chosen has met the comprehensive testing guidelines updated with each version of Microsoft Dynamics NAV.

     

    Download Zetadocs Express now!

     

    Zetadocs Express is a no-cost downloadable document management module for Microsoft Dynamics NAV, download it now and try out mobile document management with the Microsoft Dynamics NAV 2015 tablet client today!

     

  • Microsoft Dynamics NAV Team Blog

    Cumulative Update 5 for Microsoft Dynamics NAV 2015 has been released

    • 17 Comments

    Cumulative Update 5 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2015. 

     The cumulative update includes hotfixes that apply to all countries and hotfixes specific to the following local versions:

    •   AU - Australia
    •   AT - Austria
    •   BE - Belgium
    •   CH – Switzerland
    •   CZ – Czech Republic
    •   DE - Germany
    •   DK - Denmark
    •   ES - Spain
    •   FI  - Finland
    •   FR - France
    •   IS - Iceland
    •   IT - Italy
    •   NA - North America
    •   NL - Netherlands
    •   NO - Norway
    •   NZ - New Zealand
    •   RU – Russia
    •   SE - Sweden
    •   UK - United Kingdom

    Note: You must convert the database if you are upgrading to Cumulative Update 5 from a cumulative update earlier than Cumulative Update 4 (build 39663). For more information, see Converting a Database in Help for Microsoft Dynamics NAV. 

    Where to find Cumulative Update 5

    You can download the cumulative update from KB 3039824  – Cumulative Update 5 for Microsoft Dynamics NAV 2015 (Build 40262). 

    Additional Information

    For information about how to install the cumulative update, see How to Install a Microsoft Dynamics NAV 2015 Cumulative Update

    For information about how to work around a recent process change, see How to Get Back the 'Hotfix Directories' from NAV 2015 Cumulative Update 1.

    For a list of all cumulative updates for this version, see Released Cumulative Updates for Microsoft Dynamics NAV 2015.  

  • Microsoft Dynamics NAV Team Blog

    Cumulative Update 4 for Microsoft Dynamics NAV 2015 has been released

    • 17 Comments

    Cumulative Update 4 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2015. 

     The cumulative update includes hotfixes that apply to all countries and hotfixes specific to the following local versions:

    •   AU - Australia
    •   AT - Austria
    •   BE - Belgium
    •   CH – Switzerland
    •   CZ – Czech Republic
    •   DE - Germany
    •   DK - Denmark
    •   ES - Spain
    •   FI  - Finland
    •   FR - France
    •   IS - Iceland
    •   IT - Italy
    •   NA - North America
    •   NL - Netherlands
    •   NO - Norway
    •   NZ - New Zealand
    •   RU – Russia
    •   SE - Sweden
    •   UK - United Kingdom

    Please note that Cumulative Update 4 requires a database conversion. This is caused by the introduction of the ability to return the Microsoft Dynamics NAV Tablet client as the current client type. You will be able to read about that in the MSDN Library after we complete the monthly update of the Microsoft Dynamics NAV 2015 content there on February 11, 2015. For more information, see Updated Help Content

    Where to find Cumulative Update 4

    You can download the cumulative update from KB 3035986  – Cumulative Update 4 for Microsoft Dynamics NAV 2015 (Build 39663). 

    Additional Information

    For information about how to install the cumulative update, see How to Install a Microsoft Dynamics NAV 2015 Cumulative Update

    For information about how to work around a recent process change, see How to Get Back the 'Hotfix Directories' from NAV 2015 Cumulative Update 1.

    For a list of all cumulative updates for this version, see Released Cumulative Updates for Microsoft Dynamics NAV 2015.  

  • Microsoft Dynamics NAV Team Blog

    Cumulative Update 2 for Microsoft Dynamics NAV 2015 has been released

    • 16 Comments

    Cumulative Update 2 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2015. 

     The cumulative update includes hotfixes that apply to all countries and hotfixes specific to the following local versions:

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

    Where to find Cumulative Update 2

    You can download the cumulative update from KB 3020885  – Cumulative Update 2 for Microsoft Dynamics NAV 2015 (Build 38798). 

    Additional Information

    For information about how to install the cumulative update, see How to Install a Microsoft Dynamics NAV 2015 Cumulative Update

    For information about how to work around a recent process change, see How to Get Back the 'Hotfix Directories' from NAV 2015 Cumulative Update 1.

    For a list of all cumulative updates for this version, see Released Cumulative Updates for Microsoft Dynamics NAV 2015.  

  • Microsoft Dynamics NAV Team Blog

    How to get Microsoft Dynamics NAV for tablets to connect using a self-signed certificate

    • 16 Comments

    Overview

    This blog post helps you connect Microsoft Dynamics NAV for tablets using a self-signed certificate. The targets for the blog post are the following apps:

    • Dynamics NAV for iPad
    • Dynamics NAV for Android
    • Dynamics NAV for modern Windows

    The Internet Information Services Manager (IIS) needs a trusted certificate that holds the private key for https. iOS and Android need the https certificate to be trusted by a root certificate.

    In this blog post, you will be creating one certificate that is used for both the IIS to enable https and to install on your device. Follow the steps below and replace the following string: <your site name> with the name of the site. You can either use a real name like www.abc.com, or use your pc name. It must match the first part of the URL that you have specified. Currently the PowerShell script New-SelfSignedCertificateEx supports Windows 8 and Windows Server 2012 and newer.

    Steps

    For the Microsoft Dynamics NAV Web server, do the following:

    1. Download and save the PowerShell script from https://gallery.technet.microsoft.com/scriptcenter/Self-signed-certificate-5920a7c6#content.
    2. Create the certificate:
      1. Open a PowerShell prompt with the option As administrator.
      2. Go to the directory where you saved the New-SelfSignedCertificateEx.ps1 file.
      3. Run the following command: Import-Module .\New-SelfSignedCertificateEx.ps1.
      4. Then run the following command: New-SelfSignedCertificateEx –Subject “CN=<your site name>” –IsCA $true –Exportable –StoreLocation LocalMachine –StoreName My.
      5. Manage the certificate:
        1. Open the mmc.exe.
        2. Go to the File menu, and then choose Add/Remove Snap-in...
        3. Select Certificates.
        4. Choose Add.
        5. Select the computer account.
        6. Choose Finish and then OK.
        7. Locate and copy the certificate you just created in the personal/certificates folder.
        8. Paste the certificate into the Trusted Root Certification Authorities/Certificates folder.
        9. Select the certificate, right-click and export the certificate.
        10. Select the No, do not export the private key option.
        11. Choose Next.
        12. Select DER encoded binary x.509 (.cer).
        13. Specify a location and filename and finish the wizard.
        14. Enable https: In IIS Manager, create a binding for https using the certificate you added.

    Next

    For iOS, do the following:

    1. Use the iPhone Configuration Utility tool from Apple http://support.apple.com/downloads/#iphone or mail the certificate you exported.
    2. Run the certificate file and install the certificate.
    3. You are now ready to start the Dynamics NAV app.

    For Windows, do the following:

    1. If you run the client on the same box as the web server, then you are all set to go.
    2. Copy the certificate you exported to the tablet, install the certificate and place the certificate in the Trusted root certification authorities folder of the local machine.

    For Android, do the following:

    1. Copy or mail the certificate that you exported.
    2. Run the certificate file and install the certificate.
    3. You are now ready to start the Dynamics NAV app.

    This should help you get up and running using self-signed certificates. Be aware that Microsoft Dynamics NAV for tablets does not support Always Ask certificates.

  • Microsoft Dynamics NAV Team Blog

    Compatibility with SQL Server 2014

    • 16 Comments

    SQL Server 2014 released earlier this year with many new and interesting capabilities. For further information, please take a look at the product information at this location: http://www.microsoft.com/en-us/server-cloud/products/sql-server/default.aspx.

    Over the last few months, the Microsoft Dynamics NAV team has been testing compatibility with this new version of SQL Server, and we are now proud to announce that Microsoft Dynamics NAV 2013, Microsoft Dynamics NAV 2013 R2, Microsoft Dynamics NAV 2009 R2, and Microsoft Dynamics NAV 2009 SP1 are compatible with SQL Server 2014!

    Please note that this applies to the following editions of Microsoft SQL Server:

    • Standard Edition
    • Enterprise Edition

    Best regards,

    The Dynamics NAV team

     

    ----- This blog post was updated on September 22, 2014. -----

  • Microsoft Dynamics NAV Team Blog

    Application Test Toolset for Microsoft Dynamics NAV 2009 SP1

    • 16 Comments

    The C/AL Application Test Toolset for Microsoft Dynamics NAV 2009 SP1 is now available on PartnerSource. This toolset helps NAV developers to quickly develop and run C/AL-based tests in their primary development environment.

    The toolset includes sample tests to help you get started with C/AL test development, tools for test case management and execution, and useful test library functions, such as assert and database state restore.

    These tools build on top of the Test Features released with Microsoft Dynamics NAV 2009 SP1.

    Download from PartnerSource

  • 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

    .NET Interoperability in NAV 2009 R2

    • 15 Comments

    The greatest development platform in the world meets the greatest set of functional libraries, types, methods, and properties as Microsoft Dynamics NAV 2009 R2 allows developers to take advantage of the Microsoft .NET Framework! With NAV 2009 R2, you can reference external .NET components and make use of the Types and Functions from .NET Framework assemblies and from your own or 3rd party code.

    Being able to use .NET from C/AL code has been planned for a long time - the whole NAV Server architecture released with NAV 2009 has been building to this time where we can finally reach out from the NAV C/AL context and make use of these functions. The feature is very much part of our roadmap going forward where we want to give developers more power and allow partners to create solutions with much broader reaches than can be achieved within a native C/AL environment.

    Referencing an external component will be similar to the pattern that Automation developers are accustomed to - you can quickly choose a component from the variable declaration window and then start using the object in C/AL with full support from NAV's Symbol Menu (F5). 

    When working with variables of type DotNet, we distinguish between two sorts: Add-ins and those registered from the Global Assembly Cache (GAC). The Add-in type are those that are custom made or custom written, they do not need to be strong-named, and they may also change or are updated often. These components must be copied into a new directory (the Add-ins directory) on the developer's C/SIDE installation in order to be utilized. Variables based on types registered in the GAC are less likely to be swapped around but support strong-named types and include components like the .NET Framework. .NET Framework components have the additional benefit that they are already deployed on computers so there is no need for additional deployment!

    Rather than elaborate more on the properties and definitions, let's look at a sample. In this code sample, we will use methods from the .NET Framework to retrieve a list of processes running on the NAV Server and show the process IDs in a message box. The sample is not exactly an ERP task but shows what can now be achieved by using .NET and hopes to show that familiar code patterns can be applied.

    This screenshot shows the whole solution:

    Notice that we have declared two DotNet variables here - myproclist, which is a System.Array and holds our list of processes, and process, which is a System.Diagnotics.Process subtype. Both variables are from the .NET Framework and are thus registered in the system GAC and we don't need to worry about deploying them for when we run the code.

    Notice also that unlike Automation (based on COM), you don't always need to CREATE the objects. In DotNet, objects need to have a constructor called when they are instance-based or they may be used directly if they are static. The GetProcesses method is a static method in .NET, as we can see in the information section in our ever-helpful Symbol Menu.

    Notice also that the C/AL code is able to loop through the Array. Using arrays (be they NAV arrays or .NET System.Arrays) is such a common programming pattern that it would be very wrong of us to not include it.

    Of course using .NET is only supported on the NAV Server and, like Automation, you can also run the .NET objects either on the NAV Server or on the RoleTailored client.

    Using .NET in C/AL will open many new options - more than we can possibly imagine. We hope you'll enjoy using this feature from NAV 2009 R2 and go on to make some fantastic new solutions for all our customers!

    Good luck and happy coding!

    Stuart

    To view a recorded version of the Hot Topic session about .NET Interoperability, see the Partner Learning Center.

  • Microsoft Dynamics NAV Team Blog

    Microsoft Dynamics NAV 5.1 becomes 6.0; Delivery Date H1 of 2008 becomes H2 of 2008

    • 15 Comments

    Nobody ever wants to miss a commitment that they make, and with the move of our delivery date from H1 to H2 of 2008, that is the situation we as a Dynamics NAV R&D team find ourselves in right now.  This reality is very disappointing for all of us, and definitely not what we hoped for , but I have to say that I am as excited as I have ever been about the product we are building and I am confident that you will find that the product will definitely be worth the additional wait.

    With our next version of Dynamics NAV we are making incredible leaps forward on the user experience and technology platform of the product. It was important that the market, our partners, and our customers understand the magnitude of this advance, thus we have updated the code name for this version from 5.1 to “6.0”. It is at minimum a full version worth of progress. The advances we have made include:

    ·         We have moved the product from a two-tier architecture to a three-tier architecture dramatically increasing the integration opportunities for customers.

    ·         We have added support for web services across the board and enabled all of our ISV and partner solutions to also be web serviced enabled. The win for customers is the ability to leverage the open interface from multiple applications in their organizations.

    ·         We have transitioned our runtime execution engine from an interpreted environment to a compiled environment running on.NET. Giving customers increased performance and stability and aligning us even closer with the advances being on the Microsoft Stack.

    ·         We have transitioned our reporting story to Microsoft SQL Server Reporting Services and the incredible richness that it provides for users to gain more insight into their business.

    ·         We have added a deep integration with Office SharePoint Services making it even easier to get more people in an organization working with your business system.

    ·         Finally, and most dramatically and importantly, we’ve made a MAJOR upgrade to a new Role Tailored User Experience that our research indicates that customers will absolutely Love.

    We are accomplishing this while at the same time working to ensure that we preserve customer and partner investments. This requires a robust set of transformation tools and processes in addition to the core product advancements.

    We are introducing a lot of change and we must make sure to get it right. Why the change in date?  Well there are a few reasons:

    ·         First, we just were not tracking towards the plan we had created, and we were not going to make the planned H1 2008 date.

    ·         Second, we are closely monitoring the performance and simplicity of the new 3-tier model. As a result, we made some adjustments to our designs to increase our performance and the simplicity of our install.

    ·         Third, we’ve made a huge commitment to getting more feedback on this release before shipping.  We will provide code much earlier in the release cycle in order to maximize the feedback that we can receive and process. I will talk more about this later.

    As a result of our decision to move the date of “6.0” we decided that it would possible to pull some of the work we were doing in “6.0” forward into a Service Pack for 5.0. That work includes:

    ·         We are going to deliver Dynamics Mobile support for Dynamics NAV as part of the service pack and for Dynamics NAV 4.0. This feature will allow our partners to create mobile solutions that are occasionally connected and fully integrated with Dynamics NAV.

    ·         We brought forward a number of Microsoft SQL data access improvements. These will increase both the performance and scalability of the product.

    ·         We have added a collection of small features that have been highly requested over the years.

    ·         We have rolled up a number of the improvements and corrections that have been done since version 5.0 shipped.

    ·         We will expand the number of countries that will have version 5.0 in their markets.

    Dynamics NAV 5.0 is a great release, and with these additions it will be even better. Because of the investment we’ve made in the transition process from 5.0 to “6.0” customers and partners should not hesitate to make the move to 5.0 now.

    Earlier I mentioned that we are increasing our feedback process before we release “6.0”. Here is some of what we are planning at this point:

    ·         In November at the Directions Conference in Orlando, the entire NAV R&D leadership team will be there to do an entire day of sessions, running the current “6.0” code, discussing the transformation process, showing our new concepts, and working to gather as much input as we can. We will also provide a set of pre-recorded step by step demos of the “6.0” product that can be used to build familiarity with the product.

    ·         Also in November we will deliver a preview version of the product to 50 ISV’s who are part of our early adopter program. These partners have committed to working with the product and providing us with feedback. This drop will be of our core release.

    ·         In Q1 and Q2 of 2008 we will release updated previews to the entire partner community . These will be early availability drops and will need to be treated as such; our intent is to gather feedback on quality, performance, and any transition process issues that partners can identify.

    ·         The Q2 version will also be localized to a selected number of countries, and we will be working with a small number of partners and customers to work on transitioning their solutions onto the “6.0” product. 

    ·         The final beta will be provided in Q3 and we will deliver a version for select countries that we will use with our early adopter customers to take them live on the product. By going through the full implementation process and getting end user feedback we are confident that we will have exercised the product to the level where we can all be confident in the solution

    As a Dynamics R&D team we are extremely committed to this plan and we are doing everything we can to make sure we get feedback, react to the feedback, and deliver a high quality solution.

    The team and I are really, really, really excited about the product we are bringing your way.  I sincerely hope that this quick glimpse behind the scenes into our delivery plan increases both your confidence and anticipation of where we are taking Dynamics NAV.  With well over 1,000,000 users today Dynamics NAV is already a great product, Version 5.0, Version 5.0 SP1 and Version “6.0” are moving it forward towards and even better future. It is a ride you will most definitely want to be a part of.

    Darren Laybourn

  • Microsoft Dynamics NAV Team Blog

    Saying Farewell to the Native Database

    • 14 Comments
    I've met many people who imagine that everyone who works at Microsoft must be of a single mind, with one goal - much like a hive mentality. Nothing could be further from the truth. We are an organization of individuals, often passionate about our beliefs and very emotionally invested in the work that we do. We're very proud of our successes and we want to learn from our failures. We're very human. And as such, when I was asked to work with a team that would decouple the NAV product from our native database, it was with an element of sadness that I agreed. I can also admit that I wanted to do the job because, like many of you, I've worked with this product for over a decade and I wanted this one to happen by someone who understood what we were saying farewell to.    

    You shouldn't be burdened with the technical details about decoupling the files from our build system, generating the lists of extra dlls that we no longer need to install, or reviewing documentation that has references to the database format. When we are about to commit a huge change like this to our internal systems, we send an email to all team members informing them of an impending ‘Breaking Change' and to give teams a last chance to speak up about the impact this will have in their work cycles. There were almost no issues raised but I did receive a large number of comments from team members along the lines of "are you sure we want to take this away," "aren't we giving up the NAV simplicity," and "this is sad."  And a part of me agreed.

    But it's not really sad. The day we committed this change was a bit like the last day of High School. We've all had a fabulous time but our future is ahead.

    It's not sad because the original goal of Navision was not to become a best of breed database product - we wanted to build business applications. We happened to build a very clever little database at the same time but it was never the goal to have the database as the reason that people buy NAV.

    It's not sad because now we focus on SQL Server and we can ensure that SQL is the platform we do our enhancements on. And aim to improve performance on. And benchmark on.

    We can spare our Quality Assurance (Test) organization the pain of testing on a legacy platform and double our efforts into the SQL stack. We can spare our developers from maintaining data connections for two different platforms and spare ourselves the discussion about how to take advantage of SQL features without impacting the way the native database is used. 

    I'm looking forward to everything we can now do and I hope you will join us too.

    -Stuart Glasson

    For more information about the Statement of Direction for Microsoft Dynamics NAV where we talk about ending support for the native NAV database, see this blog post.

Page 2 of 51 (758 items) 12345»