NAV Development Tools Preview – March Update


Best News on March Update

About In-Client Designer

You can now reorder columns with a simple drag and drop, and you can hide or show columns. Try it out on any page with columns, such as worksheets, sales documents, or lists.

About Reports

Report application objects join the list of supported objects! Create reports using new syntax and include them in your extensions.

  • Reports do support both Word and RDLC layout.
  • Layouts are now saved as external files.

About Dependency

You may define a dependency on another extension by listing it in the app.json configuration file.

About Bub Fixing

https://github.com/Microsoft/AL/issues

 

New Azure Image

You can find updated Image here:  http://aka.ms/navdeveloperpreview

ten1

Source: NAV Development Tools Preview – March Update – Dynamics NAV Team Blog

Old Source: https://blogs.msdn.microsoft.com/nav/2016/12/20/announcing-the-preview-of-development-tools-for-dynamics-nav/

Advertisements

New Book availabe: “Building ERP Solutions with Microsoft Dynamics NAV”


Hi Guys, a new book is available: “Building ERP Solutions with Microsoft Dynamics NAV”, by Stefano Demiliani (Author) and Duilio Tacconi (Reviewer).

demiliani

… I spoke yesterday with these 2 guys (my colleagues and friends) during a workshop about “New Modern Development Experience“, i didn’t know that today would be released the book .. i thought later…  but today Amazon quickly provided me a copy (ebook) for review, i will read in next days….

About This Book

  • Integrate NAV with various offerings of the Microsoft stack to create enterprise-ready and service-oriented solutions
  • Use Power BI and Universal Windows Platform for effective data analysis and real-time tracking with NAV
  • Discover the services offered by Microsoft Azure and implement them in different industries using real-world case scenarios

This Book is for

“This book is for NAV developers and solution architects who need to implement real-world enterprise solutions based on Microsoft Dynamics NAV. Knowledge of the NAV programming language (C/AL) and C# language is recommended. Knowledge of ASP.NET and Visual Studio development would help, but is not necessary.”.

You can find this book on:

Amazon
http://amzn.to/2kANTZU

PacktPub
https://www.packtpub.com/application-development/building-erp-solutions-microsoft-dynamics-nav

Fast first look: for now it seems very interesting, some nice topics (that were not included before in other books) are exposed, i recommend it.

Have a nice reading !

Dynamics NAV with Power BI


Dynamics NAV with Power BI

I spoke recently of using NAV with Power BI, currently this topic (NAV integration with Power BI) is current and widely discussed, many questions about “How-to” integrate new and old releases on NAV with Power BI. I have collected a series of posts videos on Power BI and about integration with NAV (the most interesting that I fond).

MICROSOFT POWER BI

Best Definition by Microsoft: “Microsoft Power BI is a Microsoft’s Business Analytics service for Visualizing, exploring and deriving insights from data!”

Power BI Portal

https://powerbi.microsoft.com

Power BI Features

https://powerbi.microsoft.com/it-it/features/

“HOW-TO “GET STARTED

Get Started

https://powerbi.microsoft.com/it-it/documentation/powerbi-service-get-started/

https://powerbi.microsoft.com/it-it/get-started/

Power BI Free ebook

https://robertostefanettinavblog.com/2016/06/18/introducing-microsoft-power-bi-free-ebook-from-sqlbi/

Power BI Developer

https://powerbi.microsoft.com/it-it/documentation/powerbi-developer-overview-of-power-bi-rest-api/

https://powerbi.microsoft.com/it-it/get-started/

Nice series of pages about power BI on EID Site (NAVlab Partner)

http://www.eid.it/microsoft-powerbi/

ABOUT DYNAMICS NAV CONTENT PACK & CONNECTOR

Power BI Integration

https://robertostefanettinavblog.com/2016/03/15/power-bi-integration-microsoft-dynamics-nav-microsoft-power-bi/

https://powerbi.microsoft.com/en-us/integrations/microsoft-dynamics-nav/

Microsoft Dynamics NAV with PowerBI.com

https://suvidhablogpost.wordpress.com/2015/10/13/microsoft-dynamics-nav-with-powerbi-com/

Dynamics NAV Content Pack

https://powerbi.microsoft.com/it-it/documentation/powerbi-content-pack-microsoft-dynamics-nav/

https://robertostefanettinavblog.com/2016/02/04/connecting-dynamics-nav-20132015-to-the-nav-content-pack-in-powerbi-com/

Microsoft Dynamics NAV and Power BI (with O365) – Schedule Report Refresh

https://suvidhablogpost.wordpress.com/2014/12/09/microsoft-dynamics-nav-and-power-bi-better-together/

BEST CONNECTORS FOR DYNAMICS USERS

BEST VIDEOS

Power BI Desktop for Beginners: Create your first Power BI report and dashboard in 10 minutes

https://www.youtube.com/watch?v=h6AIAxMEDiw

Webinar Basics of Power BI for NAV users

https://www.youtube.com/watch?v=v9VIfrXwAfo

Power BI and Microsoft Dynamics NAV by Steven Renders

https://www.youtube.com/watch?v=u_nWPvBkU9w

Power BI and Microsoft Dynamics NAV 2016

https://www.youtube.com/watch?v=Qbx0FdlZDBk

Enjoy!

How “not” to increase the batch name


NAV standard, in the case of use of batch name containing numbers, after posting automatically increases the last number existing in batch name (example: Batch 1 > 2 ..AL110A > AL111A.. and so on..)

This functionality is handled “Bydesign” in NAV, if you want to “NOT increase” the number and keep the same number in the batch (example in the case of fixed batch used for example for output and consumption and related numbered machines, former assets) can modify the codeunit 23 “Item Jnl.-Post Batch”

To achieve this, you need to change this line ItemJnlBatch.Name: = INCSTR ( “Journal Batch Name”) in function HandleNonRecurringLine

Function HandleNonRecurringLine

(VAR ItemJnlLine: Record “Item Journal Line”; OldEntryType: ‘Purchase, Sale, Adjmt Positive., Negative Adjmt., Transfer, Consumption, Output,, Assembly Consumption, Output Assembly’)

Original Code
ItemJnlLine3.COPY (ItemJnlLine);
ItemJnlLine3.DELETEALL;
ItemJnlLine3.RESET;
ItemJnlLine3.SETRANGE ( “Journal Template Name”, “Journal Template Name”);
ItemJnlLine3.SETRANGE ( “Journal Batch Name”, “Journal Batch Name”);

IF NOT THEN ItemJnlLine3.FINDLAST
IF INCSTR ( “Journal Batch Name”) <> ” THEN BEGIN
ItemJnlBatch.DELETE;
ItemJnlBatch.Name: = INCSTR ( “Journal Batch Name”);
IF THEN ItemJnlBatch.INSERT;
“Journal Batch Name”: = ItemJnlBatch.Name;
END;

You can change code in this way … for example in case of Outputs Consumptions entries to post from machine from MES..
IF NOT (ItemJnlLine2. “Entry Type” IN [ItemJnlLine2. “Entry Type” :: Consumption, ItemJnlLine2. “Entry Type” :: Output]) THEN
..
//ItemJnlBatch.Name: = INCSTR ( “Journal Batch Name”); // OLD
ItemJnlBatch.Name: = “Journal Batch Name”; // NEW, maintain old batch name, don’t use INCRSTR statement
..

Nice post here on Mibuso about this issue.
Journal batch names post
http://forum.mibuso.com/discussion/44485/journal-batch-names

About “UI Elements Removal” feature


About “UI Elements Removal” feature

 

I never talked about this subject because is “daily bread” for NAV users, however, since some of NAV customers (and some of my readers) are still in old versions of NAV and they want to understand how this technology works, i collected a bit of existing documentation about this topic; below you will find many links from MSDN.

 

About “UI Elements Removal” feature

“UI Elements Removal” feature was introduced with NAV 2015; Microsoft Position at the end of 2014 before NAV 2015 launching date: “To simplify the users’ experience in Microsoft Dynamics NAV 2015, we have introduced the UI Elements Removal feature. The feature can be used to remove user interface (UI) elements, such as fields and actions from pages in Microsoft Dynamics NAV so that the Role Center and pages become simpler to look at, easier to navigate on, and faster to get through.”

Access By Permission on NAV 2015 (v=nav.80).aspx

How to: Try Out the UI Elements Removal Feature based on Demo Permission Set

(v=nav.80).aspx

How System Works with “LicenseFileAndUserPermissions” option active?

When you configure user interfaces in Microsoft Dynamics NAV, you should make sure that the UI Elements Removal field is set to its default, LicenseFileAndUserPermissions, so that you only see the relevant UI elements in the Customize window.

 

What objects will be removed objects by LicenseFileAndUserPermissions option?

All types of UI elements will be removed if they relate to objects that are not included in the license or the user does not have the required permission to the objects:

• Fields, Actions, Page parts

 

“UI elements” removed “By Design”

Directly Related

UI elements that are directly related to an object through the TableRelation or the CalcFormula property can be removed automatically according to the license file and/or user permissions

Not Directly Related

For UI elements that are not directly related to an object, you can use the AccessByPermission property to remove the element according to the user’s permission to a related object

“All types” of UI elements will be removed if they relate to an object to which the user does not have the required permissions:

  • Fields on pages, including FactBoxes
  • Actions on pages, including toolbars and navigation panes

  • Page parts, such as Lines FastTabs

 

About “FOUNDATION” permissions set

A prerequisite for all other permission sets. The FOUNDATION permission set grants access to system tables and application setup tables that are required for most application features to work.

This permission set is “recommended” when using the UI Elements Removal feature to automatically remove UI elements according to user permissions.

To use the LicenseFileAndUserPermissions option in the UI Elements Removal field, you must assign the special FOUNDATION permission set to the user along with the relevant application permission sets that define which application objects the user will access. Unlike the BASIC permission set, the FOUNDATION permission set only grants access to application setup and system tables and requires that other assigned permission sets define which specific application objects can be accessed. For more information, see Special Permission Sets.

Note that all of the 167 default permission sets that are provided with Microsoft Dynamics NAV are ready to support the FOUNDATION permission set to remove UI elements according to user permissions. You must therefore edit the relevant permission sets as explained in the following procedures.

Important ! 1

“If you defined the property for a table field, then all instances of the field on pages are removed from the user’s view. 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.”

Important! 2

“The majority of the permission sets that are provided with the CRONUS demonstration database cannot be combined with the FOUNDATION permission set to fully use the UI Elements Removal feature. You must first create or edit the relevant permission sets to avoid that the user is blocked from performing the involved tasks. For more information, see How to: Create or Modify Permission Sets.”

 

Post Based on MSDN Documentation and others sources

Accessbypermission Property (NAV 2017 HELP on MSDN)

Source https://msdn.microsoft.com/en-us/dynamics-nav/accessbypermission-property

Source https://msdn.microsoft.com/en-us/dynamics-nav/how-to–remove-ui-elements-using-the-accessbypermission-property

 

SAMPLES

NAV Service Configuration

“UI Elements Removal” property with “LicenseFileAndUserPermissions” option

To use this property, the UI Elements Removal field in the Microsoft Dynamics NAV Server Administration tool must be set to LicenseFile or LicenseFileAndUserPermissions.

This Property Applies To

  • Fields in tables (affecting all related fields on pages)
  • Fields on pages

  • Actions on pages

  • MenuSuite items

  • Page parts, such as a Lines FastTab

  •  

    “AccessByPermission “Property Values

    When you choose the AssistEdit button, the Access By Permission window opens.

    Field Description

    Object Type Specify the type of object to which permission is required to display the UI element

    Object ID Specify the object to which permission is required to display the UI element

    Read Specify if Read permission is required to display the UI element

    Insert Specify if Insert permission is required to display the UI element

    Modify Specify if Modify permission is required to display the UI element

    Delete Specify if Delete permission is required to display the UI element

    Execute Specify if Execute permission is required to display the UI element

     

    Sample on table 137 “Sales Invoice Line”, on field “Line Amount”

    Others samples (Standard NAV)

    Table 37 “Sales Line”

     

    Page 42 “Sales Order”

     

    MenuSuite

    Bank Accounts List Page

    Item PropertiesAccess by Permission

     

    AVAILABLE DOCUMENTATION ON MSDN, Microsoft NAVHelp on MSDN

    Accessbypermission Property (NAV 2017)

    https://msdn.microsoft.com/en-us/dynamics-nav/accessbypermission-property

    Removing Elements from the User Interface According to Permissions

    https://msdn.microsoft.com/en-us/dynamics-nav/removing-elements-from-the-user-interface-according-to-permissions

    How to: Remove UI Elements Using the AccessByPermission Property

    https://msdn.microsoft.com/en-us/dynamics-nav/how-to–remove-ui-elements-using-the-accessbypermission-property

    How to: Specify When UI Elements Are Removed

    https://msdn.microsoft.com/en-us/dynamics-nav/how-to–specify-when-ui-elements-are-removed

    ABOUT DEMO PERMISSIONS SETS

    How to: Try Out the UI Elements Removal Feature Based on Demonstration Permission Sets

    https://msdn.microsoft.com/en-us/dynamics-nav/how-to–try-out-the-ui-elements-removal-feature-based-on-demonstration-permission-sets