Limited Users in NAV 2016

I suppose the most of you have already used Limited Users. It is pretty good possibility to save some money for users who have not a lot different processes to work in NAV. But limitation was a big; you could insert in only 3 tables by your need and in 80 additional by default. It was enough for some basics processes (creating contacts, HR, warehouse and similar).

But from NAV 2016, we have a pretty greater possibilities. That means we can use for inserting even 151 default tables; you can find completely list here. Some of the most important default tables for insert are:

  • Customers and Vendors
  • Customer and Vendor Invoice Discounts
  • Sales and Purchase Headers and Lines
  • Deferrals
  • Sales/Puchase Price and Line Discount
  • Assembly Order Headers and Lines
  • Incoming Documents
  • Workflow tables

You can see that with these tables in combination with three additional by your needs, we can use Limited Users for a lot different processes. It can decrease project cost and improve quality.

LimitedUsers.jpg

Posting Groups in Assembly Order in NAV

In my previous articles about using of posting groups in Dynamics NAV, I didn’t describe using of posting groups in Assembly Orders. Assembly Orders are here in the few last versions of NAV and I want to show them as well.

Using of Assembly Orders is not so complex and we can use only Items on header and Items and Resources in lines. Because of that, we can use only Inventory Setup and General Posting Setup. You can see the flow chart with description of usage these posting groups:

AssOrdFlCh.jpg

When we post one Assembly Order, we will get the following G/L Entries:

AssOrdEntr.jpg

Posting Groups in Service Management with Warranty

I’ve already show how looks like using of posting groups in Service Management in NAV, but when you use Service Item with currently active Warranty, there are some differences. Generally, system will use Line Discounts configured on Service Item as Warranty % for “parts” and “labor”. If you have 100% warranty, posting will be as the following:

SM-w01.jpg

System posted inventory cost for all item line based on costing type. But for each line (Item, Resource…) system posts sales line amount and the discount with the same value.

But, when you have warranty with the less percentage than 100%, it will be a bit difference. System will post item cost again, but for each line, system posts sales line amount, discount and value as difference between sales amount and discount:

SM-w02.jpg

Registration Opened for Directions EMEA 2016

Directions EMEA 2016 in Prague attendee registration has opened from today. You can make registration here. You can use the early bird in registration and save as much as 300 EUR:

Super Early Bird Feb 16 to Apr 29   745 EUR (net)
Early Bird Apr 29 to July 31   895 EUR (net)
Normal July 31 to Oct 15 1.045 EUR (net)

Directions EMEA will be probably the biggest NAV Event in 2016 and you can have a really big benefit if you will be there. You can learn a lot of different topics and meet a lot of interesting people. Directions EMEA will be held on October 12-14, 2016 in Prague, Czech Republic.

DirectionsEMEA

In the same time, registration for Directions NA 2016 in Chandler, AZ is still not opened. I hope it will be soon. In the meantime, you can find the last registration information here.

See you there.

Posting Groups in Service Management in NAV

I’ve already wrote 27 articles about using of Posting Groups in NAV. Now, I’ll continue this series with the new topic – Service. When we use Service Order, all posting will be based on the following flow-chart:

ServiceFlCh.jpg

You can notice, this is very similar with postings in Sales, but we have some specifics about using of additional fees. But if you look at the part based on Service Lines, everything is the same. I want to accent that this part is drawn for items ()because of usage Inventory Posting Group and Location); if you use G/L Account or Resource, there will not be inventory postings.

Now, let look at the posting results. First, if we decide to post “Ship and Consume” from Service Line, that means these lines have been used for servicing but cannot be included in the invoice to the customer and we will have only inventory postings if we used items (in other cases, we will not have anything for posting):

Serv1.jpg

But if we decide to post “Ship and Invoice” from Service Line, the result will be different. In this case, we have some additional entries except inventory posting:

Serv2.jpg

And on the end, we need to finish posting from Service Order. If we have not some additional fees for invoicing, it will not be anything for posting, but if we have additional fees, it looks the same (for “Ship and Consume” and “Ship and Invoice” examples):

Serv3.jpg

 

MS SQL is a Global ODBMS Leader

A few days ago, I’ve wrote about place of Power BI in Gartner survey about BI & Analytics solutions. Power BI was a global leader on Gartner Magic Quadrant. Now, we have new Gartner story about Operational Database Management Systems. For the first time, MS SQL is an absolutely leader and on better position in comparison with Oracle database.

ODBMS Gartner.jpg

The operational database management system (DBMS) market is concerned with relational and nonrelational database management products suitable for a broad range of enterprise-level transactional applications. These include purchased business applications, such as those for ERP, CRM, catalog management and security event management, and custom transactional systems built by organizations’ own development teams. Also included in Gartner’s definition of this market are DBMS products that support interactions and observations as new types of transaction. (from Gartner)

Microsoft deserves this position because they market its SQL Server DBMS for the operational DBMS market, as well as the Microsoft Azure SQL Database (a DBMS platform as a service), and the NoSQL DBMSs Microsoft Azure DocumentDB and Azure Tables.

It is very important that Microsoft continue with working on enterprise SQL Servers and on Azure SQL as well. And finally about NAV. Microsoft Dynamics NAV (from NAV 2016) works on both of these SQL versions and I think this cooperation between strong database and ERP solution will continue to deliver amazing business solutions.

Dynamics NAV Comparison Tool

If you want to upgrade your existing Dynamics NAV solution, now you can use NAV Feature Comparison Tool with added NAV 2016 features.

You just need to select you current NAV release and system will compare it with NAV 2016 and you can see key differences. All of these can help you to decide upgrade or not for sure. You can compare all version from the release 4.

You can find this new tool on the following link:

https://www.microsoft.com/dynamics/upgrade-compare/nav/default.html

CompTool.jpg