• Microsoft Dynamics NAV Team Blog

    Getting a warning when new demand jeopardizes projected availability?

    • 0 Comments

    How can I get a warning when entering a sales order so I am aware that this demand jeopardizes availability for other demands? That is the Avail. Check Warning functionality. Nothing new. But, I would like to bring focus to this functionality to emphasize the relevance it has.

    There are two parameters in Company Information which are relevant here:

    • "Check Avail. Period Calc.": this defines the period from demand due date where availability calculation will take place. As an example, if this is a sales order, it will check "Shipment Date" + "Check Avail. Period Calc" to determine what is the availability within that period. If availability goes negative, a warning will then arise.
    • "Check Avail. Time Bucket": this defines the bucket of this period. As an example, if we define Month, availability will be rounded to first date of next month when determining the availability period.

    Based on this two, together with the demand due date (ie. "Shipment Date" in the Sales Order), the availability calculation is executed to determine if there would be any availability issue in the future when this new demand is entered (ie. projected inventory goes negative). If so, warning arises. This is an indication to the user for action:

    • Should we go ahead and create the demand as is?
    • Should we try to promise (ATP or CTP) this or any of the other demands ahead to remove negative projected availability?
    • ...

    This warning should be considered as a tool to anticípate issues before planning is run. If we let planning to resolve this issue we might end on these undesiderable scenarios:

    • Lead time does not allow us to react and planning shows an exception (ie. we might require to consume safety stock to address this demand)
    • Demand is now on the frozen zone and this might mean negative stock in the starting date which is shown as an emergency action

    We don't want to run into exception or emergencies in our business. Of course, it might well be the case that planning is able to provide a meaningful action line for our business (ie. this availability issue is later enough that we can react within our lead times and create new replenishment). But, I would still encourage the user to be proactive and check availability when Avail. Check Warning arises.

  • Microsoft Dynamics NAV Team Blog

    Understanding Availability info in the Sales Info-Pane

    • 0 Comments

    Starting from NAV 2013 R2 CU8 or NAV 2013 CU15, we are now providing extended info in the Sales Info-Pane (Sales Order Page). This is to allow user to have clear visibility around item availability when making the right decissions to minimize inventory levels and reduce carrying costs. 

    Sales Info-Pane is now providing the following info around availability calculation:

    • Shipment date: just the shipment date from the active sales line. Nothing more than that. True. But, we need to keep in mind this is the date availability calculation is run against.
    • Item availability: this is the result from the availability calculation. It is the projected inventory on the shipment date (Inventory - Gross Requirements + Scheduled Receipts). This defines if we will have available inventory on that date for the current sales orde line.
    • Available inventory: the existing stock which is not reserved. This is the portion of the inventory we can consider as available
    • Scheduled receipt: existing replenishment (purchase order, production order, ...)
    • Reserved receipt: same as above but related only to reserved receipts
    • Gross requirements: demands (sales order, forecast, service lines, job planning lines, production order components, ...)
    • Gross reserved: same as above but related only to reserved gross requirements

    Thus, this is the info that is provided to the user there which should be used to make decissions together with the "Item Availability by ..." views. The info on this Sales Info-Pane provides insight on:

    • stock reserved/not reserved
    • availability in the shipment date
    • other existing demands up to shipment date and how many of these are already reserved
    • other existing receipts up to the shipment date and how many are reserved

    This info should tell the user how much efficient I am with my reservations. How much stock do I currently have? How much is already reserved? How much of this is being used for any existing demand which comes before or on shipment date? Is there any room for improvement on how long are we holding reserved stock to avoid waiting too much time and minimize carrying costs?

    The above together with the "Item availability by ..." views should provide tools to make decissions around this. As an example, if we have an availability issue when entering a new sales order, I would encourage user to open "Item Availability by Event" and determine what is the point in time where availability goes negative. On that date, I would check if we have any reserved stock for a demand with later shipment date. This other sales might instead be promised through CTP and existing stock used to account for negative availability.

    Lastly but not least, I would like to link this blog entry with an earlier one where I stated the fact reservations should only be done when it is strictly required. Otherwise, we might disturb planning and we might increase inventory levels if reservations are not made on a meaningful business scenario. On this assumption is where user should benefit from this Sales Info-Pane.

  • Microsoft Dynamics NAV Team Blog

    Order promising: shall we reserve available replenishment to avoid this is used when promising other demand?

    • 0 Comments

    Order promising is about using available-to-promise or capable-to-promise functionality to commit dates with customers. There is a functional difference between those two:

    • ATP is based on existing replenishment, on what is available to promise. This has nothing to do about reservations. We are just running the availability calculation.
    • CTP is based on creating new replenishment. Here, we need to create an action line in the planning (or req.) worksheet which defines the new replenishment required. This action line requires reservation to ensure that new replenishment is link to the committed demand.

    Having said this, asume we have a reservation for an existing replenishment, does it mean the above that we will just use that replenishment when running order promising for another sales? No. If that replenishment is reserved, it is not available for the order promising.

    Now, going back to the question here: assume I run ATP and promised a sales order. Should I reserve the sales order against the replenishment to ensure no other demand is using it? I would say No. Two reasons:

    • Even when there is another sales order, you might want to use this replenishment for that new demand since this might be earlier and we will reduce carrying costs. An example is when you promised a sales order for Dec 2014 based on existing stock. If another sales order comes for October 2015, why not using the stock here? We will reduce inventory costs here if we are using this for October and use CTP to create a new replenishment for the other demand.
    • If you are using reservations, you will disturb planning. Assume you have a demand/supply set reserved. This will be ignored by planning since it is considered as satisfied. Instead what we will like to do is to proceed with a planning run to ensure all demands and supplies are going through the planning parameters and an optimal plan is achieved. For instance, assume we reserve a demand to a purchase order. And, for the same date with have another demand. Here, we might run CTP since there is no availability. This will create a new replenishment for this second demand. Up to here, planning parameters from item card are not considered. However, we would like to still calculate plan to optimize this and combine both replenishment into one purchase order if this is a lot-for-lot ítem. If replenishment is reserved against the demand, it will be ignored and won't be combined into one purchase.

    But, if we are not using reservations with ATP, how will I prevent that promising a new order will not jeopardize my earlier promised demands? That is a very good question. Here, we have the Avail. Check Warning functionality. If you are entering a new sales order and this jeopardizes availability for another existing sales, it will raise a warning. User is required now to check availability here and perform actions (ie. re-promise the existing sales order and use available for new one). Avail. Check Warning is based on "Check Avail. Period Calc." and "Check Avail. Time Bucket" (Company Information) to determine the horizon from shipment date where this availability is checked. In other words, this horizon determines the demands which will be considered when checking if new sales jeopardizes availability.

     

     

  • Microsoft Dynamics NAV Team Blog

    A SCM perspective to the Intercompany functionality

    • 1 Comments

    "Intercompany resides in the Financial Management series in NAV". "IC is designed for those users who control multiple business entities to separate accounting processes". "User can enter intercompany transaction Information only once in the appropiate documents". "Users of previous versions of the product needed to re-key all Information manually for all companies and transactions".

    All the above are excerpts from IC White paper. So, this is nothing I am trying you to evangelize you about.

    And, that is what my blog is about: if you are a SCM individual, Intercompany needs to be understood as an "administrative" functionality to copy documents/transactions from one side (one IC company) to the other. This will reduce errors when manipulating orders and transactions. Good enough. But, our standard SCM processes should not change here. We still need to have those independant. Some examples:

    • Variants: One company might use variants, the other might not. Or, one IC company (the main warehouse) might have unified or agreed naming around "Item No.". But, this does not mean all other companies follow the same naming. As company B in IC, I might want to get different item codes for each íiem+variant since that is a different manufacturing process in my side.  Or, I might only have that item+variant in my other IC company and don't need to define it. Or, I might have different naming convention in this company B since it is what makes sense on my business. This is why NAV is not transferring the variants by default. However, we still have functionality to offer: cross-reference functionality. If you use this, you can define what is the Item No. that your other IC company (which is a vendor/Customer here). That will work.
    • Unit of measure: same thing applies here. We might have different UOMs on each different company. Use cross-reference.
    • Locations: sometimes we are requested to transfer locations which are set on a IC order. As an example, if I set my IC purchase order for location WHITE, it means I am expecting to receive the ítem in location WHITE. And, your vendor might send this ítem from different locations ... and this is the vendor internal processes to define what location this needs to be sent to. So, if you are just copying the location, it means that one IC company is buying an ítem expected to be receive in WHITE location and the other IC company will ship the same ítem from same WHITE location. From a standard and generic processes, this might not be valid in the majority of the scenarios. We might have a central warehouse (WHITE, IC company A) which is shipping to the subsidiaries (BLUE, IC company B). That is why SCM BUSINESS process might still be independant and not to copy the locations.
    • Planning: we cannot interfere our planning with IC. We might want to transfer data from one IC company to the other to try to commit to that. But, this is not valid for all fields. An example is "Promised Receipt Date" in Purchase Order. We cannot expect that if are filling this, that IC will transfer to the sales order as "Promised Delivery Date". Who should promise and commit this order? The vendor. And, vendor's company has a sales order to promise. We can use Order Promising functionality here and might want to copy this into the purchase order of the other IC company. But, not the other way around.

    Thus, Intercompany is about avoiding re-entering order data and transactions. But, it is not to avoid what your BUSINESS is about. If you need to promise an order or if you need to define cross-references, you still need to promise the order or still to define cross-references. IC is not to replace this. 

    This is the reason why Intercompany White paper provides the following note: "There are certain restrictions applying to the items that can occur in inter-company transactions. Not all item information can be transferred between companies. Variant codes, unit of measure, and location, for example, cannot be transferred. You need to add manually the location information to any document lines that require it ... You can use several different methods for mapping item numbers between companies: When item numbers are the same, if Common number from the e-commerce tab on the Item Card is to be used, or if the Vendor Item Catalog is to be used to map item numbers, Intercompany Postings assumes that variant codes and units of measure are the same for the item in both companies. If you need variant codes, use the Cross-Reference functionality". So, this is not to be seen as a limitation but to ensure businesses processes in IC companies are still independant.

  • Microsoft Dynamics NAV Team Blog

    Microsoft Dynamics NAV 2015

    • 8 Comments

    On September 14th, we presented Microsoft Dynamics NAV 2015 to 600 partner representatives at Directions US, and we are proud to announce that General Availability of Microsoft Dynamics NAV 2015 will be October 1st 2014. Already today partners can download Microsoft Dynamics NAV 2015 from PartnerSource and start investigating the new functionality. Visit the new readiness page to access training and resources about Microsoft Dynamics NAV 2015, and download the product here. For more information, see the Microsoft Dynamics NAV Help in the MSDN Library.

    Partners who did not attend Directions US and want to learn more about Microsoft Dynamics NAV 2015, explore business opportunities, and network with other partners should sign-up for Directions EMEA event October 8-10 in Poznan, Poland. Make sure to check back here on The NAV Team Blog for more updates in the coming weeks.

    Best regards,

    The Dynamics NAV team

  • Microsoft Dynamics NAV Team Blog

    Cumulative Update 18 for Microsoft Dynamics NAV 2013 has been released

    • 2 Comments

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

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

         *   AU - Australia

         *   AT - Austria

         *   BE - Belgium

         *   CH - Switzerland

         *   DE - Germany

         *   DK - Denmark

         *   ES - Spain

         *   FI   - Finland

         *   FR - France

         *   IS  - Iceland

         *   IT   - Italy

         *   NA - North America

         *   NL - Netherlands

         *   NO - Norway

         *   NZ - New Zealand

         *   SE - Sweden

         *   UK - United Kingdom

    Where to find cumulative update 18

    You can download cumulative update 18 from KB 2992503 - Cumulative Update 18 for Microsoft Dynamics NAV 2013 (Build 37798).

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

    CustomerSource:

         *  Overview of Released Application Hotfixes for Microsoft Dynamics NAV 2013

         *  Overview of Released Platform Hotfixes for Microsoft Dynamics NAV 2013

    PartnerSource:

         *   Overview of Released Application Hotfixes for Microsoft Dynamics NAV 2013

         *  Overview of Released Platform Hotfixes for Microsoft Dynamics NAV 2013

    More Information

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

  • Microsoft Dynamics NAV Team Blog

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

    • 3 Comments

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

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

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

    Where to find cumulative update 11

    You can download cumulative update 11 from KB 2992495  – Cumulative Update 11 for Microsoft Dynamics NAV 2013 R2 (Build 37799). 

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

    CustomerSource:

         *  Overview of Released Application Hotfixes for Microsoft Dynamics NAV 2013 R2

         *  Overview of Released Platform Hotfixes for Microsoft Dynamics NAV 2013 R2

    PartnerSource

         *   Overview of Released Application Hotfixes for Microsoft Dynamics NAV 2013 R2

         *  Overview of Released Platform Hotfixes for Microsoft Dynamics NAV 2013 R2

    More Information

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

     

  • Microsoft Dynamics NAV Team Blog

    Reservations versus Planning and Projected availability calculation

    • 0 Comments

    Nice and interesting topic when it comes to planning, existing reservations and how projected inventory work together.

    To start with, our NAV Supply Planning White Paper is clear:

    ...

    The planning system does not include any reserved quantities in the calculation. For example, if a sales order has been totally or partially reserved against the quantity in inventory, the reserved quantity in inventory cannot be used to cover other demand. The planning system does not include this demand-supply set in its calculation.

    However, the planning system will still include reserved quantities in the projected inventory profile because all quantities must be considered when determining both when the reorder point has been passed and how many to reorder to reach and not exceed the maximum inventory level. Consequently, unnecessary reservations will lead to increased risks that inventory levels run low because the planning logic does not detect reserved quantities.

    ...

    I believe the first paragaph above is reasonable. Planning assumes demand is replenished for the reserved quantity and that reserved supply cannot be used for any other demand. Clear. Based on this, planning is not including the demand/supply set which is reserved one against the other. Any other portion of the demand (unreserved portion) which requires to be replenished is included into the planning calculation since we will require planning actions here. 

    Now, the missunderstanding comes with second paragraph.The projected inventory is used by the planning system to monitor the reorder point and to determine how much to reorder quantity when using Reordering Policy="Maximum Qty.". And, as said on second paragraph above, this includes reserved quantities. This projected inventory calculation is meaningful with reorder point when stock level is evaluated to determine if new replenishment is required. To determine this stock level all projected inventory is included ... regardless if reserved or not. The stock will be there ... so it needs to be considered. An example: assume we are using Reordering Policy= "Max. Quantity". This means, most of the time, our warehouse has a maximum capacity that we cannot exceed. In other words, we cannot go above this maximum inventory level (maximum capacity) ... so we need to include reserved quantities since that is truly using our warehouse capacity. That is why reserved quantities are included. Unnecessary reservation will lead to the fact that stock is there (ie. above the certain stock level) but it is reserved to another demand.

    To summarize, if demand/supply are reserved, these will be respected in planning. And, if this is a reorder point item, reservations will be included into the projected inventory calculation which means it might disturb planning since might not be available.

  • Microsoft Dynamics NAV Team Blog

    Windows Regional Settings and Number Formatting in RDLC Reports

    • 2 Comments

    You probably know this blog post from Robert Miller: http://blogs.msdn.com/b/nav/archive/2014/03/25/formatted-decimal-values-dropping-symbols-in-rdlc.aspx. It talks about changing/forcing number formats when Windows is not able to do so. For Switzerland (de-CH), number formats in Windows are not correct regarding the thousands separator. It should be formatted “1’234,56” but is formatted like “1 234,56” (a space instead of an apostrophe). 

    Current status

    Due to the nature of RDL and the option to specify a language name for each and every single TextBox Control, Report Viewer does not pick specific user changes for decimal or date formats, even if the requested regional setting is equal to the current user's regional setting. Report Viewer retrieves the default culture settings for a language name, but does not take into account, that this setting (when selected as current/default user format) may have changed the number format.

     

     

    So ReportViewer never knows about the current regional settings and the changed symbols when looking up and using the default settings. So for our friends from Switzerland, there is currently only one known option: manually change the thousands separator and re-format the RDLC decimal values. The drawback of this is that every decimal expression has to be changed in all affected reports.

    Talking about the world and everything

    Due to a talk between buildings K and L in Munich a while ago, we came across localization topics, globalization and ways to force specific locales (and number symbols) for a Windows Forms application. Unfortunately, there is no way, because globalization changes are only supported for web.config, not app.config (see http://msdn.microsoft.com/en-us/library/vstudio/bz9tc508(v=vs.100).aspx). Not talking about different threads and (from my knowledge) no inheritance of culture information to the ReportViewer thread.

    But this discussion caused me to start searching the web and I came across custom locales (http://msdn.microsoft.com/en-us/library/windows/desktop/dd317785(v=vs.85).aspx). There is also a tool to create custom locales named Locale Builder (Download at http://www.microsoft.com/en-us/download/details.aspx?id=41158). 

    The end is near

    With the Locale Builder tool, you can create custom locales with changed number symbols, build an MSI file of it, and the *REPLACE* an existing locale in Windows by assigning the same name to the new locale:

     

    The new locale is installed using the MSI file, replaces the default locale (in this case for de-CH), and is marked with an asterisk as a custom locale: 

    Now, by default, the correct grouping symbol is used and shown when selecting de-CH, even without changing it manually: 

    With this in mind, what do you think is the result when a Report is executed on this system without any change? See fields VK-Preis (Sales Price) or Betrag (Amount). 

     

    BANG – Great!

     

    Serving some white wine with the fish

    However, when printing reports for foreign countries, it always uses the new default format now. Better than before, but not like a world champion would do…

    So, in Object Designer, open table 8 Language in design mode and add the following function: 

    GetLanguageName(LanguageCode : Code[10]) : Text[10]
    CultureInfo := CultureInfo.GetCultureInfo(GetLanguageID(LanguageCode));

    EXIT(CultureInfo.Name);

    Name         

    DataType

    Subtype

    CultureInfo

    DotNet

    System.Globalization.CultureInfo.'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'

    Save table 8.

    Open report 206 in design mode and add a new column to the DataItem Sales Invoice Header

    Language.GetLanguageName("Language Code")             Name: "LanguageName"

    Now open the report layout for report 206 and bulk-select all TextBox controls in each Tablix. When selected, change the property Language for all controls to =Fields!LanguageName.Value.

    Save everything and run report 206 for to show all posted invoices in the database. For all different languages, you should see correct decimal symbols.

    Love it? 

     

    Carsten Scholling

    Microsoft Dynamics Germany
    Microsoft Global Business Support (GBS) EMEA

    Microsoft Connect: http://connect.microsoft.com
    Online Support: http://www.microsoft.com/support

  • Microsoft Dynamics NAV Team Blog

    Select multiple filter values on a request page for an option field in Web client compared to Windows Client

    • 0 Comments

    Unfortunately, it is not possible to select multiple filter values for an option field on a request page of a report in the Web Client. This is however possible in the Windows Client. In the GUI of the Web Client it is possible to select a range as a filter though there is no underlying coding that supports this. Documentation around limitations of Web Client can be found here.

    The Web Client was originally designed for an occasional use as opposed to intensive use for which we have the Windows Client. Partner and Customer feedback has clearly indicated that the strengths of the Web Client (e.g., easy to deploy, runs in major browsers) have pushed adoption well beyond its’ intended use. In feature releases we will therefore address the functionality of the Web Client further.

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

    Marco Mels
    Microsoft Dynamics NAV

  • Microsoft Dynamics NAV Team Blog

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

    • 9 Comments

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

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

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

    License Versioning

    Microsoft Dynamics NAV 2013 R2 Cumulative Update 10 introduces license key versioning to Microsoft Dynamics NAV. Observe the following specifications:

    • Microsoft Dynamics NAV 2013 R2 license keys will continue to be backward compatible with Microsoft Dynamics NAV 2013 instances.
    • Microsoft Dynamics NAV 2013 license keys cannot not be used with Microsoft Dynamics NAV 2013 R2 instances. Accordingly, newly issued Microsoft Dynamics NAV 2013 license keys will not work with Microsoft Dynamics NAV 2013 R2 CU10 (or later) instances.
    • Microsoft Dynamics NAV 2013 and Microsoft Dynamics NAV 2013 R2 license keys are not forward compatible with Microsoft Dynamics NAV 2015 instances.

     More details about license versioning will be made available in the October 2014 release of the Microsoft Dynamics Perpetual Licensing Guide.

    Where to find cumulative update 10

    You can download cumulative update 10 from KB 2984452 – Cumulative Update 10 for Microsoft Dynamics NAV 2013 R2 (Build 37563). We listed a different build number when this blog post published the first time, and we apologize for the resulting confusion. the correct build number is 37563.

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

    CustomerSource:

         *  Overview of Released Application Hotfixes for Microsoft Dynamics NAV 2013 R2

         *  Overview of Released Platform Hotfixes for Microsoft Dynamics NAV 2013 R2

    PartnerSource

         *   Overview of Released Application Hotfixes for Microsoft Dynamics NAV 2013 R2

         *  Overview of Released Platform Hotfixes for Microsoft Dynamics NAV 2013 R2

    More Information

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

     

  • Microsoft Dynamics NAV Team Blog

    Cumulative Update 17 for Microsoft Dynamics NAV 2013 has been released

    • 0 Comments

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

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

         *   AU - Australia

         *   AT - Austria

         *   BE - Belgium

         *   CH - Switzerland

         *   DE - Germany

         *   DK - Denmark

         *   ES - Spain

         *   FI   - Finland

         *   FR - France

         *   IS  - Iceland

         *   IT   - Italy

         *   NA - North America

         *   NL - Netherlands

         *   NO - Norway

         *   NZ - New Zealand

         *   SE - Sweden

         *   UK - United Kingdom

    Where to find cumulative update 17

    You can download cumulative update 17 from KB 2984829 - Cumulative Update 17 for Microsoft Dynamics NAV 2013 (Build 37532).

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

    CustomerSource:

         *  Overview of Released Application Hotfixes for Microsoft Dynamics NAV 2013

         *  Overview of Released Platform Hotfixes for Microsoft Dynamics NAV 2013

    PartnerSource:

         *   Overview of Released Application Hotfixes for Microsoft Dynamics NAV 2013

         *  Overview of Released Platform Hotfixes for Microsoft Dynamics NAV 2013

    More Information

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

  • Microsoft Dynamics NAV Team Blog

    Filter values specified on a request page for a report are not saved by the Web Client

    • 1 Comments

    When running a report from the Windows Client with Microsoft Dynamics NAV 2013 R2, filter values specified on the request page are saved along with the relevant user’s personalization information. These filter values are conveniently restored to the request page the next time the user runs the same report.

    The Web Client does not save such personalization information so the filter values cannot be restored to the request page when the user runs the same report subsequently if they are using the Web Client. This is one of the known feature limitations of the Microsoft Dynamics NAV Web Client.

    For more information about feature limitations of the Microsoft Dynamics NAV Web Client click here.

  • Microsoft Dynamics NAV Team Blog

    Temporary Issue with Single Sign-On for Office 365

    • 0 Comments

    On August 13, the Single Sign-On (SSO) protocol that is used in Microsoft Azure Active Directory (Azure AD) was updated, which unfortunately caused the SSO implementation in Microsoft Dynamics NAV 2013 R2 to fail temporarily. As a result, users could not log into Microsoft Dynamics NAV using their Office 365 credentials.

    The problem was resolved later in the day so that single sign-on was again working for Microsoft Dynamics NAV users using Office 365 credentials. However, we have decided to change the way we handle authentication against Microsoft Azure AD so that we are less sensitive to this type of update to the SSO protocol. The new design will be part of the Cumulative Update 11 for Microsoft Dynamics NAV 2013 R2. 

     

     

    ----- This blog post was updated on August 14 -------

  • Microsoft Dynamics NAV Team Blog

    Compatibility with SQL Server 2014

    • 8 Comments

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

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

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

    • Standard Edition
    • Enterprise Edition

    Best regards,

    The Dynamics NAV team

     

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

Page 1 of 44 (655 items) 12345»