Straight Line Depreciation Formula

Different depreciation methods are being calculated based on different algorithms. 

Examples - Straight line depreciation: 

a) based on depreciation period 

Depreciation Amount = ((Book value - Salvage Value) * Number of Depreciation Days) / Remaining Depreciation Days

b) based on fixed yearly percentage 

Depreciation Amount = (Straight-Line % * Depreciable Basis * Number of Depr. Days) / (100 * 360)

c) based on fixed yearly amount

Depreciation Amount =(Fixed Depreciation Amount * Number of Depreciation Days) / 360

Approval Management NewNAV2016

Microsoft Dynamics NAV 2016 introduces new approval types. These approval types provide flexibility for different scenarios and enable you to choose different types of approvals for different workflows.

Out of the box, the following approval types are supported:

Type	Description
Approver Chain	Specifies that approval request entries are created for all the requester’s approvers, up to and including the first qualified approver. This is typically used to support a scenario where the approval must go up the hierarchy to find someone with sufficient spending limit to sign off.
Direct Approver	Specifies that an approval request entry is only created for the requester’s immediate approver, regardless of the approver’s approval limit. This is typically used in employee/manager sign-off approvals.
First Qualified Approver	Specifies that an approval request entry is only created for the requester’s first qualified approver. This approval type is similar to the Approval Chain type but instead of informing each approver in the chain, it jumps directly to the approver who has sufficient limit to approve.

The Approval User Setup window helps you define how approvals users interact according to a hierarchy.

The following example shows how the Approval Type and Approver Limit Type settings control the navigation through the user hierarchy.

Assume the following user hierarchy:

User ID	Approver	Salesperson/Purchaser Code	Sales Limit	Purchase Limit
USER 1	USER 2		100 Rupees	100 Rupees
USER 2	USER 3	A	500 Rupees	500 Rupees
USER 3		B	Unlimited	Unlimited

As USER 1, you create a purchase document and send it for approval. What happens?

1. Approver Type = Approver
   • Approver Limit Type = Direct Approver: A request is sent to USER 2, regardless of the amount on your document, because USER 2 is your direct approver.
   • Approver Limit Type = Approver Chain:
     • Document amount < 100 EUR: The request is automatically approved.
     • Document amount between 100 and 500 EUR: A request is sent to USER 2.
     • Document amount over 500 EUR: A request is sent to both USER 2 and USER 3.
   • Approver Limit Type = First Qualified Approver: Same behavior as for Approver Chain, with the difference that the request is sent directly and only to the relevant user. For example, when the document is over 500 EUR, a request is only sent to USER 3.

2. Approver Type = Salesperson/Purchaser
   • Same behavior as for Approver Type = Approver, with the difference that the first approver for the document is identified by the salesperson/purchaser code. For example, given B as the sales document approver, then the algorithm starts with USER 3 rather than USER 2 (which is the approver for the user who sends for approval).

3. Approver Type = Workflow User Group
   • A workflow group consists of a number of users who are not structured in a hierarchy. Instead, they are ordered by a sequence number that controls the order in which they receive the approval requests.

For more information, see Workflows.

NAV Blogs

 Waldo's Blog          Vjeko Blog                  Totovic BlogMagno's Blog         ArcherPoint Blog           Kauffmann Blog           Hougaard Blog       Kulla's NAV Blog          Mohana's Blog Ashwini Tripathi Blog      Tharanga N. Chan.

Automatic Recording Permissions in NAV 2016

In older NAV versions, every time we needed more permissions sets then we already have in NAV, we have had a problem. It was not so easy and we had to be careful with this process. There was no some automatic tool for permissions recording. Now, we got it.

If we need more permissions sets, we can make them manually as earlier. But now we can use new automatic tool as well. This tool for recording permissions is based on the code coverage functionality. We can do more different activities on NAV and it will be recorded.

We just need to create a new Permission Set and choose Permissions. We need to click Start button and then we have to work all activities this role need to do. For example, open Sales Orders, create new, and create new Customer and new Item. When you finish with activities, click Stop button on Permissions and system will fill your page with all user rights. System will add only tables you used with Readpermission; you have to add other permissions you need (Insert, Modify, Delete).

If you have forget some activities, you can do it again and after you click Yes on question “Do you want to add the recorded permissions?”, you will get add new rights.

This is really useful feature. Maybe we could use some of similar solutions, but now we have it in standard NAV.

NAV 2016 installation overwrites NAV 2015 Administration Tool

October 7, 2015 by ajk | 15 Comments

If you are like me, than you might have installed NAV 2016 right away after it was released during Directions EMEA in Mannheim this week.

Dynamics NAV 2016 installs nicely side-by-side with Dynamics NAV 2015. (By the way, the items in the menu are now called ‘Dynamics NAV 2016’ instead of ‘Microsoft Dynamics NAV 2016’. So look at the ‘D’ in your menu and not at the ‘M’).

There is one small issue with installing NAV 2016 along NAV 2015: the NAV Administration Tool of NAV 2015 doesn’t work anymore. If you start it, you will notice that the NAV 2015 Administration Tool is actually the NAV 2016 version. And you can’t administer the NAV 2015 servers using the NAV 2016 Administration Tool. You will see this kind of error:

The real and rock solid solution to manage your existing NAV 2015 services is simple: go use PowerShell. 

If you are not a PowerShell hero right now, and don’t want to take this opportunity to become one, then read on for a solution to repair the NAV 2015 Administration Tool.

[UPDATE 14-10-2015] Waldo doesn’t want to call himself a PowerShel guru, but if he is not, who else is? He couldn’t resist and wrote a PowerShell script to fix the NAV 2015 Administration tool. I was only thinking about using PowerShell to administer NAV servers. However, look at the script Waldo wrote, and see that PowerShell can do a lot more!

Reason

The reason that NAV 2015 Administration Tool is actually starting NAV 2016 is because of a registry entry. There is just one registry entry that is used for both versions which points to the assemblies that must be loaded.

The NAV Administration Tool is a Microsoft Management Console snap-in. This snap-in is started by the file “Microsoft Dynamics NAV Server.msc” which is in your RoleTailored Client folder.

The “Microsoft Dynamics NAV Server.msc” file is basically an XML file with an entry that points to and registry key.

The NAV 2015 and NAV 2016 Administration Tool both point to this registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\FX:{BA484C42-ED9A-4bc1-925F-23E64E686FCE}

Manual steps to fix

The solution to fix the NAV 2015 Administration Tool is as follows.

You can also download the registry file here and skip to step 3.

Step 1

Open the registry editor, find the key and export it to a file.

Step 2

Edit the exported file:

Search for all occurences of  C:\\Program Files (x86)\\Microsoft Dynamics NAV\\90 and change it to C:\\Program Files (x86)\\Microsoft Dynamics NAV\\80

Search for Microsoft.Dynamics.Nav.ManagementUI, Version=9.0.0.0 and change it toMicrosoft.Dynamics.Nav.ManagementUI, Version=8.0.0.0

Change all occurences of BA484C42-ED9A-4bc1-925F-23E64E686FCE to BA484C41-ED9A-4bc1-925F-23E64E686FCE. (Only changed 8th character here, you can even choose to replace the complete GUID).

Step 3

Import the file into the registry by double clicking on it. Answer yes to the security warning (only if you are sure you can trust me, otherwise let it go…).

Step 4

Open your favorite text editor (run as Administrator) and open C:\Program Files (x86)\Microsoft Dynamics NAV\80\RoleTailored Client\Microsoft Dynamics NAV Server.msc

Step 5

Change all occurences of BA484C42-ED9A-4bc1-925F-23E64E686FCE to BA484C41-ED9A-4bc1-925F-23E64E686FCE
Notice this is the same GUID as changed in step 2. There are 4 occurences.

Save the file and close it.

Now both NAV 2015 and NAV 2016 Administration Tool run nicely side-by-side!

Word Forms and Emailing