• Microsoft Dynamics NAV Team Blog

    Costing Error Detection and Data Correction white paper - updated for Microsoft Dynamics NAV 2013

    • 0 Comments

    The Costing Error Detection and Data Correction white paper and report has been updated for Microsoft Dynamics NAV 2013 and 2013 R2.

    The Costing Error Detection and Data Correction white paper discusses common inventory costing issues and how you can correct erroneous data after inventory costing issues have been identified. The white paper focuses on the data and the fields that typically cause problems in the cost adjustment process.

    The Costing Error Detection report can help you find common costing data problems. If the report shows that there are errors in your database, you can use the suggestions in the white paper to correct the data. The report can also be used to validate inventory data after an upgrade.

    To review the white paper and download the report for Microsoft Dynamics NAV 2013 and earlier versions, go to:

     

  • Microsoft Dynamics NAV Team Blog

    Announcement about Tax Updates Dependent on Cumulative Updates (CU) in Microsoft Dynamics NAV

    • 0 Comments

    This announcement describes upcoming changes around processes related to Tax Updates released for Microsoft Dynamics NAV.

    1. Tax Updates to be Built with Cumulative Update as a Baseline

    Effective July 15, 2014, all Tax Updates (commonly referred to as Regulatory Features) will be developed based on the latest Cumulative Updates as their baseline instead of the current practice of basing the same on an RTM release.

    This move will provide an improvement in quality, because a Tax Update is built on the latest baseline and state of code compared to the previous process of building on an older RTM version.

    This new process also now ensures that partners will have all Application level hotfixes in place. These were not included previously when a Tax Update was delivered, which meant that partners had to merge the hotfixes again while deploying the Tax Update.

    Example Scenario

    Version: Microsoft Dynamics NAV 2013/Country X

    Cumulative Updates Released 

    Update

    Release Date

    Microsoft Dynamics NAV 2013 RTM Country X

    September 2012

    CU 12

    March 2014

    CU 13

    April 2014

    CU 14

    May 2014

    CU 15

    June 2014

     

    Tax Updates Released 

    Tax Update

    Release Date

    Tax Update 1

    March 2013

    Tax Update 2

    April 2014

    Tax Update 3

    Developed and released in July 2014

     

    Current Model

    Tax Update 3 for Country X on Microsoft Dynamics NAV 2013 is developed using the following baseline or has the following prerequisites for installation:

    • Microsoft Dynamics NAV 2013 RTM X     +
      • Tax Update 1 + 
        • Tax Update 2

    New Model

    Tax Update 3 for Country X on Microsoft Dynamics NAV 2013 is developed and has only the following prerequisite:

    • Microsoft Dynamics NAV 2013 CU 15

    2. Tax Updates to be Released Only Through Cumulative Updates

    Effective October 1, 2014, all Tax Updates for Microsoft Dynamics NAV will be developed on CU as described in section 1 of this announcement and will be released only through Cumulative Updates. Microsoft Dynamics NAV
    will no longer release individual .fob or text files for a Tax Update.

    Partners now benefit by having all regulatory features in sync with the latest application code, a single and one stop quality solution from Microsoft.

    Applicability

    A. Applicable for all Microsoft Supported Countries where Cumulative Updates exist.

    B. Applicable for versions Microsoft Dynamics NAV 2013 and higher.

    Related Information

     

    The Microsoft Dynamics NAV team

  • Microsoft Dynamics NAV Team Blog

    NAV Design Pattern - Implementation of Surrogate Keys using the AutoIncrement Pattern

    • 3 Comments

    This week's pattern describes how to link tables in a generic way, so that satellite tables (such as a comment table) can be linked to multiple different master tables, each having its unique related comment lines. You can find all published patterns on the Dynamics Community Wiki site. 

    Meet the Pattern

    This Pattern is meant to create generic & reusable links between tables. The goal is to have an easy generic way to link a generically designed sub table to a record on a main table which can be used for other links too.

    To minimize the impact of customizations and to keep modules as generic and reusable as possible the idea of the Unique Record Identifier is:

    • To create a generic and reusable link on a main table with minimum impact on the table.
    • To create generic and reusable sub tables that effortless can be reused anywhere in the application.

    Know the Pattern 

    Over years of development many things are repeated across different implementation and even inside the same application. A typical example could be adding comments to an area just as it is done in Microsoft Dynamics NAV multiple times. There can be reasons for doing this again and again, but not only does this need to be maintained and upgraded over the years, but all the implementations of comments also needs to be tested separately. If a standard and generic comment could be developed and a generic way of connecting it to a main table this could resolved. This is exactly what this pattern will resolve.

    The following diagram shows the table structure for linking a Document Header and Line Table with a Document Comment Table.

    The following diagram shows the table structure for linking a Master Data Table with a Master Data Comment Table.

    A typical way of linking a table to master data or to a document has been to use the primary key of the table being linked to. This causes some issues as the linked table now is designed specifically for the main table and cannot be reused. In case of renames the linked table needs to be renamed too which is costly in processing. Code also needs to be added on the delete trigger of the table to ensure that the attached records get removed if needed. The following diagram shows a generic way of creating a Comment table and linking it in a generic way to the main table no matter what this table might be. The Unique Record Identifier on the main tables is an Integer with AutoIncrement set to Yes.

     

    It is recommended using this pattern in all tables which need sub tables unless specific reasons exists for not doing this.

    Use the Pattern

    Step 1: Create a generic Unique Record Identifier in the main table

    The pattern is implemented by adding a field called Unique Record Identifier in a table (Main Table) where links are needed to be established to. Set the Property Data Type to Integer, Editable to No & AutoIncrement to Yes.

    Step 2: Create a generic linkable subtable.

    Read more about the Unique Record Identifier on NAV Wiki...

     

    Best regards,

    Soren Klemmensen

    The NAV Patterns team

  • Microsoft Dynamics NAV Team Blog

    Merging Application Objects using Windows PowerShell

    • 5 Comments

    Upgrading a Microsoft Dynamics NAV solution is time consuming. You have to identify which changes you have to make, you have to upgrade the application objects and the application code, and you might have to move the existing data around so that it fits the new database schema. In Microsoft Dynamics NAV 2013 R2, we started delivering Windows PowerShell cmdlets and sample scripts that can help you automate different parts of the upgrade process. In the latest cumulative update, we introduce a new set of Windows PowerShell cmdlets that can help you through the code upgrade.

    You can use the new cmdlets to modify application object source files in the Microsoft Dynamics NAV 2013 R2 Development Shell, or by importing the Microsoft.Dynamics.NAV.Model.Tools.psd1 module into the Windows PowerShell Integrated Scripting Environment (ISE). The new application merge utilities install when you choose the Developer option in Microsoft Dynamics NAV 2013 R2 Cumulative Update 9 Setup, or if you add the development environment to another installation option.

    The application merge utilities include the following Windows PowerShell cmdlets:

    Name

    Description

    Merge-NAVApplicationObject

    Compares the changes that have been made between two sets of Microsoft Dynamics NAV application objects, and applies the difference to a third set of application objects. The result of the merge is a number of text files with the merged application objects. Any conflicts that the cmdlet cannot merge are identified in conflict files.

    Compare-NAVApplicationObject

    Compares text files that contain Microsoft Dynamics NAV application objects, and then calculates the delta between the two versions. The result of the comparison is a number of text files with the calculated delta.

    Update-NAVApplicationObject

    Applies a set of deltas to the specified application objects. The files that describe the delta are generated by the Compare-NAVApplicationObject cmdlet.

    Join-NAVApplicationObjectFile

    Combines multiple application object files into one text file

    Split-NAVApplicationObjectFile

    Splits a text file that contains two or more application objects into separate text files for each application object.

    Get-NAVApplicationObjectProperty

    Gets Microsoft Dynamics NAV application object properties from the specified application object text files.

    Set-NAVApplicationObjectProperty

    Sets Microsoft Dynamics NAV application object properties in the specified application object text files.

    Getting started

    You will be able to read more about the cmdlets and how to use them in the MSDN Library after the release of Microsoft Dynamics NAV ‘Crete’, but for now, you can also type Get-Help "NAV" in the Windows PowerShell ISE the Microsoft Dynamics NAV Development Shell.

    If you don’t want to use the Microsoft Dynamics NAV Development Shell, use the Windows PowerShell ISE. But before you can access the cmdlets, you must import the Microsoft.Dynamics.Nav.Model.Tools.psd1 module. Here is an example of the command you can type:

    Import-Module "${env:ProgramFiles(x86)}\Microsoft Dynamics NAV\71\RoleTailored Client\Microsoft.Dynamics.Nav.Model.Tools.psd1" -force

    Get-Help "NAV"

    Now you can see the Help for the cmdlets and take a closer look at the examples for how to use them. You can also see detailed Help for each cmdlet by typing the following command:

    Get-Help cmdletname -detailed

    And you can concentrate on the examples by typing the following command:

    Get-Help cmdletname -examples

    For all of the new cmdlets, the starting point is 3 versions of application objects that you want to merge. The following table describes the three versions of the Microsoft Dynamics NAV application that you want to compare and merge.

    Version

    Description

    ORIGINAL

    The baseline of the application merge. For example, the Microsoft release of MicrosoftDynamics NAV 2013 R2.

    MODIFIED

    The updated version of the original. For example, this can be Microsoft Dynamics NAV 2013 R2 Cumulative Update 9. Alternatively, it can be a small add-on.

    In many cases, the modified application is the version that contains fewer changes to the original than the version that is the target of the merge. This is because you want to apply fewer changes to a large application rather than applying a large change to a small application.

    TARGET

    The version of the application that you want to apply the difference between the original and the modified application to. For example, this can be your solution that you want to apply a cumulative update to. Alternatively, it can be a new major release from Microsoft that you want to apply your modified solution to.

    Each of these versions can be any version that you want to do a three-way merge between. ORIGINAL can be your add-on, MODIFIED can be a customization of your add-on, and TARGET can be a new release of Microsoft Dynamics NAV from Microsoft. But for the purposes of this blog post, we'll keep the definitions as described in the table above.

    As input to the cmdlets, you can provide a text file, a list of text files, or a folder with text files. So you need to export the relevant application objects as text files. Optionally, you can use the development environment command ExportObjects. You can export each application object to a separate text file, or you can export all objects to a single text file. Optionally, you can use the Join-NAVApplicationObjectFile and Split-NAVApplicationObjectFile cmdlets to structure the text files in the way that works better for you. Also, depending on your scenario, you can work with a subset of your application, such as all codeunits, objects within an ID range, or a specific group of objects. Use the tools to get the text files that you need, and take a look at the sample scripts for inspiration.

    The Windows PowerShell sample scripts are available in the attached compressed archive. Start by opening the HowTo-Start-Import-NAV-Module.ps1 script in the Windows PowerShell ISE, navigate the command prompt to the folder where you placed the samples, and then run the script. Then open one of the other scripts, such as HowTo-Merge-1-General.ps1, and follow the guidance in the script.

    The sample script package includes a folder with four subfolders that can help you get started with the scripts. The demonstration data in the ORIGINAL, MODIFIED, and TARGET folders illustrate the text files that are the input to the cmdlets. For clarity, we have chosen to have one application object in each file, but you can use the Join-NAVApplicationObjectFile cmdlet to combine all the text files in the MODIFIED folder in a single file, for example, before you run the script. That way you can see how the Merge-NAVApplicationObject cmdlet identifies the application objects in the combined text file. We find it easier to work with one object in each file, but the cmdlets are there so you can configure the text files in the way that works better for you.

    We suggest that you open each of the sample scripts in the Windows PowerShell IDE and read through them to get acquainted with the new cmdlets. Then, set up a small test environment of your own where you can safely use the cmdlets on your own application objects to upgrade your solution to Microsoft Dynamics NAV 2013 R2 Cumulative Update 9.

    For more information, see the Merge Application Object Source Files whitepaper, which you can download from the blog post that announced the availability of Cumulative Update 9 here: http://go.microsoft.com/fwlink/?LinkId=403646.

  • Microsoft Dynamics NAV Team Blog

    Cumulative Update 9 for Microsoft Dynamics NAV 2013 R2 has been released

    • 9 Comments

    Cumulative update 9 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2013 R2. 

    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 (New)
    • 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

    This cumulative update also introduces new application merge utilities: A new set of Windows PowerShell cmdlets that can help you through code upgrade.

    You can use the new cmdlets to modify application object source files in the Microsoft Dynamics NAV 2013 R2 Development Shell, or by importing the Microsoft.Dynamics.NAV.Model.Tools.psd1 module into the Windows PowerShell Integration Script Environment (ISE). The new application merge utilities install when you choose the Developer option in Microsoft Dynamics NAV 2013 R2 Cumulative Update 9 Setup, or if you add the development environment to another installation option.

    For more information, see the MicrosoftDynamicsNAV2013R2CU9_MergeApplicationObjectSourceFiles.pdf whitepaper, which is attached to this blog post. We will also write about the new cmdlets here on the blog.

    Where to find cumulative update 9

    You can download cumulative update 9 from KB 2977473 – Cumulative Update 9 for Microsoft Dynamics NAV 2013 R2 (Build 37221).

    For a full list of all hotfixes included in cumulative updates for Microsoft Dynamics NAV 2013 R2, see the following CustomerSource and PartnerSource pages: 

    CustomerSource:

    PartnerSource

    More Information

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

    For a list of all release cumulative updates, see Released Cumulative Updates for Microsoft Dynamics NAV 2013 R2.

  • Microsoft Dynamics NAV Team Blog

    Cumulative Update 16 for Microsoft Dynamics NAV 2013 has been released

    • 3 Comments

    Cumulative update 16 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2013. 

    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
    • SE - Sweden
    • UK - United Kingdom

    Where to find cumulative update 16

    You can download cumulative update 16 from KB 2977472 – Cumulative Update 16 for Microsoft Dynamics NAV 2013 (Build 37201).

    For a full list of all hotfixes included in cumulative updates for Microsoft Dynamics NAV 2013, see the following CustomerSource and PartnerSource pages: 

    CustomerSource:

    PartnerSource:

    More Information

    For more information about cumulative updates for Microsoft Dynamics NAV 2013, see Released Cumulative Updates for Microsoft Dynamics NAV 2013.

    For a list of all release cumulative updates, see Released Cumulative Updates for Microsoft Dynamics NAV 2013.

  • Microsoft Dynamics NAV Team Blog

    Synchronize metadata, please…

    • 6 Comments

    One of new procedures/functions we have in NAV 2013 R2 is “metadata synchronization”. It is process when object (table) description done in C\SIDE by NAV developer is applied to SQL object (object structure in SQL becomes the same as we have in NAV object designer).

    It is described at http://blogs.msdn.com/b/nav/archive/2014/03/27/table-synchronization-paradigm-in-microsoft-dynamics-nav-2013-r2.aspx

    Unfortunately synchronization step is not mentioned in some place, for example:
    - after you convert database to NAV 2013 R2, just after you have opened database with NAV 2013 R2 C\SIDE client and received message “database conversion was successful”  - run metadata synchronization;
    - after you have created new database – run metadata synchronization
    - in any case whatever you have done with objects – please run synchronization…

    About synchronization process in details you can read at https://mbs.microsoft.com/files/partner/NAV/Support/HotTopics/SynchronizingSchemachangesNAV2013R2.docx 

    But rough description could be: in NAV we have 3 “parts” of the same object: SQL object, Object description in Metadata snapshot, Object description in Object metadata.
    When synchronization runs, NAV compares object description in metadata snapshot and object metadata and if differences found then NAV tries to apply object description from object metadata to SQL object to make it as we see it objects designer in C\SIDE. When this is done, NAV updates object description in metadata snapshot and we have all 3 parts identical. So there must be no situation when SQL objects is not the same as object description in metadata snapshot.
    To find theses inconsistency we have released NAV 2013 R2 database consistency checker tool” which checks database metadata vs database structure and reports any inconsistency which could be fixed directly in SQL. Mentioned tool is released under KB 2963997 and could be downloaded from hotfix site.

    Metadata synchronization process is running by NAV Service Tier (NST) and it starts when
    - any client (RTC, Web client, Web service) connect to NST
    - or executed NAV Administration PowerShell cmdlet “Sync-NAVTenant”
    - or user imports objects to object designer and option “Prevent data loss from table changes” is set to “Yes”.

    Usually synchronization is fast process: we run RTC, connect to NST, synchronization starts and finishes and RTC loads.

    However when we do “big changes” (added fields to table and few keys…) or have big databases, synchronization runs hours. I have cases where synchronization runs >3 hours and here comes problem: process runs in background, users are not aware about it and whatever they tries to do with db, they receives different errors (about channel failure; SQL timeout, service not responsive and etc.). Even worse user can stop NST and with this kills synchronization and then SQL starts rollback for next few hours…

    When NAV shows that synchronization finished successfully (cmdlet finished) or NAV client shows error, it could be that SQL still continue to synchronize metadata in background (or rollback ). Run sp_who2 in SQL management studio to see if there are running/active processes where ProgramName is “Microsoft Dynamics NAV Service”. If there is not “sleeping” process and it’s DiskIO increase continuously, please wait and do nothing with NAV (don’t modify any object, don’t compile, don’t import – better close development environment at all). At some moment processes becomes “sleeping” – this means synchronization finished (successful or failed you can see in Windows Event Viewer). Only after that you can continue your further actions.

    Our development team is preparing solutions which make metadata synchronization more transparent and user friendly, so we expect easier life soon, but now: Synchronize metadata and track synchronization, please…  

      

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

    Gedas Busniauskas
    Microsoft Lithuania
    Microsoft Customer Service and Support (CSS) EMEA

  • Microsoft Dynamics NAV Team Blog

    Introducing the Microsoft Dynamics NAV Application Profiler

    • 2 Comments

    Did you ever wish you could monitor how your application code performs at real time? We have produced a sample and a video that can help you get started with C/AL tracing and application performance profiling.

    Get the Microsoft Dynamics NAV Application Profiler here, http://go.microsoft.com/fwlink/?LinkId=403898, and watch the video on how to install, configure and use this tool to enable C/AL code tracing and determine application performance during code execution here, http://go.microsoft.com/fwlink/?LinkId=403897.

     

    David Worthington and Dmytro Sitnik from the Dynamics NAV team

    Format: ???
    Duration: 7:00

  • Microsoft Dynamics NAV Team Blog

    Introducing the NAV C/AL Cookbook

    • 0 Comments

    While talking about design patterns, we often came upon a different category of code solutions. Useful, reusable, good practice code solutions which are just not design patterns. They might be APIs, they might be mini-features, new platform functionality, or services.

    We don't want to throw away those good ideas. On the other side, they do not belong to design patterns.

    Hence, a chapter called “Recipes - The NAV C/AL Cookbook” was born, as a separate section on the Dynamics Community NAV Patterns Wiki. We hope you’ll find it as useful as we did. And find below one of the first articles on this new section. Note that we’re still using the “Meet the pattern - Know the pattern” format, just to keep an uniform approach on all articles, for the moment.

    Creating Custom Charts

    by Nikola Kukrika at Microsoft Development Center Copenhagen

    Meet the Pattern

    The goal of this pattern is to enable you to:

    1. Use charts in the web client.
    2. Create charts with custom functionality.

    Know the Pattern

    This pattern enables you to implement a business chart (Specific Chart type) in a way that is maintainable and reusable on other pages. This also enables you to provide specific functionality that is not possible with the Generic Chart type and it enables you to show charts in the web client.

    The Business Chart add-in is a special because it is a combination of .NET and Javascript add-ins depending on the display target. In the Microsoft Dynamics NAV Web client, it renders a JavaScript control, while in the Microsoft Dynamics NAV Windows client, it renders a .NET control. Because of this behavior, you can expect minor differences in how the chart is presented in the two clients. Note that this implementation is specific to the Microsoft Dynamics NAV platform code, because it is not possible to create add-ins that combines .NET and JavaScript by using a framework API.

    Example of the same chart in the Microsoft Dynamics NAV Windows client:

    The most obvious differences in chart rendering in the two clients are: Slightly different line heights, slightly different chart height, legends in web-client charts can be used as toggle filters to show/hide groups (this is not possible in the win client).

    Implementation Overview

    Add-in Buffer Table

    This table is used to encapsulate the logic of the Business Chart Add-in. The table handles the following logic:

    • Storing chart values and conversion from .NET to C/AL and vice versa
    • Handling of captions: We must use C/AL to provide multilanguage text in add-ins. In addition, the multilanguage text must be encapsulated in a single place, because we pass/read the same dataset from/to the add-in.
    • DrillDown logic
    • Other helper data related functions, for displaying date, periods, etc. 

    Note: It is recommended that you reuse the Business Chart Buffer table (485) as a buffer table or extend. It is a generic table which should cover most of the use cases. Implement a new buffer table only if this table does not meet your needs.

    CardPart page

    The CardPart page hosts the Business Chart add-in and must use the add-in buffer table as a source table.

    On the page, you must implement the following triggers:

    • AddInReady – Executed when the page is done rendering. Used to initialize the add-in.
    • DataPointClicked – Single-click on an element on the chart.
    • DataPointDoubleClicked – Double-click on an element on the chart

    The CardPart usually contains a StatusText variable to provide more information about the chart or dataset and a set of actions to control the chart.

    The most commonly used actions are: ... Read more on NAV Wiki...

     

  • Microsoft Dynamics NAV Team Blog

    Help us make Microsoft Dynamics NAV better

    • 3 Comments

    We always strive to make Microsoft Dynamics NAV a better product – and in order for us to do that efficiently we need to know how real customers out there are using the product. To help us getting that knowledge, Microsoft Dynamics NAV Server can send anonymous data about how server instances are configured and used.

    You may have noticed the following option when installing Microsoft Dynamics NAV Server:

    Setting this to ‘Yes’ makes the server generate a small file every day at midnight, and this file gets uploaded to Microsoft. The generation of this file happens asynchronously and is designed so that the performance impact is completely negligible. Furthermore, data is sent when the service is stopped.

    The collected data points fall in 3 categories

    • Environment info: Available memory, Windows version, processor speed etc.
    • Configuration info: Settings from the configuration file
    • Usage data: Which objects in the Microsoft ID range have been executed in the last 24 hours

    We want to stress that we do not send any customer / partner specific data, and we have no way of finding out which company sent certain data. We only collect information about Microsoft Dynamics NAV objects that are part of the standard application, and we do not read or send any business data.

    So how is this useful to us? Identifying the pages and reports that are most used allows us to prioritize improvements to these higher than others. For example, knowing the Windows versions that are in use gives input to our system requirements and support matrix.

    Over time we will change and expand the data collected to evaluate the success of new features, so the actual data sent may vary between versions.

    The data sent is only useful if we have statistically significant amounts to make valid conclusions, so you can help us by having your customers participate in the Customer Experience Improvement program. This can be done by selecting ‘Yes’ in the Send Feedback question when installing the server, or by setting the following value to true in the configuration file for the service: 

    <!--

        When this parameter is set to TRUE, Microsoft Dynamics NAV Server collects basic information

        about your hardware configuration and how you use Microsoft Dynamics NAV software.

        Microsoft uses this information to identify trends and usage patterns. When this parameter is

        set to FALSE, no data is collected. The default value is FALSE. 

      -->

      <add key="EnableSoftwareQualityMetrics" value="false" />

     

    Please help us making the right choices when developing Microsoft Dynamics NAV by encouraging your customers to allow sending feedback to us from their deployments.

    For more information, see the Microsoft Dynamics NAV Privacy Statement.

    Best regards,

    The Dynamics NAV team

  • Microsoft Dynamics NAV Team Blog

    Experience Convergence Europe! Register Early and Save!

    • 0 Comments

    Convergence 2014 Europe is a Microsoft Dynamics customer event and the best opportunity to expand your professional network, explore Microsoft solutions, and bring new ideas to life. Even better, if you register early, you'll save €300.

    Whether you are new to Convergence or have attended in the past, there are many benefits to going: networking, learning opportunities, visionary business leaders and access to product experts. As a user of Microsoft Dynamics NAV you will have the opportunity to explore what is new in the coming version code named Microsoft Dynamics “Crete”. Convergence Europe is held in Barcelona November 4-6. Explore more on the event web site: http://www.microsoft.com/dynamics/convergence/europe14/

  • Microsoft Dynamics NAV Team Blog

    Importing and Exporting Data in Microsoft Dynamics NAV 2013 R2 CU 8

    • 18 Comments

    In earlier versions of Microsoft Dynamics NAV, you could move or copy all or part of the data in a database by using the Microsoft Dynamics NAV backup functionality. In Microsoft Dynamics NAV 2013 R2, the support for the .fbk files was removed, but with Cumulative Update 8 for Microsoft Dynamics NAV 2013 R2, we introduce Windows PowerShell cmdlets so you can export data from a Microsoft Dynamics NAV database and import it into another Microsoft Dynamics NAV database. You can also export and import data in the Microsoft Dynamics NAV Windows client.

    You can export and import a single company or all companies in a database, and you can export and import other types of data such as global data, application data, and application objects. As part of Cumulative Update 8, we include a whitepaper that provides examples of the types of data and how to export and import data using Windows PowerShell cmdlets as well as in the Microsoft Dynamics NAV Windows client.

    When you export data from a Microsoft Dynamics NAV database, the data is stored in a file with the extension .navdata, which is a new file format that is proprietary to Microsoft Dynamics NAV data. You cannot edit the .navdata files in other tools.

    The data that you export is not deleted from the original database. So that means that you can use the functionality to essentially take a copy of your customer’s live data, leave them to continue working, while you import the data into an offline database back at your office for further debugging or other investigation. You can also use the .navdata files to move data to a new database, such as moving a company to a new database when you want to deprecate a database, for example.

    Exporting and Importing Data in the Microsoft Dynamics NAV Windows Client

    To export or import data, in the Search box, enter Data File, and then choose the related link.

    To export data, you specify the type of data that you want to export, and when you choose the OK button, you specify where you want to save the file.

    To import data, you specify the .navdata file to import data from, but you can't import an application if the .navdata file contains an application. This is because you can't overwrite the application that is currently open in the Microsoft Dynamics NAV Windows client. So the window has one less type of data that you can choose to import:

    If you want to import an application into a Microsoft Dynamics NAV database, you must use the Import-NAVData Windows PowerShell cmdlet.

    Windows PowerShell Cmdlets

    The following table describes the Windows PowerShell cmdlets that are new in Microsoft Dynamics NAV 2013 R2 Cumulative Update 8.

    Name

    Description

    Export-NAVData

    Exports data from a Microsoft Dynamics NAV database. You can export company-specific data, and you can choose to include global data, application data, or application objects.

    Import-NAVData

    Imports data into a Microsoft Dynamics NAV database from a file. You can import all data in the file, or you can choose to include specific companies, global data, application data, or application objects.

    You can only import an application into an empty database.

    Get-NAVDataFile

    Gets information from a file that has been exported from a Microsoft Dynamics NAV database.

    The extracted information includes the types of data that the file contains and any company names.

    The cmdlets take different parameter sets depending on how you connect to the database that you want to export data from or import data into. You can access the database through the Microsoft Dynamics NAV Server instance, or you can access the database directly as described in the following table.

    Access

    Description

    Through the Microsoft Dynamics NAV Server instance.

    Use parameter sets that include –ServerInstance when the database that you want to access is mounted against a Microsoft Dynamics NAV Server instance.

    The user account for the Microsoft Dynamics NAV Server instance must have access to write to the location that is specified by the –FileName parameter.

    Through a direct connection to the database.

    Use parameter sets that include –DatabaseServer and –DatabaseName when the Microsoft Dynamics NAV Server instance is stopped or not available. For example, if you want to import an updated application into a database, you stop the service so that users cannot access the database.

    You must have access to write to the location that is specified by the –FileName parameter.

    The following table describes the Windows PowerShell cmdlets that are modified in Microsoft Dynamics NAV 2013 R2 Cumulative Update 8.

    Name

    Description

    Get-NAVCompany

    Gets a list of the Microsoft Dynamics NAV companies in the specified tenant database or exported Microsoft Dynamics NAV data file.

    The cmdlet has been updated to be able to get information from a Microsoft Dynamics NAV data file.

     

    However, the Help for the Export-NAVData and Import-NAVData Windows PowerShell cmdlets does not show the correct syntax when you run a command such as the following:.

    PS C:\WINDOWS\system32> Get-Help Export-NAVData

     

    Refer to the following syntax for the Export-NAVData cmdlet:

    1. Export-NAVData -DatabaseName <string> -FileName <string> [-DatabaseServer <string>] [-ApplicationDatabaseServer <string>] [-ApplicationDatabaseName <string>] [-Description <string>] [-IncludeApplication] [-IncludeApplicationData] [-IncludeGlobalData] [-CompanyName <string[]>] [-Force]  [<CommonParameters>]

    2. Export-NAVData [-ServerInstance] <string> [[-Tenant]< TenantId>] -FileName<string> [-Description <string>] [-IncludeApplication] [-IncludeApplicationData] [-IncludeGlobalData] [-CompanyName <string[]>] [-Force]  [<CommonParameters>]

    3. Export-NAVData [-ServerInstance] <string> [[-Tenant] <TenantId>] -FileName<string> -AllCompanies [-Description <string>] [-IncludeApplication] [-IncludeApplicationData] [-IncludeGlobalData] [-Force]  [<CommonParameters>]

    4. Export-NAVData -DatabaseName <string> -FileName <string> -AllCompanies [-DatabaseServer <string>] [-ApplicationDatabaseServer <string>] [-ApplicationDatabaseName <string>] [-Description <string>] [-IncludeApplication] [-IncludeApplicationData] [-IncludeGlobalData] [-Force]  [<CommonParameters>]

     

    Refer to the following syntax for the Import-NAVData cmdlet:

    1. Import-NAVData [-FileName] <string> -DatabaseName <string> [-DatabaseServer <string>] [-ApplicationDatabaseServer <string>] [-ApplicationDatabaseName <string>] [-IncludeApplication] [-IncludeApplicationData] [-IncludeGlobalData] [-CompanyName <string[]>] [-Force] [-WhatIf] [-Confirm]  [<CommonParameters>]

    2. Import-NAVData [-ServerInstance]< string> [[-Tenant] <TenantId>] [-FileName] <string> [-IncludeApplicationData] [-IncludeGlobalData] [-CompanyName <string[]>] [-Force] [-WhatIf] [-Confirm]  [<CommonParameters>]

    3. Import-NAVData [-ServerInstance]< string> [[-Tenant] <TenantId>] [-FileName] <string> -AllCompanies [-IncludeApplicationData] [-IncludeGlobalData] [-Force] [-WhatIf] [-Confirm]  [<CommonParameters>]

    4. Import-NAVData [-FileName] <string> -DatabaseName <string> -AllCompanies [-DatabaseServer <string>] [-ApplicationDatabaseServer <string>] [-ApplicationDatabaseName <string>] [-IncludeApplication] [-IncludeApplicationData] [-IncludeGlobalData] [-Force] [-WhatIf] [-Confirm]  [<CommonParameters>]

     

    You can find more information about this functionality, and the new or changed objects, in the following documents on the W1 version of the Microsoft Dynamics NAV 2013 R2 CU8 download media:

    • MicrosoftDynamicsNAV2013R2CU8_ExportImportDataUsingNavDataFiles.pptx
    • MicrosoftDynamicsNAV2013R2CU8_ImportExportData.pdf

    In subsequent cumulative updates, the documents will be available in the country-specific downloads as well.

  • Microsoft Dynamics NAV Team Blog

    NAV Design Pattern - Instructions in the UI

    • 3 Comments

    Meet the Pattern

    To mitigate usability problems with learnability or discoverability of Microsoft Dynamics NAV functionality, it is possible to embed instructions in the user interface (UI) in connection with the task that the user is performing. The goal is to explain how to use the product or feature without impairing the user’s productivity after user has learned how to use a feature.

    Know the Pattern

    Users must often go through a few days of training to learn how to use Microsoft Dynamics NAV, and even then, many users rely on super users to help them mitigate difficulties using Microsoft Dynamics NAV. In addition, because of low discoverability and learnability, many useful features are not being used at all.

    Users’ expectations are changing. They expect the software to be usable out-of-the-box because this is the trend in software generally.

    One of the cheapest and most effective methods to solve usability issues is to embed instructional messages in the product. From a user-experience point of view, this should be used as a last resort. UI should be self-explanatory, efficient, and simple to use. Accordingly, you should only implement this pattern if simplifying and improving a scenario is not possible or is too expensive.

    In this connection, the most important requirement is not to impair productivity of the users. One of the biggest and most common UX mistakes that developers make is to “optimize for new users”. After the user has learned how to use the product, all the instruction texts and dialogs that we added to the UI will clutter the page and make information less visible. Instructional dialogs on routine tasks will become annoying. Therefore, we must make all instructions dismissible.

    In the Mini App solution we have used following elements:

    1. Dismissible dialogs
    2. FastTabs with instructional text
    3. Help tiles on a Role Center
    4. Tooltips on actions and fields
    5. Task-oriented page Help

    Use the Pattern

    The following pattern applies to dismissible parts in the UI.

    We have a table that stores the instructional code ID and the UserID, so that we can track which user has turned off which instruction. All the logic handling is done from a codeunit. It is the responsibility of the codeunit to show/hide dialogs if needed. 

    Dismissible Dialogs

    Dismissible dialogs show the instructional message about the functionality, with the user option to... read more on the NAV Design Patterns wiki.

    Best regards,

    Nikola Kukrika at Microsoft Development Center Copenhagen

  • Microsoft Dynamics NAV Team Blog

    Cumulative Update 15 for Microsoft Dynamics NAV 2013 has been released

    • 1 Comments

    Cumulative update 15 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2013. 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
    • SE - Sweden
    • UK - United Kingdom

    Where to find cumulative update 15

    You can download cumulative update 15 from KB 2971745 – Cumulative Update 15 for Microsoft Dynamics NAV 2013 (Build 36919).

    For a full list of all hotfixes included in the cumulative update, see the following CustomerSource and PartnerSource pages:

    CustomerSource:

    PartnerSource:

    More Information

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

  • Microsoft Dynamics NAV Team Blog

    Cumulative Update 8 for Microsoft Dynamics NAV 2013 R2 has been released

    • 11 Comments

    Cumulative update 8 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2013 R2. 

    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

    Cumulative update 8 also introduces new functionality for exporting and importing companies and other data. You can export a company from a Microsoft Dynamics NAV database and import it into another database, and you can export and import other types of data such as global data, application data, and application objects.

    In earlier versions of Microsoft Dynamics NAV, you exported and imported this type of data as part of backing up and restoring databases. In Microsoft Dynamics NAV 2013 R2 CU8, you can do this by using the Export-NAVData and Import-NAVData Windows PowerShell cmdlets. You can also import and export data in the Microsoft Dynamics NAV Windows client.

    For more information, see the following documents on the W1 version of the Microsoft Dynamics NAV 2013 R2 CU8 download media:

    • MicrosoftDynamicsNAV2013R2CU8_ExportImportDataUsingNavDataFiles.pptx
    • MicrosoftDynamicsNAV2013R2CU8_ImportExportData.pdf

    Please note that there is very limited support for exporting and importing data in the Microsoft Dynamics NAV Web client. Use the Microsoft Dynamics NAV Windows client or the Windows PowerShell cmdlets instead.

    Where to find cumulative update 8

    You can download cumulative update 8 from KB 2971746 – Cumulative Update 8 for Microsoft Dynamics NAV 2013 R2 (Build 36897).

    For a full list of all hotfixes included in cumulative updates for Microsoft Dynamics NAV 2013 R2, see the following CustomerSource and PartnerSource pages: 

    CustomerSource:

    PartnerSource

    More Information

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

Page 1 of 43 (639 items) 12345»