NAV Gallery Image – PS Scripts Order

This week I have training about NAV and Azure and I used some examples in NAV 2016 Gallery Image on Azure.

NAV90GalleryImage.jpg

This image is awesome, but sometime people doesn’t know what PowerShell script can be started before some others. For example, you cannot run “Use Azure SQL Database” and after that “Install Multitenancy”…

Because of that I wanted to make some small help to all people who want to use this NAV 2016 image. In the following, you can find a chart with order of using all PowerShell scripts. Now, you know how to configure all of them on the same VM.

NAV90GalleryImageOrder.jpg

How to Configure Limited Users in NAV?

A few days ago I’ve wrote about new possibilities in using of Limited Users in NAV 2016. I think this is big improvement, because we can use limited users for much more roles.

But I got a few comments about configuration limited users. OK, you can configure users as limited and this is all. Nothing more.

l-1.jpg

But people wants to configure what three additional application tables these limited users can use. Base on the standard NAV, this is not possible. These users get write access to a maximum of three application tables in the object range 0 – 99,999,999 other than the General Ledger Entry table. But system will count the first three used application tables beside the default tables. This is counted by the session. That means, users can use different three application tables in different sessions.

Some of administrators still want to limit these users on some specific tables. There is not feature for this requirement, but it can be made using User Permission Sets. We can create one permission set with all read permission on all tables (or less if you want this). Then, we can configure additional permission set with all permissions (insert, modify, delete) on our default 151 application tables. And on the end we can configure specific permission set based on our requirements for three additional tables.

Every time when we want to configure new limited user, we just need to add him these first two permission sets and one specific for him (or his role). In this case this limited user will have read permission to all tables and all other permissions to default tables and three we added to him. In this case, his three application tables will not depends of his first usage in session.

This is not some specific feature, but it is useful work around solution for configuration.

Posting Groups #25 – Job WIP Posting (3 – Cost Value)

In one of my previous posts, I have already described how you can post Job WIP entries if you use Cost Value as recognized cost in WIP posting method. But, it was only part of posting when you calculate Job WIP for the first time. But if you have already posted Job WIP entries and want to post WIP, again after new usage posting (as Contract).

In this situation, system first need to post correction of previous Job WIP entries and that post new entries. You can see how there G/L entries look like on following table:

Job WIP Posting 3a

When we speak about “Remaining Cost in Comparison with Schedule”, we already think about relation between Contract usage posting and values as Schedule.

Posting Groups #24 – Job WIP Posting (2)

If you have the same example as in previous post, but with using different methods of WIP posting (e.g. Completed Contract, Cost of Sales or Contract-Invoiced Cost), you will get the some different results. To repeat, my example was only posted usage of resources and items, without invoicing. System calculates WIP for all Resource and Item usage, based on Unit Cost and consumed Quantity. Result of this posting is following:

Job WIP Posting 2

How to Upgrade NAV

Today, Microsoft has published new article about best practices and tips and tricks in upgrading process when you want to upgrade your solution to NAV2013R2 or NAV2015. After this first part about this topic, Microsoft already publish a second part with the same topic.The main reason why to read this article is because, the Classic Client is no longer supported by Microsoft. Now, it is the right time to make upgrade of your old NAV version.

Anyway, you can find awesome articles about this upgrade process here on MSDN Blog and part 2, as well. I recommend these articles.

Posting Groups #23 – Job WIP Posting (1)

As the most of projects are jobs performing usually several months (or several years), WIP calculation is very important part of Job Management. From NAV 2013, we have new functionality for WIP calculation in Jobs – the WIP cockpit. I already described how this feature works in my older post and now, I want to show you results of WIP posting in G/L Entry.

When you want to post WIP to G/L, system will use only Jobs Posting Groups for determining what account need to use. Considering, there are not only one method of WIP posting, it means system doesn’t post results on the same way every time.

In this first example, I have used following WIP posting methods as recognized costs: Cost Value and Usage (Total Cost). Results for these two methods are the same.

System calculates WIP for all Resource and Item usage, based on Unit Cost and consumed Quantity. Result of this posting is following:

Job WIP Posting 1

Posting Groups #22 – Item Purchase for Job

If you want to purchase items directly for some Job, you can do it using e.g. Purchase Order and posting it. Flowchart of posting groups usage is the same as in post I already wrote about item purchase posting. There is only one additional step in comparison with standard item purchasing; you have to choose Job No. and Job Task No. in each line on Purchase Order.

This is not currently real example of Job Posting Groups using, but it still has some specifics when you have purchasing for Job. When you post this document, you will get both of posting documents – Purchase Receipt and Purchase Invoice, as well. But when you look in Purchase Receipt, you will see that you have two Item Ledger Entries for each line in document. One of them is Purchase, but second in Negative Adjmt. with the same quantity. It actually means that in the same posting process, system post item purchase (as usually) and item consumption for Job purpose. This posting also creates one Job Ledger Entry for each line in document with Usage Entry Type for each Negative Adjmt. line in ILE.

When you look at G/L Entries, you will see the following result of this posting:

ItemPurchJob