• Microsoft Dynamics NAV Team Blog

    Modifying the Microsoft Dynamics NAV 2013 R2 Installation Program to Include Microsoft.Dynamics.Nav.Client.WinForms.tlb

    • 6 Comments

    With NAV 2013 R2 Update Rollup 3, in the process of build sealing, it has been changed the Library GUID used to register Microsoft.Dynamics.Nav.Client.WinForms.tlb.

    Accordingly to this previous blog post: Installing Microsoft Dynamics NAV 2013 R2 Side-by-Side with Microsoft Dynamics NAV 2013, the TypeLib GUID has been changed from the RTM value of {5020AC1E-A4F0-402B-A920-3FED4E3B05CC} to {95819FD3-CF0A-4706-BE93-35B3DDCB817C}.

    Due to this change, if you try to patch a Microsoft Dynamics  NAV 2013 R2 DVD with the latest platform hotfix from Update Rollup 3, you will probably receive an error from the Setup.exe that is related to a missing registration of this TypeLib during the installation of the Microsoft Dynamics NAV Windows client.

     

    In order to successfully deploy a new DVD that is fully patched with the latest platform hotfixes, we at the NAV core team could create a new client MSI file for every localized version that we have released for Microsoft Dynamics NAV 2013 R2 and include this into the hotfix stack, or we could create a new hotfix package that only contains a specific, country-/region specific MSI file.

    Since this does not follow the normal hotfix sealing procedure and the effort to put through is consistent, the recommended best practices is to deploy Microsoft Dynamics NAV 2013 R2 based on the installation program in the original release and then fully patch the installation afterwards with the platform hotfixes.

    However, you can choose to change the MSI file TypeLib value using an MSI editor. Microsoft provides a set of Windows Installer Development Tools for free. We recommend that you use the Orca.exe tool that is part of the Windows Installer Development Tools. If you download the tools, you can install Orca.exe from the following location:

    On an x86 computer:  \Program Files (x86)\Microsoft SDKs\Windows\v7.0\Bin\Orca.msi

    On an x64 computer: \Program Files\Microsoft SDKs\Windows\v7.0\Bin\Orca.msi

    Once you have installed Orca.exe, to edit the Microsoft Dynamics NAV client components MSI file, follow the following steps:

    1. Run Orca.exe.
    2. Choose File, and then choose Open.
    3. Browse to the Role Tailored Client folder in your copy of the Microsoft Dynamics NAV 2013 R2 DVD to locate and open the Microsoft Dynamics NAV RoleTailored Client.msi file.
    4. When the file is opened, in the left pane, under Tables, choose the TypeLib entry as illustrated in the following screenshot.

    5. In the row that refers to Microsoft.Dynamics.Nav.Client.WinForms.tlb , in the LibId field, change the value to {95819FD3-CF0A-4706-BE93-35B3DDCB817C}.
    6. Choose the Save button. The following screenshot illustrates the result of your modification:
       
    7. Close Orca.exe.

    Now you can replace the Microsoft Dynamics NAV RoleTailored Client.msi file that is in the Role Tailored Client folder on your copy of the Microsoft Dynamics NAV 2013 R2 DVD with this modified file.

     

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

     

    Duilio Tacconi (dtacconi)          &             Marco Mels (mmels)

    Microsoft Dynamics Italy                        Microsoft Dynamics Netherlands

    Microsoft Customer Service and Support (CSS) EMEA

  • Microsoft Dynamics NAV Team Blog

    RDLC Report and Performance in Microsoft Dynamics NAV

    • 9 Comments

    It has been a while since I last blogged and I am taking the chance now to post on a very delicate argument. The main focus of my dissertation is about performance (Out Of Memory exception, typically) with Microsoft Dynamics NAV 2009 R2, Microsoft Dynamics NAV 2013, and Microsoft Dynamics NAV 2013 R2.

    I would encourage you to post your comments and thoughts. Have a good read.

    Microsoft Dynamics NAV 2009 R2 Considerations (RDLC 2005 - Report Viewer 2008)

    All the Microsoft Dynamics NAV 2009 stack (RTM, SP1, R2) is built and sealed for the x86 platform. This means that both client (Microsoft.Dynamics.NAV.Client.exe) and server (Microsoft.Dynamics.NAV.Server.exe) are 32bit components of the NAV platform. RDLC Reporting (Enhanced Reporting, in the recent NAV terminology) in Microsoft Dynamics NAV 2009 is made of a Report Viewer .NET Control targeted for WinForm, and Microsoft Dynamics NAV casts this control into a Microsoft Dynamics NAV modal page (that is a WinForm, roughly speaking) within the RTC boundaries.

    Report Viewer works, in principle, accepting 2 items:

    -          a metadata definition plain XML file (Report.rdlc) that define the structure of the report rendering runtime  

    -          a Dataset that is a serialized XML file that contains the data to be rendered in the way defined in the rdlc file definition

    With Microsoft Dynamics NAV 2009, Report Viewer works client-side to render the report to the user (Preview Layout rendering extension) and therefore it needs to have both RDLC definition and dataset streamed completely from the Server to the Client. This streaming process of Client memory population, since Microsoft Dynamics NAV 2009 SP1, is made with a chunking method that can be resumed in shorts as per below.

    SQL Server process and generate a complete Result Set. The Result Set is sent to the Microsoft Dynamics NAV Server as normal TCP packets informations and the Microsoft Dynamics NAV Server, meanwhile receiving these packets from SQL Server, is sending this Result Set in chunks to the client, clearing the Microsoft Dynamics NAV Server memory once the packet is received from the client. This has been introduced to avoid memory leak server side that works only as routing point for packets / chunks from SQL Server to the Microsoft Dynamics NAV Windows client. If you open task manager both in the Middle Tier machine and Client machine, meanwhile processing a Heavy report (or whatever report), you might notice that the memory footprint server side is constant and pretty low while the Client one is growing and growing in consumption until it reaches a physical limit.

    When it reaches its physical limit, you receive the typical error message like the one shown below (explicit Out Of Memory exception)

    And, most of the times, report viewer continue clearing the error message and simply display a single blank page (implicit Out Of Memory exception) or several pages with mixed random string value assignments (blurred Out of Memory exception).

    I do not want to go more deep into the technicalities that lies beneath but you have to consider the following:

    1. The Microsoft Dynamics NAV 2009 R2 Role Tailored client is a 32bit application (with a limit, on the chart, of 2GB memory per process).
    2. The Microsoft Dynamics NAV 2009 R2 Role Tailored client and report(s) share the same memory Application Domain (this means the same memory stack).
    3. Report Viewer control run in a sort of sandbox mode inside the Microsoft Dynamics NAV WinForm so that the memory consumption is even more limited (approx. 1GB).

    Based on the assumption above my studies on performance related to heavy reports have been the following:

    1. Report Viewer Preview rendering extension within Role Tailored Client is raising an Out Of Memory exception when Client process memory reaches 0.8 – 1.1 GB approx. (this differs between multiple factors like e.g. OS, Hardware type, Resources, etc.)
    2. Considering a typical Microsoft Dynamics NAV dataset (60 – 80 columns on average) there is a potential risk of Out Of Memory between 40K up to 100K rows range. This depends on number of columns in the dataset and quality of columns (e.g. which data type they belongs, if and how this is populated, etc.).

    If you pack up all these considerations, these are the actions that you might take (or have to) depending on your scenarios within the Microsoft Dynamics NAV 2009 R2 stack:

    1. If your report is raising an Out Of Memory exception in a range lower or close to 80/90K rows then you can try to optimize the report by reducing the Dataset. Reducing the dataset means :
      1. Write optimal code for RDLC Report (e.g. use CurrReport.SKIP when needed, avoid use data items for CALCSUMS and use record AL variables instead, rewrite the report to use drill-through to enable getting to details if required in the report - so still possible to move calculations to CSIDE – or refactor to use hyperlink to another report for details, etc.)
      2. Reduce the Dataset Columns (e.g. eliminate Section control that you do not use with RDLC report)
      3. Reduce the Dataset Rows (refactor as much as it possible to push in the dataset only the data that need to be printed)
    2. If your report is already in a range equal or higher then 80/90K then you have no other choices with NAV 2009 R2 than the following :
      1. Delete RDLC Report layout and enable Classic Client report fall back (this is the solution that I will warmly suggest and it is a really finger snap solution)
      2. (this is pretty obvious) Apply filters in the request page (or through AL Code) in order to reduce the amount of rows in the dataset and instead of print the report in one single shot, print it N times.

    And this is all about the Microsoft Dynamics NAV 2009 R2 stack and how to solve / workaround the problem in the feasible (and easiest way) within this version.

    Microsoft Dynamics NAV 2013 (RDLC 2008 – Report Viewer 2010) / NAV 2013 R2 (RDLC 2010 – Report Viewer 2012) is another story and challenge type.

    To resume, the milestone changes between Microsoft Dynamics NAV 2009 and Microsoft Dynamics NAV 2013 (and R2) are the following:

    1. Microsoft Dynamics NAV Server is now 64bit (finally…) while the Windows client still remains as 32bit application. This means that the client is still a physical bottleneck and are still valid the considerations related to memory footprint and dataset volume as reported previously for Microsoft Dynamics NAV 2009 R2.
    2. You cannot anymore enable Classic client report fallback but you have to use RDLC Report in any occasion.

    With these 2 new variables or constraints in mind, below how you could workaround / resolve the performance problem with Microsoft DynamicsNAV 2013  / Microsoft Dynamics NAV 2013 R2:

    1. Same considerations about Optimizing reports: if you receive (or think of receiving) an Out Of Memory exception you might go for optimize the report as much as you can IF you forecast that in the end your dataset will never ever exceed 70/90K rows.
    2. If you have heavy reports with a dataset volume higher than 70/90K rows then this is what you could do:
      1. Filter data and print the report N times, wherever possible (use common sense)
      2. Use the Job Queue to enable Server Side Printing. What is Server Side Printing? It is simply running Report Viewer totally in the background through NAS Services (that is using Background Sessions through STARTSESSION AL statement). Running Server Side means running under 64 bits context and therefore Report Viewer (“.NET component targeted for any CPU” = 64 bit enabled) will use ALL the memory available from the OS (e.g. if you have 32 GB it could reach up to consume all of these if you have to work with several MILLION of dataset rows – I have seen it with my own Italian eyes - ) and you will succeed in PRINT the report or, better, use SAVEASPDF to generate a PDF file to be consumed by the user.
      3. Use STARTSESSION AL statement as you like in your own custom code after gathering user filters and parameter and pass this to a Codeunit that does filter record(s) and run a SAVEASPDF in the background as per your exotic flavor.

    THE FUTURE

    The Microsoft Dynamics NAV Core team is fully aware about these scenarios and working hard on improving the RDLC Report performance and experience in future versions of Microsoft Dynamics NAV

    NOTE:

    In this blog post you will find a set of objects (1 Report, 1 Codeunit, 1 Page) to easily simulate an Out Of Memory exception or Save as PDF the report in background.

    Just import these NAV object set and run Page 50666. You can choose to simulate an Out Of Memory exception by clicking the appropriate Action and then Preview the Report or you can choose to SAVEASPDF the same Report via enabling a Background Session that would do this action Server Side. 

    Be sure to have at least 4 GB of Available Memory Server Side and just wait for the background session to end its activity and stream out the content of the report (this should take close to 5/6 minutes with a standard Cronus database, depending on resources).

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

    Duilio Tacconi (dtacconi)

    Microsoft Dynamics Italy

    Microsoft Customer Service and Support (CSS) EMEA

    A special thanks to Peter Borring Sørensen & Torben Wind Meyhoff from the Microsoft Dynamics NAV core team.

  • Microsoft Dynamics NAV Team Blog

    Coming Soon: Exporting and Importing Companies and Other Data

    • 11 Comments

    We are not quite ready yet, but we will soon announce the availability of new functionality for Microsoft Dynamics NAV 2013 R2: The ability to export business data, global data, and/or applications from one database and import the data into another database. Many of you used the FBK functionality to do this in earlier versions of Microsoft Dynamics NAV, but since we removed that backup/restore functionality in Microsoft Dynamics NAV 2013 R2, you have let us know how much you relied on it in your daily work. So we are working hard on this new functionality, and we will make an announcement when you can download the update.

    When the update is available, we will also update the Microsoft Dynamics NAV 2013 R2 Release Notes Follow-Up document, which is available here: https://mbs.microsoft.com/downloads/customer/NAV/NAV%202013%20R2/MicrosoftDynamicsNAV2013R2_ReleaseNotesFollowup.pdf

    Best regards,

    The Dynamics NAV team

  • Microsoft Dynamics NAV Team Blog

    SAVEASWORD and the Fixed Header design

    • 0 Comments

    Microsoft Dynamics NAV 2013 and Microsoft Dynamics NAV 2013 R2 implement a new rendering extension and give users the capability of saving the report into Word .DOC (NAV 2013) or .DOCX (NAV 2013 R2) format. The same action can be done through C/SIDE by using the SAVEASWORD C/AL statement.  For more information, see the MSDN Library:  http://msdn.microsoft.com/en-us/library/hh165802(v=nav.71).aspx

    However, the Report Viewer Word rendering engine has some caveats related to its own proper design that you should be aware of.

    When you are invoking the Word rendering engine, the Header and Footer are transformed into static Word Header and static Word Footer. The SSRS team took the basic Header / Footer Word concept to have these as static sections. Therefore the FIRST statement generated in report viewer is the one that will be sent to the Word document, no further processing will be made typically to the value expression of any control in Page Header / Page Footer. In other words, it is like saying that all the ReportItems!Field.value or Code.Function() in Page Header or Page Footer are evaluated only one time and never changed at runtime.

    Let's illustrate the challenge with the Word rendering engine and how it handles Page Header and Page Footer within the context of Microsoft Dynamics NAV. I am using the following to demonstrate this behavior in few seconds:

    1. Open the Microsoft Dynamics NAV 2013 or Microsoft Dynamics NAV 2013 R2 Windows client.
    2. Go to Posted Documents (in the navigation pane).
    3. Go to Posted Sales Invoice list.
    4. Select all invoices, and then choose Print.
    5. In the report request page, choose Print and then choose Microsoft Word… and you have your repro: All the invoices belong to the first customer and have the same invoice no., etc.

    This designed limitation is described in the Page Headers and Footers section of the Exporting to Microsoft Word (Report Builder and SSRS) article in the TechNet Library:

    http://technet.microsoft.com/en-us/library/dd283105(v=sql.110).aspx

    The article points this out: "However, when a page footer or page header contains a complex expression that evaluates to different values on different pages of a report, the same value might display on all report pages. "

    Since this is a declared design limitation, you could target SAVEASWORD to those reports where:

    • The report does not use Page Header / Page Footer

    Or

    • The report does have a Static Page Header / Page Footer

    If you would like to have this design changed in future version from SQL Server Reporting Service (SSRS) Team, I would encourage you to log a request of design change into MSCONNECT or vote for an existing one, if any.

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

    Duilio Tacconi (dtacconi)

    Microsoft Dynamics Italy

    Microsoft Customer Service and Support (CSS) EMEA

    A special thanks to Peter Borring Sørensen & Torben Wind Meyhoff from the Microsoft Dynamics NAV Core Team

  • Microsoft Dynamics NAV Team Blog

    Great update rollup news for AT, BE, CH, ES, FI, IS, NO

    • 3 Comments

    We have some great news to share with customers and partners in AT, BE, CH, ES, FI, IS, and NO: The next update rollups for Microsoft Dynamics NAV 2013 and Microsoft Dynamics NAV 2013 R2 will include local files for these countries.

    We know this has been long-awaited and we hope we are putting smiles on a few faces with this announcement. :-)

  • Microsoft Dynamics NAV Team Blog

    Important Information: In a live database with active users connected, changing an object multiple times or compiling all objects can cause data loss in NAV 2013 R2

    • 38 Comments

    You may experience data loss in Microsoft Dynamics NAV 2013 R2 in the following situations, separately or in combination:

    • Changing an application object more than once, for example by two different developers, in the same database connected to the same Microsoft Dynamics NAV Server instance while users are working in the system.
    • Compiling all application objects, and thereby potentially changing objects more than once, in a database that is connected to a Microsoft Dynamics NAV Server instance that users are accessing.

    To avoid the problem, we advise that you work according to the following best practices:

    • Application developers must be working on their own database and connect to their own Microsoft Dynamics NAV Server instance. When you deploy changes to the live production database, make sure that no users are working in the system.
    • You must compile objects only when no users are working in the system, including users connecting through NAS. 

    With update rollup 5 for Microsoft Dynamics NAV 2013 R2 - KB 2937999, this issue has been fixed and you do not have to take the precautions described above. However, we still advise that you separate development from production databases.

    Please note that implementing update rollup 5 will require a database conversion.

     

     

  • Microsoft Dynamics NAV Team Blog

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

    • 11 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

    Microsoft Dynamics NAV 2013 R2 available in the Windows Azure Portal under MSDN subscription

    • 9 Comments

    Ever wondered what it is like to work with Microsoft Dynamics NAV on Windows Azure - but found it too cumbersome even with our nice Windows Azure provisioning tools?  Then this might be something for you. 

    Today we have made Microsoft Dynamics NAV 2013 R2 easily available on Windows Azure with just a few clicks. The Microsoft Dynamics NAV 2013 R2 image is an exclusive offer for MSDN subscribers and includes a fully functional, ready to use Microsoft Dynamics NAV 2013 R2 installation including Microsoft SQL Server. The MSDN subscription gives you the well-known discounted prices and allows you to use it for development, test, and demo purposes, but not for production purposes.

    How to get it? Make sure you have an MSDN subscription and the subscription has Windows Azure benefits activated. Then follow these steps:

     

    1. Sign in to the Windows Azure Portal using your MSDN subscription.
    2. Choose the + sign at the bottom of the Portal page.
    3. Choose Compute, point to Virtual Machine, and then choose From Gallery.
    4. Select the MSDN filtering checkbox as shown in the following screenshot. This will filter the list to only show the available MSDN images.

    1. Choose the Microsoft Dynamics NAV 2013 R2 image.
    2. Choose the arrow in the lower-right corner.
    3. Fill in the relevant fields about the virtual machine as described in the following list:
      1. Specify the name of the virtual machine.
      2. Specify the size of the virtual machine, such as Medium.
      3. Specify the user name and password for connecting to the virtual machine.
      4. Specify the region  where you want to host your virtual machine, such as West Europe.
      5. Verify the remaining parameters. In most cases, the default values are sufficient.
    4. Choose the Finish icon to start the provisioning process.
    5. Once the image is provisioned after a few minutes, you can use Remote Desktop to connect to it. In the Azure Portal Virtual Machine page, choose the newly created image, and then choose Connect. Use the credentials that you specified step 7.

    When you are connected to the VM, you are welcomed to the Microsoft Dynamics NAV 2013 R2 virtual machine on Windows Azure:

    No further configuration is required and you can immediately start using the clients and the development environment.

    Best regards

    Kamil Koclega & Morten Jensen from the Dynamics NAV team

  • Microsoft Dynamics NAV Team Blog

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

    • 9 Comments

    Update rollup 4 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

     

    New in update rollup 4 

    Beginning with update rollup 4, the update rollups for Microsoft Dynamics NAV 2013 R2 now also includes hotfixes for the upgrade toolkit. 

     

    Where to find update rollup 4

    You can download update rollup 4 from KB 2930617 - Update Rollup 4 for Microsoft Dynamics NAV 2013 R2 (Build 36078).

    The hotfixes that have been released since update rollup 3 are listed in KB 2930617. 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

    Update Rollup 11 for Microsoft Dynamics NAV 2013 has been released

    • 8 Comments

    Update rollup 11 for Microsoft Dynamics NAV 2013 (Build 36076) has been released.

    Update rollup 11 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 11

    You can download update rollup 11 from KB 2930616 - Update Rollup 11 for Microsoft Dynamics NAV 2013 (Build 36076).

    The hotfixes that have been released since update rollup 10 are listed in KB 2930616. 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

    Microsoft Dynamics NAV 2009 R2, Microsoft Dynamics NAV 2013, and Microsoft Dynamics NAV 2013 R2 Compatibility with Microsoft Windows Server 2012 R2

    • 6 Comments

    At the time when we released Microsoft Dynamics NAV 2009 R2, Microsoft Dynamics NAV 2013, and Microsoft Dynamics NAV 2013 R2, all supported client and server operating systems were tested. However since that time, Windows Server 2012 R2 has become available. 

    Over the last few months, the Microsoft Dynamics NAV team has been testing the compatibility, and we are now proud to announce that Microsoft Dynamics NAV 2009 R2, Microsoft Dynamics NAV 2013, and Microsoft Dynamics NAV 2013 R2 are compatible with Windows Server 2012 R2!

    For more information, see the System Requirements on PartnerSource.

  • Microsoft Dynamics NAV Team Blog

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

    • 3 Comments

    Update rollup 3 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

     

    Where to find update rollup 3

    You can download update rollup 3 from KB 2918538 - Update Rollup 3 for Microsoft Dynamics NAV 2013 R2 (Build 36035).

    The hotfixes that have been released since update rollup 2 are listed in KB 2918538. 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

    Update Rollup 10 for Microsoft Dynamics NAV 2013 has been released

    • 0 Comments

    Update rollup 10 for Microsoft Dynamics NAV 2013 (Build 36005) has been released.

    Update rollup 10 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 10

    You can download update rollup 10 from KB 2918536 - Update Rollup 10 for Microsoft Dynamics NAV 2013 (Build 36005).

    The hotfixes that have been released since update rollup 9 are listed in KB 2918536. 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

    Understanding and Configuring Session Timeouts

    • 0 Comments

    When you start the Microsoft Dynamics NAV Windows client or the Microsoft Dynamics NAV Web client, a connection is established with the Microsoft Dynamics NAV Server instance, and a corresponding session is added on Microsoft Dynamics NAV Server. Microsoft Dynamics NAV Server includes several timeout settings that determine when a session closes because of inactivity, a lost connection, or the client closes.

    The Developer and IT Pro Help for Microsoft Dynamics NAV 2013 R2 includes a new topic that explains the session timeout behavior and configuration. For more information, see Understanding and Configuring Session Timeout in the MSDN Library.

  • Microsoft Dynamics NAV Team Blog

    Uploading large files from the Web client

    • 2 Comments

    If like me you’ve been tinkering with your Lumia 1020 smartphone and snapping some high-resolution photos over the holidays, you may be wondering whether Microsoft Dynamics NAV 2013 R2 can handle such large photo sizes on the Microsoft Dynamics NAV Web client.

    Let's say you want to capture photos of your product catalogue (using the Photo action on the Item card). When uploading large files such as high-resolution photos, Microsoft Dynamics NAV will show the following error:

    The file that you are trying to use is too large. Clearly. Whilst Microsoft Dynamics NAV defaults to 4MB uploads on the Web client, you will be pleased to hear it takes just a minor tweak to your IIS configuration to support larger file uploads: 

    1. Launch the IIS Configuration Manager (in this example I am using IIS 8 but similar steps apply to earlier versions).
    2. Select the Microsoft Dynamics NAV web site in the left pane and then double-click Request Filtering.
    3. Right-click and select Edit Feature Settings… in the context menu.
    4. Set field Maximum allowed content length to an appropriate value such as 100000000 (in bytes) and click OK.
    5. Now select the Microsoft Dynamics NAV web site in the left pane again and double-click the Configuration Editor.
    6. Make sure that the From field is set to "Microsoft Dynamics NAV 2013 R2 Web Client Web.config"
    7. Set field Section to system.web/httpRuntime
    8. A number of properties should appear. Set maxRequestLength to an appropriate value such as 100000 (this time it is in kilobytes) and click the Apply action on the right.

     

    The new settings should take effect immediately without the need for an IIS or site reset.

    Go ahead and try to upload a large file now and BANG! the upload succeeds.

    You can read more about the maxRequestLength property here:

    http://msdn.microsoft.com/en-us/library/system.web.configuration.httpruntimesection.maxrequestlength(v=vs.110).aspx

    Best regards,

    Lukasz Zoglowek and Mike Borg Cardona

Page 3 of 43 (637 items) 12345»