Skip to content

ArcherPoint Dynamics NAV Developer Digest - vol 174ArcherPoint's Developer Digest Weekly Blog

The NAV community, including the ArcherPoint technical staff, is made up of developers, project managers, and consultants who are constantly communicating, with the common goal of 

sharing helpful information with one another to help customers be more successful.

As they run into issues and questions, find the answers, and make new discoveries, they post them on blogs, forums, social media...so everyone can benefit. We in Marketing watch these interactions and never cease to be amazed by the creativity, dedication, and brainpower we’re so fortunate to have in this community—so we thought, wouldn’t it be great to share this great information with everyone who might not have the time to check out the multitude of resources out there? So, the ArcherPoint Microsoft Dynamics NAV Developer Digest was born. Each week, we present a collection of thoughts and findings from NAV experts and devotees around the world. We hope these insights will benefit you, too.

Multiple Discounts in Dynamics NAV

Adrian asks, “NAV selects the highest sales line discount among the multiple effective sales line discounts covering a sales line. Is there a way to add sales line discount on the top of another on the same line? Thanks for your ideas in advance!”

Todd replies, “…one of our clients has something like this but you have to add a new table to hold the multiple discounts for each line. You then sum up the discounts in this new table to arrive at "Line Discount %". We can review if you want. It's a little involved. Maybe others have done something easier.”

Michael adds that another client has customizations for an interface with a 3rd party discount application. He explains, “Records are pushed into a custom table in NAV. The Job Queue runs a codeunit that "sums" the multiple, active discount records into the Sales Line Discount table.”

How to Print Dynamics NAV Code

Bill shares How to print (like on real paper) from Visual Studio Code and from Dynamics NAV C/AL.

Dynamics NAV Table Relationship Diagrams: Two Sources

Adrian shares that he found a website for a free NAV 2016 table relationship diagrams

Bill adds that by right clicking on a table in Prism and picking "Explore Table Relations" gets you something similar. He elaborates, “If our customer's Master branches are up to date in source, you'll have what this offers plus all of the customization.”

Packt Books and Videos Now on Sale

Suresh found on Twitter that every Packt eBook and video are only $5. Time to grab a book and do some learning! 

KC notes that they provide a free daily book from PacktPub, but it is temporarily unavailable while the $5 sales is going on. Make a bookmark for future reference. 

Standard Cost by SKU in Dynamics NAV

Sherry has a client looking to implement standard costs by SKU and asks if we ever done this customization for another client.

Rick Dill states that he does not recommend it. “Standard Cost by SKU is a huge modification, and to be honest should be avoided. Let me make a partial list of the things that would be involved:

  1. NAV does not let you store BOM and routing by SKU so you cannot have different bills or routing by SKU/location.
  2. NAV does not store the "single level and rolled up" cost fields by SKU, these fields are important, as they are used to calculate variances. (Note there is a roll process on the Item card that would need to be changed as well to make sure it updated the SKU card.)
  3. The standard cost roll from the standard cost worksheet is the only way that costs should be rolled and implemented (to make sure inventory is revalued correctly). The standard cost worksheet is not designed to accommodate location/variant differences in cost (in part because of points 1 and 2), so the cost worksheet would need to be modified to accommodate cost by variant.
  4. Maybe the most significant reason of all is that the transfer process/logic is not designed to handle different costs per SKU. NAV would not know how to handle the cost change between location/variant when it is transferred, Keep in mind that the transfer process must move from one location to another, and the costs must remain the same. Therefore, a modification would need to be made to know what cost element had changed, (material/labor/overhead/subcontracted/MFG Overhead), and then logic would need to be added somewhere that would generate G/L entries to account for the cost difference, and where the difference should post.
  5. Production Order variances are calculated during the "Change Status" to finish, and adjust cost entries would need to be changed to know how to calculate the variances and post the variances based on the fact that the Cost elements are stored on the Item card, not the SKU card (which would have to be changed if there are different costs).

This is such a huge change, and really changes the core of the financial logic of NAV, that I have never suggested to a customer that they go this route. The integrity of the costing logic is so interweaved, that it is almost impossible to find every place that the code would need to be changed.”

Do any of our readers know of an ISV solution for this request? If so, please comment below.

Stay abreast of what is new in the Microsoft Dynamics NAV community and at ArcherPoint by subscribing to our monthly newsletter, Better Business, by completing the form in our Resource Center.

If you are interested in NAV development, be sure to see our collection of NAV Development Blogs.

Read the "How To" blogs from ArcherPoint for practical advice on using Microsoft Dynamics NAV.

Blog Tags: 
Read ArcherPoint's Blog Follow us on Twitter Follow us on Facebook Follow us on LinkedIn Link to our RSS feed Join us on Google+ Watch us on YouTube
Get Help Now