October, 2007

  • Microsoft Dynamics NAV Team Blog

    How to use the new Employee Portal with Microsoft Dynamics NAV 4.0 SP3

    • 0 Comments

    The Released Employee Portal can also work with NAV 4.0 SP3. If you want to run the new employee portal with NAV 4.0 SP3, you need to turn off the compression. This is because the compressions work differently on .NET Framework 1.1 and 2.0. Normal communication and encrypted communication is working fine. Partners will have to remove the compression in NAV and in the web.config of the portal. 

     

    1.       Remove the “Use compression” check mark in NAV

     

    ·         To do this, open your NAV client and select the menu entry

    ·         “Administration” – “Application Setup” – “Employee Portal” and click on the link to

    ·         “Application Server Setup”

    ·         The Application Server Setup card opens. Now navigate to the correct NAS record and uncheck the “Use compression” checkbox (see the following screenshot).

     

    2.       Remove the compression from the web.config of your SharePoint portal

     

    ·         On your machine running the SharePoint services please open the Windows Explorer and navigate to the root path of your site (e.g. C:\Inetpub\wwwroot\wss\VirtualDirectories\80) and open the web.config file.

    ·         Go to the end of the file to the block “appSettings”.

    ·         Change the value of the node “UseCompression” from “1” to “0”.

     

    Mtoo Norrild

    Program Manager

  • Microsoft Dynamics NAV Team Blog

    Employee Portal for Microsoft Dynamics NAV 5.0

    • 0 Comments

    I am pleased to announce the update of Employee Portal for Microsoft Dynamics NAV 5.0. This update is now available for you to download at PartnerSource ,login credentials are required.

    Employee Portal for Microsoft Dynamics NAV 5.0 includes all the known functionality from earlier versions of Employee Portal and in addition supports Windows SharePoint Services 3.0 (WSS 3.0) and Microsoft Office SharePoint Server 2007 (MOSS 2007).

    From the link above we have released:

    • Product for download
    • Fact Sheet to support the sales process
    • Installation Guide to support installation

    Mtoo Norrild

    Program Manager

  • Microsoft Dynamics NAV Team Blog

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

    • 15 Comments

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    Darren Laybourn

  • Microsoft Dynamics NAV Team Blog

    Platform Roll-up Update for Microsoft Dynamics NAV 5.0

    • 0 Comments

    I am pleased to announce that the first platform update is now available for Microsoft Dynamics NAV 5.0. You can receive the Platform Roll-up Update for Microsoft Dynamics NAV 5.0 KB943858 by requesting it here, just fill in the KB number (943858) and submit the request.

    This update contains a wide number of error corrections for the following components:

    • The Microsoft Dynamics NAV C/SIDE client
    • NODBC
    • C/FRONT
    • NAS
    • Server

    As a reminder, Microsoft Dynamics NAV platform updates are cumulative and contain all previously released hotfixes and updates for each version of Microsoft Dynamics NAV and this update involves a technical upgrade of your Microsoft Dynamics NAV ERP database. Please notice that a technical upgrade can be a time consuming process if the database is including content of several hundred Giga bytes.

    I encourage everybody to download this update, but please notice that index hinting is turned on by default if the Microsoft Dynamics NAV SQL Option is used, see more about index hinting here.

    Martin Nielander
    Program Manager

  • Microsoft Dynamics NAV Team Blog

    Diagnose your SQL Server

    • 0 Comments

    I assume that anyone reading this will be very familiar with collecting traces with SQL Server Profiler. And be equally familiar with the two main limitations of SQL Server Profiler:

    1. It adds a big overhead to SQL Server, which is the last thing you need when troubleshooting performance problems, and
    2. How to make sense of the vast amount of data that you can end up with.

    This blog shows how to make each of these limitations much less of a problem. It is in two sections: Data collection, and Data analysis. The data collection part is very different depending on whether you run on SQL 2000 or SQL 2005. This blog focuses on SQL 2005, but there is a small section in the end about how to achieve the same on SQL 2000.


    Data collection
    There used to be (and still is) a tool called PSSDiag. PSS being "Product Services and Support", the tool was designed for support engineers to collect trace files, logs, etc from customers who may not know much about SQL Server. So the support engineer decides what data to collect, and then sends a data collection tool to the customer which is easy to start.

    In SQL 2005, this tool is now part of SQL Server, and is called SQLDiag. This is how to use it:

    From a command prompt on the SQL Server machine, go into this folder:
    C:\Program Files\Microsoft SQL Server\90\Tools\Binn\
    then type:
    sqldiag

    The tool will start up, which will take a little while. If it shows any warnings, then ignore those - as long as it starts up. Once it is ready, it will display the following in green text:
    SQLDIAG Collection started.  Press Ctrl+C to stop.

    SQLDiag will now run in the background, collecting SQL Profiler traces and other information. As default, it will collect it to a subfolder called SQLDIAG. If this folder doesn't exist, the tool will create it. Once the customer has seen enough of the problem(s) that you are troubleshooting, they just have to stop the tool (Ctrl+C), then zip the content of the SQLDIAG subfolder, and send it to the support engineer for analysis.


    There is one optional parameter that should be used for the data collection. SQLDiag uses the file SQLDiag.XML to configure which SQL Profiler events and other events to apture. As default, this file does not contain much, so you should use another configuration file. Note: You should not modify SQLDiag.XML directly, but make a copy of the file, and then modify the copy. At the moment there are no simple tools to help you with this, so unfortunately it is not too simple to change the configuration. But attached is a configuration file (PSSDiagCustom.XML) which configures SQLDiag to collect trace files that are more similar to a standard SQL Profiler trace.

    To tell SQLDiag to use this file, use the /I parameter. For example, copy the attached file into a folder called C:\SQLDiagCOnfig\. Then run SQLDiag like this:
    SQLDiag /I C:\SQLDiagCOnfig\PSSDiagCustom.XML


    Now you should be able to use SQLDiag to collect information from the customer's system. SQLDiag creates a number of files in the output folder, but here we will only look at the .trc file that it creates. This is a normal SQL Profiler trace file which you can open and analyse with SQL Server Profiler.

    You can of course make .bat files to specify the commands instead of the customer having to go to the command prompt. You can also set SQLDiag up to run as a service, and then the customer just has to start this service. Or you can schedule the service to start and stop at certain times like any other service.


    Other things to be aware of are:
      - As mentioned, the default output folder for SQLDiag is C:\Program Files\Microsoft SQL Server\90\Tools\Binn\SQLDIAG\, but you can change it with the /O parameter. But always use a folder on the SQL Server itself. If you set it to use a network location, you will add overhead to the tool.

      - SQLDiag can collect a lot of information. Expect 100s of gigabytes. So you must make sure to have a lot of free disk space available. Also, the customer should run it only long enough to reproduce the problems they have. I would recommend to run it for not more than an hour or so.

      - SQLDiag creates much less of an overhead on SQL Server than running a normal SQL Profiler trace because it does not have a user interface. Much of the overhead caused by SQL Profiler goes into displaying the collected information.


    Run "SQLDiag /?" from the command prompt to see the additional parameters that are available, or look up "SQLDiag Utility" in SQL Server online help for further information about the tool.

     

    Data analysis
    Once you have collected SQL Profiler trace(s) (whether you use SQLDiag or start a SQL Profiler trace manually), the next challenge is to analyse this. You can of course just open the trace file(s) in SQLProfiler, and then take a look. But this is not an easy way to spot the worst queries.

    Luckily, there is an easy syntax to load trace files into a SQL table, which will allow you to query the events ordered by Duration, Reads, Writes or anything else. This is the syntax:

    --Load trace files into a SQL table so it can be queried:
    SELECT * INTO temp_trc
    FROM ::fn_trace_gettable('c:\MyTrace.trc', default)


    SQLDiag will make trace files up to 350GB in size, and then create a new trace file. So you will often end up with files like this in the Output folder:
    Server__sp_trace.trc - 350GB
    Server__sp_trace.trc_1 - 350GB
    Server__sp_trace.trc_2 - 150GB

    The "default" parameter in the syntax above means that it will automatically continue with the next file. So in this example, if you run this from SQL Management studio:

    SELECT * INTO temp_trc
    FROM ::fn_trace_gettable('c:\Server__sp_trace.trc', default)

    then it will automatically read all three files into the temp_trc table.

    If you want to limit how much to read into the temp_trc table, then instead of specifying "default", specify a number which will tell it the maximum number of files to read.

    This is useful because the command can take a long time to run, and take a lot of database space. So if for example you have collected 20 trace files, then it can be necessary to read 5-10 of them at a time.


    The syntax will automatically create a new table in the current database. Once you have this table, then you can add indexes. Useful indexes would be Reads, Duration, Writes etc.

    And then you have an easy way to identify the "worst" queries, ordered by any of these, for example:

    SELECT Reads, * FROM temp_trc ORDER BY 1 DESC --or:
    SELECT Duration, * FROM temp_trc ORDER BY 1 DESC

    "ORDER BY 1" just means: Order by the first column that you specify - in the example above, Reads or Duration. This is to avoid "Ambiguous column name 'Reads'."-errors if you have both a column and an index called the same.


    So in this way you can easily sort your events by anything you need. The top events may look like this:
    exec sp_execute 380,1,'20000'

    I would advice that you ignore these events, since they don't really tell you anything. Focus on events that you can relate to the activities that you are troubleshooting.

     

    Data collection on SQL2000

    As mentioned, SQLDiag is new in SQL2005. For SQL2000 you need a tool called PSSDiag. To download it, go to support.microsoft.com and just search for "PSSDIAG data collection utility". After installing this, run the file DiagConfig.exe, which lets you decide what events to collect. This part is actually a lot simpler than with SQLDiag because you have a graphical interface here.

    Once you have decided what to collect, click the "Save" button. This will create a file called \Customer\pssd.exe which you can send to the customer. You also have simple directions in the file \docs\PSSDIAG Instructions.doc to send to the customer as well. From here, the steps to start collecting are the same as with SQLDiag.

    - Lohndorf

  • Microsoft Dynamics NAV Team Blog

    Upgrade Toolkit for Dynamics NAV 5.0 Ready and Waiting for You

    • 1 Comments

    It’s time to upgrade!  The upgrade toolkit for NAV 5.0 is available on PartnerSource. 

    The main goal of the upgrade tool itself is to convert your existing data with the old version table and field structure so it can function with the new table and field structure in the new version.  It modifies the table objects and table data as a part of the data conversion.  All other objects like forms, reports, codeunits and dataports are a part of the customization merge process and are imported during the data conversion. 

    The toolkit is more than a tool to convert your data for use in the newer version.  It also includes documentation to help guide you through the process. 

    • Upgrade Manual - Use the upgrade manual in the toolkit to walk through the steps and if you need more information or context about a particular step, flip to the appendix at the end for more detail.  Ever wonder what is actually happening in Codeunit 104045 and 104048 for steps 1 and 2?  The appendix breaks it down by function. 
    • Quick Guides – For a quick overview of the upgrade process, use a Quick Guide.  These documents break down the high-level steps and refer to the appropriate page and section in the full upgrade manual. 
    • Feature Enhancements Documents – To find out what has changed from a previous version to the new version, use the Feature Enhancement documents for an overview by granule ID. 

    The NAV 5.0 upgrade toolkit can be used to upgrade directly from 3.70 or 4.0.  If you are using a version prior to 3.70, you will need to do a two-step conversion process.  First upgrade from your current version to 4.0 using the 4.0 upgrade toolkit and then upgrade to 5.0 using the new toolkit.    

    People often ask why there are manual steps in the upgrade process.  The main reason is for flexibility.  NAV is designed to be flexible to meet the specific needs of our customers.  This flexibility to customize the way NAV is used, also means that people are using NAV data differently and need the flexibility in the way the upgrade of the data is done.  The upgrade tool will take care of most of the conversion using standard rules in a standard way, but the process also leaves room to provide flexibility. 

    Check out the NAV 5.0 Upgrade Toolkit on PartnerSource from the Microsoft Dynamics NAV 5.0 Download Page. 

    Lisa Mitchell

  • Microsoft Dynamics NAV Team Blog

    Unique IDs for ISVs

    • 0 Comments

    Problem Statement

    When you create an add-on solution, you must make sure that the new objects you create are given unique IDs (UIDs) from the range assigned to the add-on in question. This is done by using the appropriate license. There will be no problem as long as only one add-on solution is included in the developer’s license.

     

    However, if the developer’s license includes permission to create more than one add-on solution, it gets more complicated. In this case, the UIDs must be added manually during development instead of allowing them to be added automatically.

     

    One consequence of not manually applying the UIDs could be that two separate add-on solutions are given the same range of IDs. This will generate merge errors when you try to implement the two add-on solutions in the same Microsoft Dynamics NAV database.

     

    Manually setting the UIDs so that they comply with the appropriate add-on UID range is both a tedious and an error-prone task.

    Cause

    The Microsoft Dynamics NAV platform is not able to identify more than one range of unique IDs in a license.

    Resolution

    A function (with a fixed, predefined ID) can be added to codeunit 1. This function returns the base UID for the application, much like the SetGlobalLanguage function does for the application language. The function is called whenever Microsoft Dynamics NAV needs to find the base UID for the application. Starting from that base UID, the function finds the next available UID, which is then used for the new function, text constant etc in question.

     

    Notation:

    PROCEDURE GetUidOffset@212122() : Integer;

     

    Example:

    While creating an add-on solution, a developer at a Microsoft Certified Partner can change codeunit 1 (and restart Microsoft Dynamics NAV or re-open the company they’re working in – because of codeunit 1’s Single Instance-like behavior) to reflect the UID range that was assigned to the add-on in question.

     

        BEGIN

          Exit(Insert add-on solution ID here);

        END;

     

    When the partner adds a new text constant, function etc., the C/AL Editor will start at the inserted add-on solution ID and find the next available number.

    The procedure for creating an add-on solution and adding UIDs is:

    1.       Open Codeunit 1 and add PROCEDURE GetUidOffset@212122() : Integer;. This ensures that you use the appropriate add-on solution ID.

    2.       Save and compile.

    3.       Open Company.

    4.       Start developing ‘Add-on Solution 1’.

    5.       Save and compile ‘Add-on Solution 1’.

    6.       Change Codeunit 1 – delete PROCEDURE GetUidOffset@212122() : Integer;.

    7.       Save and compile Codeunit 1.

    You must repeat these steps for each separate Add-on UID range you work with.

    Known Issues

    ·         After this workaround has been implemented in codeunit 1, you must open a company in Microsoft Dynamics NAV before you open the C/AL designer. This is due to the fact that codeunit 1 is not called before you open a company.

    ·         If this workaround is not implemented when you are developing an add-on solution, the UIDs will be assigned according to the old implementation and might cause problems when you merge more than one add-on solution into a Microsoft Dynamics NAV database.

     

     - martinni

  • Microsoft Dynamics NAV Team Blog

    Exact Cost Reversal function becomes more humane in Microsoft Dynamics NAV 5.0

    • 0 Comments
    The Exact Cost Reversal function - the function that helps the users to ensure that returned items, both in sales and purchase,  are valued at exactly the same cost as the original transaction when being put back on inventory/drawn from inventory - has been available in NAV since version 3.01.

    Many NAV users are aware of and actively use this function when handling their return documents.  "All" they have to do is to fill in "Apply-from/to Item Entry" field on the order line . Or even better, checkmark the  “Exact Cost Reversing Mandatory ” field as part of S&R/P&P setup and use the Copy Document function - then the "Apply-from/to Item Entry" field on the copied return line will be filled in automatically.

    In practical terms, this seemingly easy task may turn out to be rather cumbersome and even obscure. Do a lookup in the “Apply-from Item Entry” field, and most likely you will be confronted with a huge amount of entries among which you have to find the relevant one.  Copy Document function will only allow you to copy and cost reverse posted shipment/receipt and not posted invoices.

    In NAV 5.0 release, the exact cost reversal received a usability facelift, while retaining the same core functionality.  With the new Get Posted Document Lines to Reverse functions, available on return orders and credit memos, you now:
    • can access regular documents (rather than item ledger records) and copy one or multiple lines, be they from the same or different documents
    • among the documents to copy from, will find invoices (as well as credit memos, if that's relevant) - the most logical reference document in returns situation  (see screenshot below; click to expand)
    • will not have to manually enter serial/lot numbers for the returned items - the program automatically copies item tracking lines to the return document from the original document
    • can rely on the program to keep track of the already returned and cost reversed quantity on the sales documents - so you don't have to worry about cost reversing return of the same sold quantity more than once.

     
     

    Olga T. Mulvad
     

  • Microsoft Dynamics NAV Team Blog

    Convergence Comes to Copenhagen!

    • 1 Comments

    After a great inaugural event last year in Munich, the EMEA flavour of Convergence comes to our backyard later this month.  Convergence Copenhagen will be held October 23-25, with a partner-only day on the 22nd.

    This is very exciting for us, as it means more of the team will get a chance to attend, and to meet and chat with our partners and customers.  There are over 25 sessions currently listed on the Dynamics NAV track, so it's a great opportunity to learn more about the product (and perhaps see a little of what's coming next).

    For more information about Convergence Copenhagen, click here.  We hope you can come - this is one of our favourite events of the year.

    Speaking of favourite events, I want to also mention Directions 2007.  This is a conference devoted entirely to Dynamics NAV, but it isn't hosted by Microsoft.  The dedication and passion of NAV partners has one of its biggest examples in the fact that some of our partners got together a few years ago and decided to create their own conference.

    Directions is in Orlando in early November, and a bunch of us are flying down to hang out and, if they let us, present some content.

    For details about Directions 2007, see here.

    Cheers,
    Ilana Smith

  • Microsoft Dynamics NAV Team Blog

    Welcome to the Dynamics NAV Team Blog

    • 18 Comments

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

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

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

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

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

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

    Dynamics NAV Leadership

     

    Dynamics NAV Architecture Leadership

     

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

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

    Darren Laybourn
    General Manager
    Dynamics NAV and Mobility

Page 1 of 1 (10 items)