Overview of Microsoft Dynamics NAV W1 5.0 SP1

Overview of Microsoft Dynamics NAV W1 5.0 SP1

  • Comments 0

I have often been asked about the content of Microsoft Dynamics NAV W1 5.0 SP1.

I will here give a short overview of what we are planning to include in servicepack 1 for Microsoft Dynamics NAV 5.0, please be aware that the scope can still change:

1.       Product improvements

More than 300 product improvements based on feedback to Microsoft Support Services from customers and partners worldwide have been included in Microsoft Dynamics NAV W1 5.0 SP1. The improvements are split into the areas of the Microsoft Dynamics NAV platform and the Microsoft Dynamics NAV ERP system.

 

2.       Performance improvements

a.       SIFT including indexed views

                                                               i.      Purpose: To gain performance by using indexed views in relation to SIFT

                                                             ii.      Goal: To create one indexed view for each SIFT key that is enabled

b.      Bulk Insert

                                                               i.      Purpose: To gain performance by buffering inserts and send them in one go

                                                             ii.      Goal: To reduce the amount of roundtrips to the SQL Server

 

3.       Refactoring of the Planning Engine

a.       Address all real issues

b.      Have improved readability

c.       Clear decision principles

 

4.       New ERP Requirements based on feedback from Microsoft Dynamics NAV partners

a.       Better access to sales and purchase history 

                                                               i.      Purpose: Provide access to sales and purchase history from Customer and Vendor cards

                                                             ii.      Goal: To see open as well as posted documents based on the Pay-to/Bill-to or Bill-to/Buy-from role each vendor or customer can play

b.      Option for not auto-filling Quantity to Ship/Receive on Orders

                                                               i.      Purpose: Option to prevent auto-filling of Quantity to Ship/Receive

                                                             ii.      Goal: To be able to set up whether Quantity to Ship/Receive should be filled automatically or not

c.       PO dashboard

                                                               i.      Purpose: To align purchase documents with sales documents

                                                             ii.      Goal: Include the info pane from sales documents on purchase documents

d.       Option for not auto-filling Posting Date  on Sales and Purchase Documents

                                                               i.      Purpose: Option to prevent auto-filling of Posting Date

                                                             ii.      Goal: To be able to set up whether Posting Date should be blank or work date

e.       Automatic Archiving of Quotes and Orders

                                                               i.      Purpose: To be able to force archiving of quotes and orders

                                                             ii.      Goal: Optional to force archiving of quotes and orders before deletion

f.        Archiving of Return Orders

                                                               i.      Purpose: To align to other orders

                                                             ii.      Goal: To be able to archive Return Orders manually or automatically

g.       Print Archived Quotes and Orders

                                                               i.      Purpose: Align to other posted documents

                                                             ii.      Goal: To be able to print archived Quotes and Orders

h.      Add External Document No. and Applies-to Doc. Due Date to payment journal

                                                               i.      Purpose: Improve information about what is paid in the journal

                                                             ii.      Goal: To display the External Document No. and Applies-to Doc. Due Date columns on the Payment Journal form

i.         365 Days Depreciation for Fixed Assets

                                                               i.      Purpose: To extend the depreciation methods for fixed assets

                                                             ii.      Goal: Make it optional to use 360 or 365 days for depreciation calculation

j.        Line Comments on Documents

                                                               i.      Purpose: Extend comment to document lines.

                                                             ii.      Goal: To be able to enter comments for each line entered in sales and purchase documents and have them posted/archived as well.

k.       Posting Date on posted document lines

                                                               i.      Purpose: Better reporting on posted documents.

                                                             ii.      Goal: Add Posting Date field to posted document lines tables.

l.         Purchase Quote No. maintained in sales and purchase documents

                                                               i.      Purpose: To be able to see where the document originates from (if a quote existed).

                                                             ii.      Goal: Add quote number to not-posted Order and Invoice, and add quote number to posted Invoice and Receipt/Shipment.

m.    Add Account Description to G/L Entries Form

                                                               i.      Purpose: Better information on G/L Entries

                                                             ii.      Goal: To be able to show the G/L Account Name next to the G/L Account No. in the G/L Entries form.

n.      Filter Balance Field on Customer/Vendors to show Open Entries only

                                                               i.      Purpose: To make it easier to get an overview of content of the balance on the Customer and Vendor cards.

                                                             ii.      Goal: Show only open entries.

 

 

 

5.       Mobile integration (Ready for Mobile Integration)

a.       Purpose: To prepare Microsoft Dynamics NAV 5.0 SP1 for integration with mobile devices

b.      Goal: To be able to gather the backend information in Microsoft Dynamics NAV 5.0 SP1 to be represented on a mobile device

 

- martinni

Leave a Comment
  • Please add 2 and 4 and type the answer here:
  • Post