In January 2013 we released Microsoft Dynamics NAV 2013 Management Pack for System Center which we announced in this blog post.
This extension package is helping Microsoft System Center Operations Manager users monitor computer systems running Microsoft Dynamics NAV 2013.
Microsoft Dynamics NAV 2013 Feature Pack 1 released in June along with the great management and Windows Azure provisioning features included in it, introduces a new way of deploying Microsoft Dynamics NAV Web server components.
In Microsoft Dynamics NAV 2013, the administrators could deploy these components using the following hierarchy:
In Microsoft Dynamics NAV 2013 Feature Pack 1, we introduced a different and more flexible approach for installing the Web components, allowing the user to install and configure multiple Web applications for a Microsoft Dynamics NAV Web site:
The following screenshot illustrates this setup.
If you use Microsoft System Center Operations Manager, install the new version of Microsoft Dynamics NAV 2013 FP1 Management Pack for System Center in order to discover and monitor multiple Microsoft Dynamics NAV Web Server instances (applications) that are running in your environment.
Microsoft Dynamics NAV 2013 FP1 Management Pack for System Center can be downloaded from this location on the Microsoft Download Center.
The Microsoft Dynamics NAV Service Experience team
The Reusable Dynamics NAV Patterns is a joint initiative between the NAV team and NAV partners. This is an open initiative to anyone who has documented design patterns which are specific to NAV, please reach back to us either by leaving a comment here, or by writing to us. This week, we introduce the pattern well before the weekend, just to break our own pattern again.
Meet the Standard Journal pattern, which gives the NAV user the advantage of storing transaction details and reusing them multiple times at later dates. For example, this is how to pay a monthly bill.
If the journal data can be reused later, the user has the possibility to save the current temporary transaction details. One example can be the case of monthly electricity payments. The user will manually enter the details for the first payment, of the current month. Next month, a part of the data will be the same, such as the vendor and transaction details. If the user has saved the initial monthly payment as a standard journal, then they can now reuse it to create the draft of the next monthly payment. Once the draft journal lines are created, they can be updated with the current month information.
When a journal is created, the user can invoke the Save as Standard Journal action to save the current journal for later use. When saving the journal as a standard journal, the user is required to choose a code, which is later used to identify the saved journal. The journal lines are stored in a separate table. There can be one standard journal saved per journal type and code.
Later, the user can create new journal lines by using the Get Standard Journals action. This action restores the saved journal into the new journal lines.
Step 1: The data entered by the user through the Journal page is stored temporarily in the Journal Line table. The data is available for editing or deleting. The journal line data will be stored in this table until it is either deleted or posted.
Step 2: The user decides to save the current journal line entries for later use. If this is the monthly rent, the user may want to use similar entries next month when a new payment is due. On the Journal page, the user invokes the Save as Standard Journal action. This triggers the Save as Standard Journal report, which copies the entries from the Journal Line table to the Standard Journal Line table. When saving, the user will be asked for an identifier, a code, which will be used to later uniquely identify the saved entries.
Step 3: When the user invokes the Get Standard Journal action, a list of codes are presented to the user so that they can decide which standard journal to restore and copy in the Journal Line table.
The sequence flow of the three steps is described in the following diagram.
In the standard version of NAV, the Standard Journal functionality is implemented in the following journals:
The user enters data in the General Journal page (39) and invokes the Save/Get actions as illustrated in the following screenshot:
When saving the journal lines, the Save as Standard Gen. Journal report (750) is invoked. The report saves the entries in the Standard General Journal Line table (751).
The Reusable Dynamics NAV Patterns team
Today we have released update rollup 4 for Microsoft Dynamics NAV 2013 (Build 35026).
Update rollup 4 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2013 and includes hotfixes that apply to all countries and hotfixes specific to the following local versions:
Where to find update rollup 4
You can download update rollup 4 from KB 2860301 - Update Rollup 4 for Microsoft Dynamics NAV 2013 (Build 35026).
The hotfixes that have been released since update rollup 3 are listed in KB 2860301. For a full list of all hotfixes included in the update rollup, see the following CustomerSource and PartnerSource pages:
For more information about update rollups for Microsoft Dynamics NAV 2013, see Announcement of new hotfix process for Microsoft Dynamics NAV 2013.
The Reusable Dynamics NAV Patterns is a joint initiative between the NAV team NAV partners. This is an open initiative to anyone who has documented design patterns which are specific to NAV, please reach back to us either by leaving a comment here, or by writing to us. This said, it's almost weekend, so here you have the NAV design pattern of the week.
This pattern is intended for storing information about the operating setup or environment in the database, in a way that can be persisted across sessions. To facilitate this, this information is stored in a table with one record only. The user is subsequently able to modify, but not add or delete records in the table.
The most common implementation of this is in the NAV Setup tables.
Implementation of the pattern involves 3 considerations:
Since this kind of tables is a collection of several environment or setup parameters, the primary key does not refer to any business attributes for this kind of tables. However, for maintaining the integrity of the database, it is necessary to define a primary key.
So, the most common implementation is to have a field "Primary Key" of Code. This is populated with a blank value when the record is inserted. This field is not added to the page, so that the user cannot be modify it later.
The CardPage type is most suitable for representing this kind of tables. In addition, the InsertAllowed and DeleteAllowed properties in the page should be set to false to prevent the user from adding or deleting records in the table.
In the OnOpenPage trigger, the following code should be added to insert a record when the user opens the page for the first time, if a record does not exist already.
The Company-Initialize codeunit (codeunit 2) is executed when a new company is created. We recommended that you add records to the single-record tables in this codeunit. If some of the fields are expected to have default values, they can also be populated here.
Several Setup tables in NAV implement this pattern. Some of those are:
Note: While most tables just insert a record with empty primary key in codeunit 2, table 242 ("Source Code Setup") offers an example of inserting default values into all fields of the table (method "InitSourceCodeSetup"). This practice, wherever feasible, is likely to reduce the effort during implementation.
The Reusable Dynamics NAV Patterns is a joint initiative between the NAV team NAV partners. This is an open initiative to anyone who has documented design patterns which are specific to NAV, please reach back to us either by leaving a comment here, or by writing to us. This being said, find below the NAV design pattern of the week. (Yes, it's late in the week, but still!)
Generally, NAV translation refers to the translation of UI elements like captions and user texts (messages on dialogs, warnings, error messages). This translation is done by the Microsoft Dynamics NAV team before releasing the localized version of the product.
But there is one more scenario. In this scenario, Cronus International Ltd., wants to sell a "Fiets" to a Dutch customer, a"Cykel" to a Danish one, and a "Bicicletta" to an Italian customer. All 3 are the same inventory item - and its default name is "Bicycle". But for reporting, Cronus International Ltd. wants to use the customer language preferences for translating the bicycle's name.
Sometimes there's a need to support multiple languages for domestic transactions, too. For example, Switzerland has 4 official languages: German, French, Italian and Romansh, the first 3 of them being supported by NAV.
The example below uses the Item Translation feature of NAV, however, implementations of the same pattern exist for other application areas.
Enter translations for "Bicycle"
In the Windows client, on the bicycle Item card, on the Home ribbon tab, choose Translations.
On the opened page, enter the Danish (language code DAN), the Italian (ITA), and the Dutch (NLD) translations for "Bicycle".
Set the desired language for the Dutch, Danish, and Italian customers
On the customer card for your 3 customers, in the Foreign Trade FastTab, choose the preferred language for each customer. If no language is specified, then the default item description will be used for items sold or anyhow associated to that customer. If for example, the DAN (Danish) language is specified for the customer, and the "Bicycle" has a translation in Danish, then this translation "Cykel" will be used instead of the default name "Bicycle".
See the result
After those changes, when the customer (in this case the Danish "Lauritzen Kontormøbler A/S") transactions a bicycle, the translated description "Cykel" will be displayed on the documents and reports. For example, creating a sales order for this customer with 1 item No. 1000, shows:
Create the translation table
Named "<Entity> Translation" table, where <Entity> is replaced with the name of the actual object being translated. For the Item example above, this table will be named "Item Translation".
The table definition contains at a minimum:
The table above has a key composed of the first two fields.
Create the user interface for entering new translations of <Entity>
Some of the NAV implementations of this pattern are:
The Extended Text pattern is a more powerful version of the Multilanguage application data pattern presented in this section. The main differences are:
Welcome to day 3 of Microsoft's Worldwide Partner Conference 2013. And what a busy day we have lined up for you!
Building on yesterday's end-to-end product session, today's focus is on how you can plan and build your business. Firstly, at 1:30 p.m., prepare to be inspired in the Microsoft Dynamics NAV: New opportunities to build your business session, where you can learn about the new opportunities you should consider as you look at your business planning for the next 12-24 months - including key topics such as RapidStart Services for Microsoft Dynamics NAV, Windows Azure and Office 365.
Then go deep in two of these strategic business areas that could help propel your business forward and sharpen your competitive edge. First up, at 3 pm, is Heading into the Future with the Windows Azure Cloud for insight and information on opportunities to offer Microsoft Dynamics NAV and Microsoft Dynamics GP, hosted in the cloud on Windows Azure infrastructure services. Learn about the model, business best practices, pricing and licensing approaches, technical resources, top lessons learned, and more.
Then at 4:30 p.m. don't miss How to sell Office 365 together with Microsoft Dynamics GP, NAV and SL. This session will provide detailed guidance on how the increasing level of integration with Microsoft Office 365 has created a new opportunity for you to boost your bottom line by offering Office 365 to your customers. Hear about the combined sales motion, Office 365 pricing and licensing, available resources, and best practices from other Microsoft Dynamics partners.
As well as being packed with valuable information, all three sessions offer the chance to win fantastic prizes, so come along, and be sure to stay until the end!
Still hungry for more? With over 450 sessions, there is something for every taste. You could brush up on your business leadership skills in the Business Leadership track and the Emerging Leaders track. Hear more about the Microsoft cloud strategy, offerings, and programs for hosting and cloud service providers in the Hosting and Cloud Service Providers track. Or get together with other partners like you in other areas of the Microsoft business ecosystem in the Small and Medium Business Reseller track.
You can get all the session details, times and locations here, and read about all the other valuable and inspirational tracks here.
So much to do, so little time...
The Dynamics NAV ERP SMB Team
If you are among the lucky few - well, 16,000 actually - who were able to join us here in "Space City", then welcome to Houston, and to Microsoft's Worldwide Partner Conference 2013!We have five fantastic days of valuable strategy, business, and product content lined up for you, as well as an unparalleled opportunity to interact and network with your peers and Microsoft employees.
If you arrived yesterday, hope you enjoyed the welcome reception, and your first chance to join us in the citadel that is the Commons - the beating heart of the whole conference experience.
Today the fun starts in earnest with our first vision keynote, already at 8:30 a.m. in the Houston Toyota Center, close to the conference center itself. This is an unmissable chance to see Microsoft top leadership - including Steve Ballmer, Kevin Turner, and Jon Roskill - set the scene by presenting the current state of key market areas, such as Cloud, Big Data, Devices and Mobility, and Enterprise Social, and outline the huge partner opportunity that lies ahead.
Then it's back to the convention center in good time to get a front row seat for the Microsoft Dynamics Value Keynote, Seeing the future: a dynamic vision for business solutions at 1:30 p.m. Hear Kirill Tatarinov, Neil Holloway, and others as they share the Microsoft vision for the future of business solutions, highlight first-hand stories of partner business success, and chart the path toward the business opportunities of tomorrow. Also in this session – our Microsoft Dynamics NAV partners Cooper Parry will join Neil Holloway on stage.
Next stop is the Microsoft Dynamics NAV: End-to-End Update session, where you can get fully up-to-speed on all things NAV with a comprehensive strategy, business and product update, and information on how the upcoming “Sicily” release will help you operate a true volume business in the SMB space by offering the power of a comprehensive business solution from Microsoft
And if the program so far has not slaked your thirst for info, the EXPO is open from 12 p.m., with a Happy Hour from 4 p.m.to 5:30 p.m. - which I make an hour and a half :-) . But hey, who can say no to a little extra happiness?
But save a little energy for tomorrow, when we will focus on how Microsoft Dynamics NAV offers new opportunities to build your business - including how to sell Office 365, and leveraging the Windows Azure Cloud. Plan your day now on the WPC Connect Session & Meeting Scheduler, and remember that every time you attend one of our sessions, you have the chance to win great prizes!
And for those Microsoft Dynamics partners who are not among the lucky 16,000 here in sunny Houston, we will be sure to make recordings of all our sessions available to you after the event, so you can see what you missed, and start pre-warning your boss that you intend to come and join the party next year....
OK - off to the vision keynote. See you there!
The Reusable Dynamics NAV Patterns is a joint initiative between the NAV team NAV partners. This is an open initiative to anyone who has documented design patterns which are specific to NAV, please reach back to us either by leaving a comment here, or by writing to us. This being said, find below the NAV design pattern of the week.
The goal of the Copy Document pattern is to create a replica of an existing open or closed document (posted or not posted), by moving the lines and, optionally, the header information from the source document to a destination document.
Documents are widely used by most of our customers. Many times, a significant portion of these documents are similar to each other, either by sharing the same customer, vendor, type, or line structure. Being able to re-use a document as a base for creating a new one is therefore an important means of saving time.
Other business scenarios require that a newly created document is applied to an existing document. For example, in returns management, a return order can be the reversal of an existing order and can therefore be copied from the original order. Other times, there is even a legal requirement to match the document to its source. For example, credit memos need to be applied to the originating Invoice.
For these reasons, NAV supports the copying of documents as a method to re-use or link documents.
The Copy Document functionality is used in the following situations:
The Dynamics NAV application developer can take into account using the Copy Document design pattern when they have requirements such as:
The Copy Document pattern involves the following entities:
Note:The source document header/line and destination document header/line tables do not need to be the same. For example, you can copy a Sales Shipment Header/Lines into a Sales Header/Lines.
Precondition: The user creates a new destination document Header, filling up the required information.
Step 1: The user runs the Copy Document report (element no. 4), filling up the parameters:
Step 2: The report copies the information in the source tables (Header and Line) into the destination tables (Header and Line).
Post processing: The user performs additional editing of the destination document.
The sequence flow of the pattern is described in the following diagram.
Example: Copy Sales Document for Credit Memos.
In the standard version of Microsoft Dynamics NAV, the Copy Document functionality is implemented in the Sales Credit Memo window as shown in the following section.
Precondition: The user enters data in PAGE44, Sales Credit Memo.
Step 1: The user runs REP292, Copy Sales Document from the Sales Credit Memo window, populating the required parameters. The Include Header and Recalculate Lines fields are selected.
Step 2: The Sales Credit Memo window is populated with information from the source sales document.
Post processing: The user can now do additional editing of the sales credit memo.
The Reusable Dynamics NAV Patterns team with special thanks to Bogdan Sturzoiu
I'm sat in a room with Erik Tiden. We've just been shown NAV 2013 "Sicily" running on Windows Azure and running inside SharePoint 2013. You have to come and see this.!
Registrations are open – we look forward to seeing you at one of the Directions events: September 2-4 in Vienna or October 6-9 in Nashville, TE.