Microsoft Dynamics NAV 2016 - Posting Date Issue with Deferral Posting Functionality.

Hello Friends,

Today I would like to Discuss With you an Issue That I Found with a New Feature Released with Microsoft Dynamics NAV 2016.

If you remember, with Microsoft Dynamics NAV 2016 a New Feature have been Released Called as Deferral Posting.

What Does Deferral Posting Does? 

> When We post an Sales Invoice With Deferral Code The Future Entries as per Deferral Schedule will be Posted on the System.

> When we Post a Credit Memo / Return order The System Passes Adjustment To Deferral Entries in The System.

What is the Issue?

Consider an Example that Customer is Posting a Sales Invoice on 24-01-2017. With Deferral Schedule Of a Year. So My Deferral Entries will be Like as Shown Below -

As Most of Customer Uses Allowed Posting From and Allowed Posting To Either at User Level / Company Level.
Suppose Customer is having Allowed Posting Date Ranges as -  01-01-17 TO 31-01-17.

Now if Customer will try to Post Sales Invoice then he/she will end up with an error message as below

The Error is Logically Correct as During Posting of Deferral Entries System is Calling and Checking Allowed Posting Date Using Standard Function DateNotAllowed in Codeunit 11.

Pr-posed Solution - 

We can have Two More Fields in User Setup & General Ledger Setup as -
> Allow Deferral Posting From
> Allow Deferral Posting To

And A different Function to check Posting Dates Say - DeferralDateNotAllowed

We have fix this code by our-self in our client database. Hope it will help you some times.

Thank you for reading.
Keep Sharing...Keep Growing...

Dynamics NAV - Field Level Permission by new property AccessByPermission

Hello Friends,

In NAV 2016 we have new property for table’s field à AccessByPermission

Sets a value for a table field or UI element that determines the permission mask for an object that a user must have to see and access the related page fields or UI element in the client. The UI element will be removed at runtime if the user does not have permissions to a certain object as specified in the Access By Permission window

If the user doesn’t have permission for table than field will automatic hide from page

For example,

In standard NAV 2016 – “Promised Delivery Date” on sales header require permission for table “Order Promising Line”.  If the user doesn’t have permission than this fields not visible to user on sales order page.

Hint:

If you defined the property for a table field, then all instances of the field on pages are removed. To override the property on an individual page field, delete the permission value after the = sign in the Value field. Do NOT delete the whole string as that will be replicated on the property of the table field.

For more detail refer the link - https://msdn.microsoft.com/en-us/library/dn789622(v=nav.90).aspx

I hope it will be helpful to someone.

Thanks for reading.

Keep Sharing.. Keep Growing...

Know the object detail - Not in your permission range dynamics NAV

Hello Friends,

While exporting all objects from a database we sometimes get error that “You do not have permission to read the ‘XXXX' Table. Contact your system administrator to have your permissions changed.”

We cannot export those objects in Text format which are not in our license range.

So instead of identifying one by one objects that are not in license range and unmarking them, we can use below approach to export all objects that are in our license.

1 – Open Object Designer, Select all objects.

2 – Select File Menu à Lock

The column Locked will show which object(s) are locked, and the Locked By will show the user who locked the objects. You can see in the image where several objects are not locked, since these objects do not fall under the permissible range. You can now filter [Field Filter – F7] for Locked Objects and export the text file of it in one go.

Hope this help.

Keep Sharing... Keep Growing...