On October 11 Microsoft unveiled a First Look at Dynamics 365, the next generation of intelligent, purpose-built business applications that work seamlessly together to help manage specific business functions across Sales, Customer Service, Operations, Financials, and beyond. PowerApps, Microsoft Flow, and the Common Data Service are built-in to make Dynamics 365 easily adaptable to the specific needs of any organization.

On October 28 Microsoft unveiled Microsoft Dynamics NAV 2017

Now when exploring NAV 2017 and Dynamics 365 found some differences as follows

NAV 2017	Dynamics 365
NAV 2017 providing functionality like Service,Jobs,Manufacturing etc	Dynamics 365 not providing modules with required functionalities
NAV 2017 providing required financial management in every company	Dynamics 365 is missing with some key functionalities like inter company transactions.
NAV 2017 provides wide range of functionality in Purchase & Inventory Management	Dynamics 365 is missing with functionality like Item tracking,Purchase quote,Item charge
In NAV 2017 we can use links to attach external documents,use comments to add additional details	Dynamics 365 is lacking these functionalities at the moment
NAV 2017 support development through extensions as well as you can modify existing functions and code units	Dynamics 365 develops through extensions.

The above difference are based on the broad view of both applications and Dynamics 365 is in preliminary stage at the moment and in future it will come with lot more functionalities which will support in day to day activities to user.

Stay Tuned for more.

Cheers

In NAV 2017 one new parameters added in Sales & Receivables Setup i.e Default Item Quantity.

By default this parameter is unchecked .When you check this parameters then this will add by default quantity as 1 when you add Item in Sales Order.

Prior to NAV 2017 Navigate Page type was not supported in Web Client .When user try to access Navigate page then it throws error saying that use Card Page type.

In NAV 2017 Navigate page type are supported and user can view the navigated entries in Web Client.

There is one new parameter introduced in NAV 2017 reports that is ‘Saved Settings’

Depending on the report that is run, request page that lets you to set certain options and filters for changing the data that is included in the generated report. A report can include one or more saved settings that you can apply to the report from the request page. Saved settings are basically predefined options and filters. Using saved settings is a fast and reliable way to consistently generate reports that contain the correct data.

You can see the saved settings that are available to you for a report in Saved Settings section of the report request page. There is always at least one saved settings entry, which is called Last used options and filters. These settings are the option and filter values that were used the last time you ran the report.

How to Apply Saved Settings to Report

1) Open report and report request page appears

2) In the Saved Settings section of the page, set the Name field to the saved settings that you want to use

How to Create Saved Settings for Users

If you have the proper permissions, you can view, create, and modify the saved settings for all reports for all users in company. You can assign saved settings for a report to individual users or all users in the company.

You manage saved settings from page 1506 Reports Settings.

From this page you can create new settings for all users or any individual users also.

Note: The saved settings feature on reports is only relevant when the SaveValues property of the request page is set to Yes. The SaveValues property is set in the development environment.

Following cumulative updates release for this month for Microsoft Dynamics Navision

NAV 2016 :- You can download the cumulative update from KB 3202888 – Cumulative Update 13 for Microsoft Dynamics NAV 2016 (Build 47256).

NAV 2015 :- You can download the cumulative update from KB 3202890  – Cumulative Update 25 for Microsoft Dynamics NAV 2015 (Build 47254).

NAV 2013 :- You can download the cumulative update from KB 3202886  – Cumulative Update 37 for Microsoft Dynamics NAV 2013 R2 (Build 47259).

NAV 2013 R2 :- You can download the cumulative update from KB 3202886  – Cumulative Update 37 for Microsoft Dynamics NAV 2013 R2 (Build 47259).

Before you install a cumulative update in a production environment, take the following precautions:

1.    Test the cumulative update in a non-production environment.

2.    Make a backup of the system or computer where the cumulative update is to be installed.

I wrote about this cool feature introduced in NAV2017 in my earlier blog Account categories. Today we will see more in detail how this is used in NAV2017

We have to classify the Ledger accounts specially for reporting purpose and creating balance sheet and income statement.

User can define the Account category and subcategory in G/L Account master against each ledger account

Based on this NAV provided the screen to see the balances against the categories. This page gives overview of

This page show detail with balances for categories and sub categories defined. The fact boxes will show the GL Accounts associated with Account categories and subcategories which is tagged in master.

Based on this categories needed reports added in NAV2017 i.e. Balance Sheet and Income Statement which we initially creating using account schedules and now we have readily available in NAV2017.

Reports are available under Financial Management.

Cheers….

In NAV 2017 some new C/AL properties has been introduced by looking at the user requirement . These properties are introduced to give user more flexibility over the UI and give more user friendly experience.

Application Area:-

This property set application areas that apply to the control and this property applies to

• Page field, part, and action controls.
• Report request page field controls.
• MenuSuite items

This property used to hide the control in user interface .i.e. You need to tag the controls by specifying the text string with comma separated values Example If you want tag Vendor list in Menu Suite then you can mention #Basic,#Suite in applicationarea

Note :- This property is working based on the table 9178 application area setup .You can define more but still in future release it may be change again.

Gesture:-

This property specially for touch interface devices like Phone client.

The property has the following values:

Previously I wrote about new feature Notifications in following blog Notifications.Today will explain how to write/develop notifications.

Notifications provide a programmatic way to send non-intrusive information to the user interface (UI) in the Dynamics NAV Web client. Notifications differ from messages initiated by the MESSAGE function. Messages are modal, which means users are typically required to address the message and take some  corrective action before they continue working. On the other hand, notifications are non-modal. Their purpose is to notify users  about a current situation, but do not require any immediate action or block users from continuing with their current task. For example, you could have a notification that a inventory balance is low or customer have overdue balance etc.

Notifications are not stopping the users from going ahead as it will display the notifications in notification bar i.e on top of the page (just like validation errors).User can dismiss the notification and continue working.

• Multiple notification will appear chronological order from top to bottom
• Notification remain available until page instance or until user dismiss it.
• Sub page notification will also display on top of page.
• Validation will be shown before notification

By using the Notification and NotificationScope data types and functions in C/AL, you can add code to send notifications to users. The following table provides an overview of the available functions. The sections that follow provide additional information about how to create notifications.

3) Adding action to notification

4) Sending data with a notification

EXAMPLE

Suppose user want to get notification for Inventory zero then one can write

Define ItemInventoryNotification as Notification Datatype

Item.Get(“No.”);

Item.CALCFIELDS(Item.Inventory);

If Item.Inventory<=0 THEN BEGIN

ItemInventoryNotification.MESSAGE(‘Inventory zero for this item’);

ItemInventoryNotification.SCOPE:=NOTIFICATION::LocalScope;

ItemInventoryNotification.SEND;

END;

Window Client:-

Web Client:-

Stay Tuned for more updates and keep testing….

Cheers…..

NAV 2017 web client is more improved than previous version web client and supporting most of the same features as Windows client and of course with some small differences. Lot of limitations has been removed but still some limitations are there and may be these limitations will be improved in upcoming CU’s and versions. The way Microsoft promoting Web client ,definitely web client will be option in upcoming years.

Following are some of the limitations of Web Client

General Features

The following table lists general features that are not fully supported by Microsoft Dynamics NAV Web client.

Objects

The following object types are not supported by Microsoft Dynamics NAV Web client.

Pages Features

This section includes page features that are not fully supported by Microsoft Dynamics NAV Web client.

General Page Features

The following page features are not fully supported by Microsoft Dynamics NAV Web client.

Page Properties

The following page properties are not supported or are partially supported by Microsoft Dynamics NAV Web client.

Note

Properties that are not supported are ignored by Microsoft Dynamics NAV Web client.

Report Features

The following table includes reports features that are not supported or are partially supported by Microsoft Dynamics NAV Web client.

C/AL Triggers

This section lists the C/AL triggers that are not fully supported by Microsoft Dynamics NAV Web client. Triggers that are not supported are not invoked on an object at runtime.

Page Triggers

The following page triggers are not fully supported by Microsoft Dynamics NAV Web client.

C/AL Functions

This section lists the C/AL functions that are not supported by Microsoft Dynamics NAV Web client. Except when indicated otherwise, if you use a function that is not supported, you will receive an error at runtime.

User Interface Features

The following end-user interface features are not supported by Microsoft Dynamics NAV Web client.

Partially supported means that the feature does not have all the capabilities as it does in Microsoft Dynamics NAV Windows client or it works differently than in Microsoft Dynamics NAV Windows client.

Properties which are not supported are ignored by Web Client.

Still I am testing for web client and will come up with more updates. Stay tuned.

Source:- MSDN

Cheers!!!