Microsoft Dynamics NAV

Team Blog

  • Microsoft Dynamics NAV Team Blog

    Signing a ClickOnce Microsoft Dynamics NAV Windows Client Deployment (Part 3 of 5)

    • 0 Comments

    Deploying the Microsoft Dynamics NAV Windows client makes it easy for end users to install, upgrade, and uninstall the Microsoft Dynamics NAV Windows client. They can do this with a few clicks, without help from super users or IT administrators.

    This video shows how a partner or IT administrator can sign a ClickOnce deployment using a Certificate, and how this improves security and confidence for end users when they install the Microsoft Dynamics NAV Windows client.

    Watch video

    This is the third video in a series of how-to videos that show how a partner or IT administrator can deploy the Microsoft Dynamics NAV Windows client with ClickOnce. Make sure to watch the first video before you watch this video.

    For a detailed step-by-step guide about how to deploy the Microsoft Dynamics NAV Windows client  with ClickOnce, see http://go.microsoft.com/fwlink/?LinkId=251676.

    -Christian Heide Damm

  • Microsoft Dynamics NAV Team Blog

    Deploying the Microsoft Dynamics NAV Windows Client to a Web Server with ClickOnce (Part 4 of 5)

    • 0 Comments

    Deploying the Microsoft Dynamics NAV Windows client with ClickOnce makes it easy for end users to install, upgrade, and uninstall the Microsoft Dynamics NAV Windows client. They can do this with a few clicks, without the help from super users or IT administrators.

    This video shows how a partner or IT administrator can host a ClickOnce deployment on a web server instead of on a file share. This is best suited for public deployments over the internet, as opposed to deployments internally in an organization.

    Watch video

    This is the fourth video in a series of how-to videos that show how a partner or IT administrator can deploy the Microsoft Dynamics NAV Windows client with ClickOnce. Make sure to watch the first video before you watch this video.

    For a detailed step-by-step guide about how to deploy the Microsoft Dynamics NAV Windows client with ClickOnce, see http://go.microsoft.com/fwlink/?LinkId=251676.

    -Christian Heide Dam

  • Microsoft Dynamics NAV Team Blog

    Deploying the Microsoft Dynamics NAV Windows Client to Azure Blob Storage with ClickOnce (Part 5 of 5)

    • 0 Comments

    Deploying the Microsoft Dynamics NAV Windows client with ClickOnce makes it easy for end users to install, upgrade, and uninstall the Microsoft Dynamics NAV Windows client. They can do this with a few clicks, without the help from super users or IT administrators.

    This video shows how a partner or IT administrator can host a ClickOnce deployment in Azure blob storage. This combines the simplicity of a file share deployment with the accessibility of a public web server deployment.

    Watch video

    This is the fifth video in a series of how-to videos that show how a partner or IT administrator can deploy the Microsoft Dynamics NAV Windows client with ClickOnce. Make sure to watch the first video before you watch this video.

    For a detailed step-by-step guide about how to deploy the Microsoft Dynamics NAV Windows client with ClickOnce, see http://go.microsoft.com/fwlink/?LinkId=251676.

    -Christian Heide Damm

  • Microsoft Dynamics NAV Team Blog

    Document Management - Zetadocs Express is Now Available for Microsoft Dynamics NAV 2013

    • 0 Comments

    Following the launch of Microsoft Dynamics NAV 2013, Zetadocs Express has been updated for use with the Microsoft Dynamics NAV 2013 Windows client. The updated version can be downloaded from CustomerSource and PartnerSource.

    Zetadocs Express is the document management add-on available at no additional cost to users on a Business Ready Enhancement Plan, it includes the following:

    • Drag and drop - Any file, email or attachment can be dragged and dropped onto a record in the NAV Windows client to store it in SharePoint, linked to the record and listed in the Documents FactBox.
    • Document approval - Simple SharePoint workflows can be started for any document listed in the FactBox, such as an invoice, and the approval status monitored in Microsoft Dynamics NAV.
    • Save and Send any report - Click the “Save and Send” button to email almost any customized Microsoft Dynamics NAV report using SQL Server Reporting Services, archiving a copy automatically in SharePoint for future retrieval on-screen.

    As with previous releases, partners can download Zetadocs Express and include document management in their demonstrations of Microsoft Dynamics NAV. Customers on a Business Readiness Enhancement Plan should talk to their partners to get this installed in order to take advantage of document management capabilities integrated into Microsoft Dynamics NAV.

  • Microsoft Dynamics NAV Team Blog

    Jobs WIP Calculation Compliance in Microsoft Dynamics NAV 2013

    • 0 Comments

    Work in Process, WIP, and the related recognition of costs and revenues has a huge impact on the bottom-line for a project-based company. Project managers, accountants, and controllers are monitoring this recognition closely and for them it is crucial to have the process be as simple yet accurate as possible. Since the process has such an impact on financial reporting, it is also under the scrutiny of auditors. International and country-specific accounting standards control the WIP and Recognition process thoroughly. For these reasons, it’s important that the process as well as its result be easy to understand.

    So what benefits does Microsoft Dynamics NAV 2013 bring to accountants and controllers? Flexibility in defining WIP methods makes it easy to have Microsoft Dynamics NAV 2013 fit particular company or industry requirements and country specific accounting standards. Accountants are in complete control of which of the WIP methods is to be used in the company to avoid rework later in the process and risking incompliance. Accountants can enforce a policy of using a particular WIP method, posting detail, and posting schemas for all of a company’s projects, thus providing consistent and accurate financial data for management. Microsoft Dynamics NAV 2013 provides two additional levels of detail while posting WIP to improve an accountant’s efficiency during the reconciliation process. First, it provides a choice on level of detail during posting of WIP to the general ledger. Second, it provides the ability to allocate different categories of costs (inventory, resources) to different general ledger accounts. 

    All of the policies that an accounting department establishes come into effect at a point where data about actual execution of the project, collected by the project manager and project team, meets with the balance sheet. In Microsoft Dynamics NAV 2013, this place is called the WIP cockpit. The WIP cockpit provides a complete overview of costs, revenues, and profits generated by the project in particular period. In a single place, the accountant can overview the amounts that will be posted to company ledgers, and see how these amounts were calculated, with details of the underlying transactions that caused them just another click away. In addition, the WIP cockpit displays WIP warnings, which enable the accountant to see if the underlying data collected by the project team is in line with what is defined by the WIP method and if all prerequisites for recognizing costs and revenues are met before posting WIP to a company’s balance sheet. Posting WIP to the balance sheet (and reversing it in case of last minute changes to project costs) is as easy in Microsoft Dynamics 2013.

    What about benefits for project managers? A project manager, who is responsible for the execution and monitoring of a project, can focus on his job and not become bogged down with the project’s accounting details. How? Well, Microsoft Dynamics NAV 2013 enforces policies set by the accounting department by taking care of all the accounting-related requirements during creation, planning, execution and monitoring for the project. The project manager makes sure that all the costs related to the project have been accounted for and that all that should be invoiced to the customer is invoiced. When this is done, the WIP cockpit will provide him with an overview of what will be handed over to the accounting department to be recognized in the company’s books. Before wrapping it up for a milestone or period end, the project manager can initiate calculation of WIP and verify that no warnings or violations of policies set by the accounting department exist, so project information can be properly reflected in the company’s books. When warnings appear, usually something is missing or is not accounted for. In Microsoft Dynamics NAV 2013, finding out what that is this just a click away and after warnings are sorted out, the  project manager can use Microsoft Dynamics NAV 2013 to recalculate WIP, and take these last minute changes into account.

    -Ivan Koletic

  • Microsoft Dynamics NAV Team Blog

    Alternative Ways of Starting the Microsoft Dynamics NAV 2013 C/AL Debugger

    • 0 Comments

    The other day a partner asked me about how to start the Microsoft Dynamics NAV 2013 C/AL Debugger for another NAV Server instance than the one used by C/SIDE.

    The explanation is below, but first, let’s see how C/SIDE finds the NAV Server instance used for running and debugging.

    The Microsoft Dynamics NAV Server Instance used by C/SIDE for Run and Debug 

    When you Run an application object from the C/SIDE Object designer, C/SIDE is starting a Dynamics NAV Windows client with the application url constructed from:

    • NAV Server as defined in File/Database/Information Server Instance field (see Database Information)
    • Current selected Company in C/SIDE
    • Type and id of the application object you run

    Read more here: Starting the Windows Client at the Command Prompt, the URL parameter.

    This could be an example:

    Microsoft.Dynamics.Nav.Client.exe "DynamicsNAV://localhost:7046/dynamicsnav70/CRONUS International Ltd./RunPage?Page=42"

    The rest of the client configurations are taken from the default ClientUserSettings.config, which is typically found at %APPDATA%\Microsoft\Microsoft Dynamics NAV\70.

    The same principle is used when you start the debugger from within C/SIDE Tools/Debugger/Debug Session.

    All this works quite well in more confined setups where you can address different databases and NAV Servers if you are using the same authentication type for them all, but if you want to address different NAV Servers having for example different authentication types, you have to find other solutions – feel free to be inspired by how to.

    Define Alternative Ways of Starting the Microsoft Dynamics NAV 2013 C/AL Debugger

    Now let’s say you have made a dedicated NAV Test environment with:

    • a separate database
    • dedicated NAV Server(s)
    • another client authentication type than you are using in your Development environment
    • no development environment installed

    … and you want to debug some issue that appears in the Test environment from your development environment machine.

    The trick is to create a Dynamics NAV Windows client shortcuts on your development machine that specifies:

    Ending up in a combined command line description:

    Microsoft.Dynamics.Nav.Client.exe -settings:file  "DynamicsNAV://< Server>[:<port]>/<ServerInstance>/<Company>/debug"

    Or the short-form (all defaults to the .config settings):

    Microsoft.Dynamics.Nav.Client.exe -settings:file  "DynamicsNAV://///debug"

    Adding up to shortcut examples like this:

    Microsoft.Dynamics.Nav.Client.exe -settings:"%USERPROFILE%\Desktop\TestEnv.config" "DynamicsNAV://///debug"

    Microsoft.Dynamics.Nav.Client.exe -settings:"%USERPROFILE%\Desktop\ProdEnv.config" "DynamicsNAV://///debug"

    Or with full paths like this:

    "%ProgramFiles(x86)%\Microsoft Dynamics NAV\70\RoleTailored Client\Microsoft.Dynamics.Nav.Client.exe" -settings:"%USERPROFILE%\Desktop\TestEnv.config" "DynamicsNAV://///debug"

    Note

    The Windows client specifically understands the “special” /debug url, which is currently a “shorthand” for starting the client with:

    • -debug (that sets the CURRENTEXECUTIONMODE to Debug and groups the debugger clients separately in the taskbar under the debugger icon)
    • -shownavigationpage:0  (i.e. not showing a role center)
    • And do what’s defined in ApplicationManagement (Codeunit 1). LaunchDebugger (Trigger 60)
      • Typically, running the “Session List” (Page 9506)

    The debugger can be started this way because it is working similar to any Microsoft Dynamics NAV solution.

    -Hans Kierulff

  • Microsoft Dynamics NAV Team Blog

    Use Open XML to Extend the Excel Buffer Functionality (Part 2 of 2)

    • 0 Comments

    In Microsoft Dynamics NAV, there are several areas that enable the user to perform analysis in Microsoft Excel. Areas such as importing and exporting budgets, analysis by dimensions, and a number of selected reports all use Excel Buffer to export data to Microsoft Excel. In Microsoft Dynamics NAV 2013, the exporting technology has changed to gain better performance in the export as well as to enable more advanced customization capabilities. In Microsoft Dynamics NAV 2013, Excel Buffer has changed from being a chatty client automation solution to one that uses the Open XML SDK 2.0 for Microsoft Office and renders the Excel workbook on the server side.

    In the blog post Excel Buffer Using Open XML Instead of Excel Automation - (Part 1 of 2), I demonstrated simple write and read scenarios. This blog post will go into details on how you can use the Open XML API in C/AL to extend the Excel Buffer functionality.
     
    I will show what can be done with some additional cell formatting. The following areas will be covered:

    • Exposing the Microsoft Dynamics NAV Open XML worksheet writer object in table 370.
    • Using the decorator parameter to provide additional formatting.
    • Creating an OpenXml Helper class to interact with the lack of support for generics in C/AL.
    • Showing the file management capabilities by download file to client from server, without opening it directly into Excel.

    Exposing the Microsoft Dynamics NAV Open XML worksheet Writer Object in Table 370

    You need to expose the workbook writer object from table 370 by adding the following method. In this way, you open for applying functionality from the extensive and verbose Open XML API. The easiest way is to export the Excel Buffer table (table 370), add the following procedure, and then reimport and compile the object.

    PROCEDURE GetWorkbookWriter@21(VAR WrkBookWriter@1000 : DotNet "'Microsoft.Dynamics.Nav.OpenXml, Version=7.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.Microsoft.Dynamics.Nav.OpenXml.Spreadsheet.WorkbookWriter");
    BEGIN
      WrkBookWriter := XlWrkBkWriter;
    END;
     
    Using the Decorator Parameter to Provide Additional Formatting

    Due to a limitation in C/AL, you cannot use generics as part of the C/AL DotNet object type. Therefore, you need to create a helper class that can handle the places where the Open XML SDK only uses generics. This helps avoid using unnecessary, complex looping of collections in C/AL code. Often tasks like this are much easier to implement in a DotNet helper class. An example of this is described below where I have a simple method that can append an Open XML element to a collection.
     
    To create the OpenXmlHelper class, do the following steps:
    1. Open Visual Studio.
    2. Create new C# class library project called OpenXmlHelper.
    3. Ensure that signing is enabled on the project, as the assembly needs to have a strong name key.
    4. Reference the DocumentFormat.OpenXml.dll from the Open XML SDK. The default installation is typically in the following location: C:\Program Files (x86)\Open XML SDK\V2.0\lib\DocumentFormat.OpenXml.dll.
    5. Rename Class1 to OpenXmlHelper.
    6. Add a using statement DocumentFormat.OpenXml to the file.
    7. Create the method: AppendChild by copying the following code.

    public static bool AppendChild(OpenXmlElement parent, OpenXmlElement child)
    {
      if (parent.HasChildren && parent.Contains(child))
      {
        return false;
      }
      parent.AppendChild(child);
      return true;
    }

    8. Compile and place the OpenXmlHelper in an OpenXML Add-ins folder for the client and server. The default installation will point to the following locations: C:\Program Files (x86)\Microsoft Dynamics NAV\70\RoleTailored Client\Add-ins\OpenXML and C:\Program Files\Microsoft Dynamics NAV\70\Service\Add-ins\OpenXML.
    9. Import the ExcelBuffer Extensibility codeunit (attached) and compile. This codeunit opens up to add decorations as well as download the file to the client.

    The first part of the codeunit is the same as in Excel buffer that we used in the blog post Excel Buffer Using Open XML Instead of Excel Automation - (Part 1 of 2), but I have added the workbookwriter. In addition, instead of opening the file in Excel I use the FileMangement codeunit functionality to download the file from the server to the client, to show a different way of working with the generated file.
     
    // Create new method on ExcelBuffer table to expose the WorkbookWriter.
    ExcelBuffer.GetWorkbookWriter(WrkbookWriter);
     
    // Call method that adds new font with a set of new characters.
    AddingFont(FontDecorator);
     
    // Add a new cell Formula using the new fontdecorator.
                WrkbookWriter.FirstWorksheet.SetCellFormula(4,'A','SUM(A2:A3)','#,#0.0;#,#0.0',FontDecorator);
     
    ExcelBuffer.CloseBook;

    // Download the Excel file from the server to client.
    ExcelBuffer.UTgetGlobalValue('ExcelFile',FileServerName);
    FileClientName := 'C:\Temp\ClientFile.xlsx';
    FileMgt.DownloadToFile(FileServerName,FileClientName);
    MESSAGE(FileClientName);
     
    In the codeunit, there is also an example of how the AddingFont method can be used:

    // Create new Font, cloned from existing Font.
    Font := WrkbookWriter.FirstWorksheet.DefaultCellDecorator.Font.CloneNode(TRUE);
     
    // Create a new Font Color.
    FontColor := FontColor.Color;
    FontColor.Rgb := FontHexValue.HexBinaryValue('0000EEEE');
    Font.Color := FontColor;
     
    // Create a new Font Size.
    FontSize := FontSize.FontSize;
    FontSize.Val := FontSizeDoubleValue.DoubleValue(30);
    Font.FontSize := FontSize;
     
    // Get the collection of Fonts that already exists.
    Fonts := WrkbookWriter.Workbook.WorkbookPart.WorkbookStylesPart.Stylesheet.Fonts;
     
    // Add the new font to the collection of fonts and increase the number of fonts by one.
    IF OpenXmlHelper.AppendChild(Fonts,Font) THEN
    Fonts.Count.Value := Fonts.Count.Value + 1;
     
    // Add the Font to a decorator.
    Decorator := WrkbookWriter.FirstWorksheet.DefaultCellDecorator;
    Decorator.Font := Font;
     
    Running the codeunit will save the file on the client in the following file: C:\temp\clientfile.xlsx. In the spreadsheet, the number is now formatted to a larger font and color.

    From here, it's only up to your own imagination and needs for how you want to extend with more methods, and so forth.

    The capability of the Open XML SDK API is your only limitation.

    -Lars-Bo Christensen

  • Microsoft Dynamics NAV Team Blog

    Customers and Partners Save Time when Using RapidStart Services for Microsoft Dynamics NAV

    • 0 Comments

    RapidStart Services for Microsoft Dynamics NAV is an integrated tool and a native part of Microsoft Dynamics NAV that helps speed up the implementation process and facilitates better control of the whole process. It includes Configuration Packages, Project Overview, Questionnaires, and Master Data Import.

     

    TRIMIT gains complete control of the implementation process

    RapidStart Services for Microsoft Dynamics NAV helps TRIMIT Fashion provide a complete setup of a new company. TRIMIT use it to configure the application. It gives them an overview of which areas are being processed and which are already completed, who is responsible for setting up an application area and what else will be affected by the specifics of the setup.

    Better overview promotes better communication

    Kitty Bisseling, Partner Supporter at TRIMIT, finds that “using the Project Overview, the customer is able to get a better overview of the setup work that still needs to be done.”

    According to Alexander Pontoppidan Thyssen, Business Consultant at CORNATOR, RapidStart Services streamlines communication: “RapidStart Services has helped improve communication both internally as well as externally because people tend to be more aligned with the “why” and the “how” when they address the issues and challenges that they come across when implementing,” Thyssen says.

    Standardization saves time

    RapidStart Services comes with a standardized Configuration Package with out-of-the-box general setup data, such as currency codes, posting groups, VAT templates, chart of accounts, payment terms, and countries.

    For their TRIMIT Fashion solution, TRIMIT has also extended it with Configuration Packages specifically for Fashion Wholesale companies. This extends the pre-set data with fashion-specific data templates of Matrices for Color and Sizes. The standardized Configuration Packages shortens the implementation time for TRIMIT’s customers by providing them with predefined fashion-specific colors, sizes, washing label descriptions and more.

    Especially for smaller companies, the whole setup of a new Company can be adopted, so the customers can start up very quickly; this really saves time for the customer and for the consultant,” says Bisseling.

    The standardized Configuration Packages have improved efficiency for CORNATOR’s customers: “Knowledge and thereby efficiency is in general improved across departments and between consultants, because we use the same data foundation across implementations”, says Thyssen.

    Shorter learning curve

    RapidStart Services also includes Questionnaires, which TRIMIT has used to ask specific questions about the fashion company being setup. By offering out-of-the-box questionnaires, RapidStart Services makes it possible for everyone to start up their own company with only minimal training required.

    It is also a great tool for guiding the customers to what they need to do; even when the consultant is not present,” Bisseling says.

    Greater flexibility for the future

    RapidStart Services for Microsoft Dynamics NAV is a native part of the product, which means that it is available both on-premise and in the cloud, giving customers more flexibility. Bisseling believes that in the future, when more companies start to adopt the SaaS concept as a way of working with more standard and less customized functionality, RapidStart Services will help guide their customers through the implementation process.

     


    TRIMIT is an ISV (Independent Software Vendor) and a Gold Certified Microsoft Dynamics NAV Partner specialized in fashion, furniture, product configuration, and trade and distribution. TRIMIT, an industry solution designed and built within Microsoft Dynamics NAV, enhances the ERP solution with a wealth of industry-specific functionality to manage design, cuts, colors, sizes, and more. The ERP system also integrates with Microsoft Excel for reporting and business planning and with Microsoft Word for importing customer information automatically into forms, letters, and marketing communications. The TRIMIT Solution helps fashion and furniture Companies handle a greater number of product variants by simplifying product configuration. Together, Microsoft Dynamics NAV and the industry solution, TRIMIT help companies run their business by providing them with configured Master Data Templates, including Matrices for Color and Sizes.

    In 2008, the company CORNATOR divided into two independent companies, CORNATOR and TRIMIT. CORNATOR continued to support the Danish market as a VAR (Value Added Reseller), and TRIMIT continued to develop "state of the art" functionality for TRIMIT solutions and to build an international partnership strategy that focuses on the fashion and furniture industries. All 70 employees of  CORNATOR work with Microsoft Dynamics NAV.

  • Microsoft Dynamics NAV Team Blog

    Technical videos for Microsoft Dynamics NAV 2013

    • 0 Comments

    The Microsoft Dynamics NAV support team have posted videos on YouTube that illustrate various aspects of deployment and configuration of Microsoft Dynamics NAV 2013, including tips for how to extend the core product. You can share the videos with other partners, and with your customers - they are the same videos that our internal supporters have been able to consume for a while, and we hope you will enjoy them as much as we do.

    The following table lists the videos that are currently available - note that more videos may be made available later, so make sure you check to see later!

    Video

    Description

    Microsoft Dynamics NAV 2013 –   Technical – NAV Cluster

    This video shows how Microsoft Dynamics NAV 2013 behaves with NLB Clustering in a three-tier setup.

    Microsoft Dynamics NAV 2013 – Technical – Unicode

    This Video shows what’s new in Microsoft Dynamics NAV 2013 for Unicode and how it works for Unicode data.

    Microsoft Dynamics NAV 2013 –  Technical – SharePoint

    This video explains how-to set up, configure and use the new Microsoft Dynamics NAV 2013 SharePoint client. It also highlights some of the client’s features as well as tips to debug the client using commonly used SharePoint debug methods.

    Microsoft Dynamics NAV 2013 – Technical – SQL Filtering

    This video demonstrates the different options for filtering data that are available in the Microsoft Dynamics NAV 2013 query object.

    Microsoft Dynamics NAV 2013 – Technical – SQL Query Object

    This video demonstrates creating
      and executing a typical Query object in Microsoft Dynamics NAV 2013.

    Microsoft Dynamics NAV 2013 – Technical – SQL Queries with C/AL Code

    This video demonstrates how to use a Microsoft Dynamics NAV 2013 query object in your C/AL code, including best practices tips.

    Microsoft Dynamics NAV 2013 – Technical – SQL Joining Tables

    This video demonstrates how to join multiple data items (tables) and filter results with a Microsoft Dynamics NAV 2013 query object.

    Microsoft Dynamics NAV 2013 – Technical – Charts

    This video shows how to create and modify a generic chart, and how to make a simple extended chart.

     

    Best regards,

     

    The Microsoft Dynamics NAV support team

     

  • Microsoft Dynamics NAV Team Blog

    Partners Meet Customer Demand for Faster Implementation

    • 0 Comments

    “Our setup time is down from more than a week to only a few hours using RapidStart Services for Microsoft Dynamics NAV”

    RapidStart Services for Microsoft Dynamics NAV has helped Microsoft partner, Abakion, deploy their Purchase Order Management solution much faster. A standard setup used to take them over a week. With RapidStart Services, implementation time is only a few hours.

    RapidStart Services for Microsoft Dynamics NAV was introduced in response to customer demand for faster implementation. Customers want to hear that it’s easy to convert data, so their transition to their  new ERP system will be smooth,” says Claus Lundstrøm, Senior Product Manager at Abakion.

    What’s the big idea?

    The idea behind RapidStart Services was to enable companies to complete a setup with minimal training and to use ready-to-use data templates. This shortens the implementation time and allows  customers to focus on their business, rather than getting caught up in a time-consuming system switch.

    RapidStart Services, an integrated part of Microsoft Dynamics NAV, comes with standardized Configuration Packages and Questionnaires that make the Whole process faster. It also provides customers with a project overview and the ability to automate importing data from their old system using Master Data Import.

    Data import is no longer a hassle

    Abakion started using RapidStart Services for Microsoft Dynamics NAV to shorten their setup process and respond to the competitive situation.

    “We learned how to use it quickly, and it has decreased our implementation time dramatically. Our Purchase Order Management add-on is now installed and configured at a customer site in only a few hours,” says Lundstrøm.

    Abakion now uses Master Data Import to configure and set up their solution. Not only is the data imported, but all the details are taken care of as well. The company-specific imported data includes both user access rights and roles to determine what users have access to according to the role assigned to them.

    “If the data could not be imported with RapidStart, it would take at least a week to setup manually,” Lundstrøm says.

    Configuration templates save a lot of time

    Companies can use out-of-the-box Configuration Packages in RapidStart Services in order to save time. This makes it fast and easy to configure generic data, such as currency codes, posting groups, VAT templates, chart of accounts, payment terms, and countries.

    Existing Configuration Packages can always be extended later on, if needed. Companies can also choose to import their own customized Configuration Packages using Master Data Import.

    Abakion used their own customized text templates and specific text for multiple languages, importing 30 different text templates in multiple languages.

    About Abakion’s Purchase Order Management solution

    Abakion’s Purchase Order Management is an add-on solution built on Microsoft Dynamics NAV, which allows for control over the changes in purchase orders within the environment of a portal hosted on Microsoft Azure.

    Once the quotes/orders are created by the purchaser, they are then available in the portal, where vendors can update the information about a quote/order.

    “Then, via the portal, the vendor can inform the purchaser if he can deliver on time. If he can only partially deliver, he can make changes to the order or quote,” says Lundstrøm,

    The purchaser is automatically informed about all changes in Microsoft Dynamics NAV and can take necessary actions by looking at the overview of outstanding quotes and orders.

     

  • Microsoft Dynamics NAV Team Blog

    Disassembly in Microsoft Dynamics NAV 2013 Assembly Management

    • 0 Comments

    Assembly Management was released as part of Microsoft Dynamics NAV 2013, and it includes a set of features designed for companies that supply products to their customers by
    combining components in simple processes, such as assembly, light manufacturing, and kitting.

    Kitting and Assembly Management

    Before the Microsoft Dynamics NAV 2013 release, customers and partners in selected regions and countries, such as North America, France, and Australia, may have been familiar with a similar local functionality called Kitting. The uptake of Kitting  in those geographies has been both the driver and inspiration behind the global Assembly Management feature. Its value proposition and the functional breadth have been closely investigated and appreciated by the NAV core development team, resulting in Kitting’s key business and user requirements laying the conceptual foundation for the new Assembly Management feature.

    To ensure the quality of the new global Assembly Management feature as well as its solid integration into the existing supply chain suite, the core development team produced a
    physical and conceptual design that differed significantly from the one in Kitting. The differences are many. While Kitting used the BOM journal to manage the assembly process, Assembly Management operates with the concept of assembly order, which offers more functional flexibility, better user interface and extensibility. Last, but not least, assembly order offers more superior integration points to the rest of inventory, such as availability calculations and order promising, item tracking, supply planning,  warehousing, and costing. This is understandable because the BOM journal, like any other journal in the application, is different from an order in its flexibility and scope, with the BOM Journal’s main goal being to support users in quick data entry for a subset of specialized transactions, while bypassing any auxiliary inventory processes.

     Disassembly

    With the introduction of the assembly order, the BOM journal was deemed unnecessary. This also meant that a disassembly process, which the BOM journal partially supported, would
    have to be redesigned in Assembly Management along the same principles as the common assembly process. More specifically, a disassembly order to manage a reverse conversion process, i.e. from one item to many, would need to be added and integrated to the same supply chain features that the assembly order integrates to (see above). The disassembly order was not included in Microsoft Dynamics NAV 2013.
    Customers, who assemble their items themselves (as opposed to purchasing them from outside or getting them back through returns), and who need to reverse the previously made assembly, can use the new Undo Assembly function.

    The option of keeping the BOM journal in the application for the sake of disassembly was rejected for several reasons:

    a) Though useful in some scenarios, the actual BOM journal support for a disassembly process was limited to automatic creation of negative and positive adjustments for finished items and components respectively.

    b) Its handling of cost flows required serious improvement.

    c) As pointed out earlier, a journal line offers no integration to other parts of the inventory processes.

    The core development team will be evaluating the possibility of including a properly designed disassembly feature in the future NAV releases. Kitting customers that used the BOM journal for their disassembly tasks should approach their partners for a discussion of reintroducing a journal for disassembly scenarios. The core development team will make no  design recommendations in this regard.

    For more information, see Assemble Items in the MSDN Library.

    Best regards,

    The NAV Supply Chain team

  • Microsoft Dynamics NAV Team Blog

    Microsoft Dynamics NAV 2013 Management Pack for System Center

    • 0 Comments

    In the past few months we talked to many hosting companies across several countries which deal with Microsoft Dynamics NAV hosting. They all are confirming that the new platform capabilities of Microsoft Dynamics NAV 2013 are making the product much easier to deploy and
    maintain.

    The tools that are essential for the companies dealing with volume deployment of Microsoft Dynamics NAV 2013 include:

    • Flexible authentication capabilities
    • Streamlined 2- and 3-tier deployment
    • Windows PowerShell cmdlets to allow advanced scripting of repeated tasks
    • Management Console user interface built on top of PowerShell cmdlets
    • The ability to deploy the Microsoft Dynamics NAV Windows client using ClickOnce technology

    We also gained insight into the typical hosted Microsoft Dynamics NAV incidents. One of the biggest cost factors for companies dealing with a variety of products, not only from Microsoft, but also from multiple third-party software providers, was support and troubleshooting – finding the root cause faster and being able to see which product is causing problems to relay the support incident to the right support professional.

    Many of these companies chose to use the Microsoft System Center platform to manage their virtual, physical, and cloud IT environments. This is a single end-to-end service management solution to handle infrastructure, service delivery, automation, and applications that is easy to customize and extend.

    The way to extend this management platform to recognize and maintain all kinds of software and hardware is to use Management Packs (MPs) developed for them. Management Packs are the building blocks which extend Operations Manager capabilities to operating systems, applications, and other technology components. An MP contains best practice knowledge to discover, monitor, troubleshoot, report on, and resolve problems for a specific technology component.

    Microsoft provides MPs for more than 60 Microsoft products and Windows components. There are more than 500 Microsoft Partner Management Packs covering most technologies used by organizations today.

    We are pleased to announce that a Microsoft Dynamics NAV 2013 Management Pack for System Center is now available for download for all IT professionals working with System Center 2007 R2 Operations Manager or System Center 2012 Operations Manager components of the Microsoft System Center.

    This extension package provides Microsoft System Center Operations Manager users with the ability to detect and monitor computer systems running Microsoft Dynamics NAV 2013, including the following components:

    • Computers on which Microsoft Dynamics NAV Server is installed and Microsoft Dynamics NAV Server instances are installed.
    • Computers on which Microsoft Dynamics NAV Web Server components are installed. These include the websites for the Microsoft Dynamics NAV Web client.

    Companies providing hosting services to Microsoft Dynamics NAV Partners now have a toolset for extending their offering with Microsoft Dynamics NAV-specific monitoring and basic troubleshooting.

    Microsoft Dynamics NAV 2013 Management Pack for System Center enables Operations and IT Management teams to easily identify and resolve issues affecting the health of numerous distributed Microsoft Dynamics NAV 2013 installations. It lowers client support costs by surfacing critical statistics and alerts in context of running Microsoft Dynamics NAV 2013 components. It also reduces IT management complexity by automating routine administration and providing basic actions for working with Microsoft Dynamics NAV 2013 components.

     

    On a final note, we would like to thank all the companies who shared their experience and provided their feedback to our R&D team. This feedback is extremely valuable and greatly appreciated.

     

    - The Microsoft Dynamics NAV Product Marketing team 

     

  • Microsoft Dynamics NAV Team Blog

    New Management Admin Cmdlets

    • 0 Comments

    Windows PowerShell is becoming ever more used in the professional IT organization, and in Microsoft Dynamics NAV we are continuously extending and improving the set of administration management PowerShell cmdlets.

    With hotfix 2791548, we introduce these additions and updates, all fully backward compatible with cmdlets shipped with Microsoft Dynamics NAV 2013:

    • New-NAVServerInstance
      • Creates a new Microsoft Dynamics NAV Server instance - new parameters
    • New-NAVWebServerInstance
      • Creates a new Microsoft Dynamics NAV Web Server instance and binds this instance to a Microsoft Dynamics NAV Server instance - new
    • New-NAVDatabase
      • Creates a new Microsoft Dynamics NAV database from a backup file - new
    • Rename-NAVCompany
      • Renames a company in a Microsoft Dynamics NAV database - new

    Note

    To use the new and changed cmdlets, you must obtain the relevant hotfix through your Microsoft Dynamics NAV support contact. For more information, see the KnowledgeBase article for the hotfix (requires access to PartnerSource/CustomerSource).

    The rest of this blog post describes the cmdlets at a summary level. The full documentation is available on the MSDN Library. Additional documentation is available at Microsoft Dynamics NAV Windows PowerShell Cmdlets.

    New-NAVServerInstance

    Creates a new Microsoft Dynamics NAV Server instance.

    Syntax

    Parameter Set: __AllParameterSets

    New-NAVServerInstance [-ServerInstance] <String> -ManagementServicesPort <ServicePort> [-ClientServicesCertificateThumbprint <String> ] [-ClientServicesCredentialType <String> ] [-ClientServicesPort <ServicePort> ] [-DatabaseInstance <String> ] [-DatabaseName <String> ] [-DatabaseServer <String> ] [-ODataServicesPort <ServicePort> ] [-ServiceAccount {<LocalService> | <NetworkService> | <LocalSystem> | <User>} ] [-ServiceAccountCredential <PSCredential> ] [-SOAPServicesPort <ServicePort> ] [ <CommonParameters>]

    Detailed Description

    Use the New-NAVServerInstance cmdlet to create a new Microsoft Dynamics NAV Server instance. You must specify a name for the instance, in addition to values for the four port parameters. All other configuration values for the new instance are based on default values. Make sure that you verify the DatabaseServer and DatabaseName values after the instance is created, to ensure that the instance can accept client requests.
    All permissions that are required for the instance to start are configured automatically.

    See Also

     For more information, see New-NAVServerInstance on the MSDN Library.

    Examples

    Example 1

    This example creates a new Microsoft Dynamics NAV Server instance. It configures the necessary firewall exceptions and performs the necessary Access Control List registrations.

    // Copyright © Microsoft Corporation. All Rights Reserved.

    // This code released under the terms of the

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

     

    C:\PS>New-NAVServerInstance NewInstance -ManagementServicesPort 8099 -ClientServicesPort 8100 -SOAPServicesPort 8101 -ODataServicesPort 8102 –verbose

     

    VERBOSE: NavCommand.BeginProcessing

    VERBOSE: NavCommand.ProcessRecord

    VERBOSE: Creating Instance directory C:\Program Files (x86)\Microsoft Dynamics NAV\70\Service\Instances\NewInstance

    VERBOSE: Adding Windows Firewall (and UrlAcl) rules for Server Instance MicrosoftDynamicsNavServer$NewNAVServer

    VERBOSE: Adding Windows Firewall (and UrlAcl) rules for Server Instance MicrosoftDynamicsNavServer$NewNAVServer

    VERBOSE: Adding Windows Firewall (and UrlAcl) rules for Server Instance MicrosoftDynamicsNavServer$NewNAVServer

    VERBOSE: Adding Windows Firewall (and UrlAcl) rules for Server Instance MicrosoftDynamicsNavServer$NewNAVServer

    VERBOSE: NavCommand.EndProcessing

    Example 2

    This example prompts for ServiceAccount credentials and then creates a new Microsoft Dynamics NAV Server instance.

    // Copyright © Microsoft Corporation. All Rights Reserved.

    // This code released under the terms of the

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

     

    C:\PS>Get-Credential | New-NAVServerInstance NewInstance -ServiceAccount User -ManagementServicesPort 8099 -ClientServicesPort 8100 -SOAPServicesPort 8101 -ODataServicesPort 8102 –verbose

     

    VERBOSE: NavCommand.BeginProcessing

    VERBOSE: NavCommand.ProcessRecord

    VERBOSE: Creating Instance directory C:\Program Files (x86)\Microsoft Dynamics NAV\70\Service\Instances\NewInstance

    VERBOSE: Adding Windows Firewall (and UrlAcl) rules for Server Instance MicrosoftDynamicsNavServer$NewNAVServer

    VERBOSE: Adding Windows Firewall (and UrlAcl) rules for Server Instance MicrosoftDynamicsNavServer$NewNAVServer

    VERBOSE: Adding Windows Firewall (and UrlAcl) rules for Server Instance MicrosoftDynamicsNavServer$NewNAVServer

    VERBOSE: Adding Windows Firewall (and UrlAcl) rules for Server Instance MicrosoftDynamicsNavServer$NewNAVServer

    VERBOSE: NavCommand.EndProcessing

     

    New-NAVWebServerInstance

    Creates a new Microsoft Dynamics NAV Web Server instance and binds this instance to a Microsoft Dynamics NAV Server instance.

    Syntax

    Parameter Set: Default

    New-NAVWebServerInstance -Server <String> -ServerInstance <String> -WebServerInstance <String> [-ClientServicesCredentialType <String> ] [-ClientServicesPort <String> ] [-DnsIdentity <String> ] [ <CommonParameters>]

    Detailed Description

    Use the New-NAVWebServerInstance cmdlet to create a new Microsoft Dynamics NAV Web Server instance and bind this instance to a Microsoft Dynamics NAV Server instance on the same computer or on a remote
    computer. If you call this cmdlet multiple times then multiple instances of the Microsoft Dynamics NAV Web Server are created. Each instance of the Microsoft Dynamics NAV Web Server is created as an IIS Web application under a generic Microsoft Dynamics NAV Web Server web site.

    See Also

    For more information, see New-NAVWebServerInstance on the MSDN Library.

     

    New-NAVDatabase

    Creates a new Microsoft Dynamics NAV database from a backup file.

    Syntax

    Parameter Set: __AllParameterSets

    New-NAVDatabase [-FilePath] <String> -DatabaseName <String> [-DatabaseInstance <String> ] [-DatabaseServer <String> ] [-Force] [-ServiceAccount <String> ] [ <CommonParameters>]

     

    Parameter Set: MultipleDestinations

    New-NAVDatabase [-FilePath] <String> -DatabaseName <String> -DataFilesDestinationPath <String> -LogFilesDestinationPath <String> [-DatabaseInstance <String> ] [-DatabaseServer <String> ] [-Force] [-ServiceAccount <String> ] [ <CommonParameters>]

     

    Parameter Set: SingleDestination

    New-NAVDatabase [-FilePath] <String> -DatabaseName <String> -DestinationPath <String> [-DatabaseInstance <String> ] [-DatabaseServer <String> ] [-Force] [-ServiceAccount <String> ] [ <CommonParameters>]

    Detailed Description

    Use the New-NAVDatabase cmdlet to restore a database from a backup file. You can specify the location of transaction log files and data files.

    You can use this cmdlet to restore a database to a remote SQL Server instance or to a SQL Server instance that is running on the same computer on which you run the cmdlet.

    See Also

    For more information, see New-NAVDatabase on the MSDN Library.

    Examples

    Example 1

    This example restores a database and preserves the original file names and locations.

    // Copyright © Microsoft Corporation. All Rights Reserved.

    // This code released under the terms of the

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

     

    New-NAVDatabase C:\Backups\backup1.bak –DatabaseName NewDatabase –Verbose | fl

     

    VERBOSE: NavCommand.BeginProcessing

    VERBOSE: NavCommand.ProcessRecord

    VERBOSE: Restoring database 'NewDatabase' from backup file: 'C:\Backups\backup1.bak'...

    VERBOSE: Restore of database 'NewDatabase' from file 'C:\Backups\backup1.bak' has been completed successfully.


    DatabaseName : NewDatabase

    DatabaseInstance : MSSQLSERVER

    DatabaseServer : server1.cronus.com



    VERBOSE: NavCommand.EndProcessing

    Example 2

    This example restores a database, moves transaction log files and data files to the new location 'C:\newdestination', and preserves the original file names.

    // Copyright © Microsoft Corporation. All Rights Reserved.

    // This code released under the terms of the

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

     

    New-NAVDatabase C:\Backups\backup.bak -DestinationPath c:\newdestination -DatabaseName NewDatabase –Verbose

     

    VERBOSE: NavCommand.BeginProcessing

    VERBOSE: NavCommand.ProcessRecord

    VERBOSE: Restoring database 'NewDatabase' from backup file: 'C:\Backups\backup.bak'...

    VERBOSE: Restore of database 'NewDatabase' from file 'C:\Backups\backup.bak' has been completed successfully.


    DatabaseName DatabaseInstance DatabaseServer

    ------------ ---------------- --------------

    NewDatabase MSSQLSERVER server1.cronus.com

    VERBOSE: NavCommand.EndProcessing 

     

    Rename-NAVCompany

    Renames a company in a Microsoft Dynamics NAV database.

    Syntax

    Parameter Set: Default

    Rename-NAVCompany -CompanyName <String> -DatabaseName <String> -NewCompanyName <String> [-DatabaseInstance <String> ] [-DatabaseServer <String> ] [-ErrorLogFileName <String> ] [ <CommonParameters>]

    Detailed Description

    Use the Rename-NAVCompany cmdlet to rename a company in a Microsoft Dynamics NAV database.

    See Also

    For more information, see Rename-NAVCompany on the MSDN Library.

    Examples

    Example 1

    This example renames the company Cronus Ltd. in the Cronus database to MyCompany.

    // Copyright © Microsoft Corporation. All Rights Reserved.

    // This code released under the terms of the

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

     

    Rename-NAVCompany -DatabaseName Cronus -CompanyName "Cronus Ltd." -NewCompanyName MyCompany –Verbose

     

    VERBOSE: NavCommand.BeginProcessing

    VERBOSE: NavCommand.ProcessRecord

    VERBOSE: Renaming company 'Cronus Ltd.' to 'MyCompany' ...


    VERBOSE: Renaming of company 'Cronus Ltd.' to 'MyCompany' has completed successfully.

    VERBOSE: NavCommand.EndProcessing

    Example 2

    This example renames the company Cronus Ltd. in the Cronus database to MyCompany. Errors are logged to the file C:\NavDatabases\ErrorLog.txt.

    Rename-NAVCompany -DatabaseName Cronus -CompanyName "Cronus Ltd." -NewCompanyName MyCompany -ErrorLogFileName C:\NavDatabases\ErrorLog.txt

     

    - Morten Jensen and the rest of the Microsoft Dynamics NAV Management Tools team

     

  • Microsoft Dynamics NAV Team Blog

    Assembly Management versus Manufacturing in Microsoft Dynamics NAV 2013

    • 0 Comments

    As many of you may know, Microsoft Dynamics NAV 2013 includes a new application feature called Assembly Management. It is described as a set of features designed for companies that supply products to their customers by combining components in simple processes, such as assembly, light manufacturing, and kitting.

    At this point it may be tempting to ask yourself and your sales consultant: with this definition, isn't Assembly Management in essence the same as Manufacturing? That’s a fair question that will be raised in many sales and implementation situations.

    The quick answer is yes, it certainly is, insofar as it belongs to the same category of business processes that represent the conversion of a set of products into a different or new product: Manufacturing typically concerns itself with converting (changing the physical nature of) raw materials into finished goods, kitting puts together end-products into a sellable unit, and assembly is often a hybrid of the two.

    Now, as the standard application suite for Microsoft Dynamics NAV 2013 includes both Manufacturing and Assembly, how are we to know the subtle difference between the two and to decide which module fits the business and project budget best? Here is some guidance.

    Let's start from reminding ourselves that Microsoft Dynamics NAV Manufacturing is a rich functionality that covers a broad selection of discrete production processes and industrial demands. It is meant for manufacturers that operate with multi-stage production processes, with specialized activities at each work operation, long production lead times that result in WIP, versions of BOMs, and have a need for capacity load optimization and control.

    Theoretically, of course, with the right setup and user training, Manufacturing feature set could also support lighter production and assembly processes. However, the fact is that due to its scope, complexity, maintainability, price, and sometimes, lack of partners' expertise in the area, customers, especially in the small and mid-size segment, have been walking away from the Manufacturing solution. It is simply not suitable or cost-efficient for them. At those customers, an assembly task often means picking a set of items and packing them into one box that is sold as a kit, making the “production process” a part of regular warehouse operations. For other businesses, the work and labor involved in producing a final assembly is relatively short and consists of very few simple operations that do not warrant the setup and control of work centers, routings, or capacity load calculations.

    Those light manufacturers, wholesalers, and retailers are looking for a simple manufacturing solution that allows them to manage the conversion process through one-entry-point interface, with minimal setup effort, using employees without university degrees in production engineering, and for an affordable price. And they are the target audience for the new Assembly Management functionality. The assembly granule is included in the Starter license package, comes with minimum setup requirements, supports companies that run both assemble-to-order and assemble-to-stock processes, and is fully integrated with the entire Microsoft Dynamics NAV supply chain suite.

    This is also good news for existing customers with assembly and kitting needs, who in the past had little choice but to get the basic Sales BOM journal (as part of Starter license package) and then buy consulting and customization hours from their partner to bring the solution to the desired functional level. Admittedly, this approach did not represent an ideal situation. Partners would in effect have to first build a basic horizontal foundation for the assembly/kit process (as simple as it may be, it is still a manufacturing process) before taking it further into a vertical (if time and budget permitted). Many partners acknowledged that solutions built this way are poorly integrated and remain at the core level rather than support vertical industry needs.

    So, with Assembly Management joining the total supply chain offering, new and existing customers will now have more options to consider when deciding what “manufacturing” functionality they need and how much to pay for it. What we have also understood is that at its heart, the new Assembly Management has the same conversion process as a true manufacturing module – it just has a lesser scope, simpler interface, fewer setup options and maintenance requirements, and is cheaper. With this in mind and especially with regard to the latter, should we now not expect that the same license alternatives will also be considered by the manufacturers, who will be tempted to shy away from the core Manufacturing functionality?

    Tempted, yes, but upon closer examination and with partner guidance, customers engaged in full-blown manufacturing activities will come to see that Assembly Management may not be the right solution for them. The least desirable situation to find yourself in would be to choose the assembly module and then start paying your partner to beef up the Assembly Management feature, for example, to allow BOM versioning, or to enable work-in-process management, or to support multi-stage production processes. By design, the Assembly Management feature safeguards its conceptual boundaries and protects it from being turned into a full-scope manufacturing.

    This is not to suggest that manufacturers shall not be interested in Assembly Management. It is easy to imagine an operational setting where a company will rely on manufacturing modules to support their production activities and then use the assembly feature, to-stock or to-order, when selling the produced products in sets or kits to its customers. Moreover, an item's production BOM may include a subassembly with assembly BOM, an efficient way to ready several components for a work center as one set.

    -Olga T. Mulvad

  • Microsoft Dynamics NAV Team Blog

    How to Get your ERP System Up and Running in No Time

    • 0 Comments

    Introducing RapidStart Services for Microsoft Dynamics NAV

    If the phrase “IT implementation project” makes your palms sweat and your heart beat faster, this blog entry should be good news. It’s about a new service that we developed as a direct result of customer feedback. We listened when customers told us that a simpler and faster deployment would mean a lot to them. And we know how important it is for you to be able to stay focused on your business.

    That’s why we built special functionality that improves the implementation process -- right in the Microsoft Dynamics NAV solution. Functionality that makes the entire process smooth. RapidStart Services for Microsoft Dynamics NAV accelerates deployment time, improves the quality of the implementation, gives you better control of the whole process and reduces the cost. Here’s why.

    RapidStart Services for Microsoft Dynamics NAV actively involves you in a way that makes the entire implementation process transparent. So not only is the implementation fast, but equally important, it is of the highest quality,

    Simplifies Configuration and Data Migration

    The new services include four main types of tools that simplify data migration and configuration and ensure that the quality of the data stays intact:

    1. Questionnaires – These forms make it easy to set up your company in the system with specific company data, like contact and bank information, for example. You simply answer a few straightforward questions about your company, and Microsoft Dynamics NAV is set up according to your needs.
    2. The Configuration Worksheet – This worksheet helps partners and customers bring structure to the process. It serves as a kind of implementation control center providing immediate access to all the essential setup tables.
    3. Data Migration Tools – RapidStart Services also simplifies the process of migrating existing data. You gain control because you actively participate using the familiar Microsoft Excel program. It makes it easy for you to select and clean up your data before it is imported, thus ensuring better data quality.
    4. A standardized Configuration Package – The package includes general setup data, such as currency codes, Chart of Accounts, payment terms, and countries. And if the standard data packages aren´t enough, you can always import additional data packages or extend existing ones after the initial setup.

    A Good Overview and Better Control

    The RapidStart Services Role Center gives you a good overview of the setup status. And in more advanced deployments, it allows you to assign a certain set of questions to a specific person. That way you can follow up if questions are not answered in time.

    Now, you’re probably wondering if this streamlined service is only available on-premise. Well we’re happy to offer RapidStart Services for Microsoft Dynamics NAV as a native part of the product. So, it’s supported in both on-premise and in the cloud, for greater flexibility.

    Does RapidStart Services for Microsoft Dynamics NAV sound interesting?

    Do you want to take advantage of the reduced cost of deployment and accelerated deployment time? Then, contact your partner and ask to learn more about how you can get your solution up and running in no time and with better control over the process. See more in this video. If you are a partner, learn more about resources and materials for RapidStart Services for Microsoft Dynamics NAV here (PartnerSource login and password required).

Page 35 of 51 (764 items) «3334353637»