Advertisements

Now Download Available Microsoft Dynamics NAV 2018

Below are few important links which can be helpful gathering information about new  release of Dynamics Navision 2018.

It is suggested for updated details please visit authorized link in future to find updated information and links not available at the time of wring this post.

If you want to find out more about this release, Please check these links:

 

Products Downloads

Download the appropriate NAV 2018 file below:

Microsoft Dynamics NAV 2018 Partner Translation Toolkit
Download AU-Australia Available in NAV 2018
Download AT-Austria Available in NAV 2018
Download BE-Belgium Available in NAV 2018
Download CA-Canada Available in NAV 2018
Download CZ-Czech Republic Available in NAV 2018
Download DK-Denmark Available in NAV 2018
Download FI-Finland Available in NAV 2018
Download FR-France Available in NAV 2018
Download DE-Germany Available in NAV 2018
Download IS-Iceland Available in NAV 2018
Download IT-Italy Available in NAV 2018
Download MX-Mexico Available in NAV 2018
Download NL-Netherlands Available in NAV 2018
Download NZ-New Zealand Available in NAV 2018
Download NO-Norway Available in NAV 2018
Download ES-Spain Available in NAV 2018
Download SE-Sweden Available in NAV 2018
Download CH-Switzerland Available in NAV 2018
Download UK-United Kingdom Available in NAV 2018
Download US-United States Available in NAV 2018
Download NA-North America Available in NAV 2018
Download RU-Russia Available in NAV 2018
Download W1 Available in NAV 2018

Partner Translation Toolkit

  • Download (coming soon) the Partner Translation Toolkit

 

Language Modules

This table shows a list of all the available NAV 2018 language modules

Language
Download CSY-Czech
Download DAN-Danish
Download DEA-German Austrian
Download DES-German Swiss
Download DEU-German
Download ENA-English Australia
Download ENC-English Canada
Download ENG-English English
Download ENU-English US
Download ENZ-English New Zealand
Download ESM-Spanish Mexico
Download ESP-Spanish
Download FIN-Finnish
Download FRA-French
Download FRB-French Belgium
Download FRC-French Canadian
Download FRS-French Swiss
Download ISL-Icelandic
Download ITA-Italian
Download ITS-Italian Swiss
Download NLB-Dutch Belgium
Download NLD-Dutch
Download NOR-Norwegian
Download RUS-Russian
Download SVE-Swedish

 

Ordering

New customers:

  • Microsoft Dynamics NAV 2018 can be ordered online using Order Central starting December 1, 2017.

  • Customers will be able to deploy Microsoft Dynamics NAV 2017 or Dynamics NAV 2016, if desired, by using the Microsoft Dynamics NAV 2018 license key that will be issued through downgrade rights.

Existing customers:

  • The licenses of Microsoft Dynamics NAV customers with an active enhancement plan will be automatically upgraded to Microsoft Dynamics NAV 2018 in early December 2017.

  • Existing Microsoft Dynamics NAV 2009 customers with an active enhancement plan are entitled to request a transition upgrade of their license to Microsoft Dynamics NAV 2018 through Order Central from December 1, 2017.

License Information

In order to run Microsoft Dynamics NAV 2018, you must have a valid Microsoft Dynamics NAV 2018 license file.  You will find more information about how to correctly license Microsoft Dynamics NAV 2018 in the license guide (partner-only).

 

Microsoft Dynamics NAV 2018 Resources

Support Information

If you are experiencing issues downloading the install file or documentation, please contact ITMBSSUP@microsoft.com.
For technical support questions, contact your partner or, if enrolled in a support plan directly with Microsoft, you can enter a new support request to Microsoft Dynamics Technical Support from PartnerSource under Support >> New Support Request.
You can also contact Microsoft Dynamics Technical Support by phone using these links for country specific phone numbers:

 

For updated details please visit authorized link in future to find updated information and links not available at the time of wring this post.

 

Advertisements

Microsoft Dynamics NAV 2018 Licenses

You have the choice of purchasing Microsoft Dynamics NAV licenses up front, or paying a monthly fee to a service provider.

Perpetual Licensing:

  • You pay affordable upfront starting price, rapid start tools and built in functionality.
  • You license the ERP Solution functionality, and access to that functionality is secured by licensing users.

 

Perpetual License Overview

Service Provider’s Subscription Licensing:

  • You have choice to keep the upfront cost to a minimum through a “per user per month” licensing fee.
  • This helps get started with a low initial cost while leveraging the built-in functionality and rapid start tools.

 

In both licensing models

You have the choice of two Concurrent-user types –

  1. Limited User (Full Read & Limited Write)
  2. Full User (Full Read & Full Write)

Option to give those users access to advanced functionality through the “Extended Pack.”

Starter and Extended Pack License Overview

Starter Pack (Base Pack – Required)

The Starter Pack offers for one price.

  • Core Financials
  • Distributions
  • Professional Services functionality
  • 3 Full User licenses/ Concurrent CALs included
  • Additional Software licenses may be required, like Server, SQL, Office 365, SharePoint. Additional Software must be licensed according to the applicable license terms.

For many businesses, this is the only license component required.

 

Extended Pack (Optional)

The Extended Pack enables customers to integrate core financials and distribution management with broader functionality extensions such as:

  • Manufacturing to support and control the manufacturing environment
  • Warehousing to manage the warehouse to support operations
  • The first three Full Users included in the Start Pack and coming users get to access to all of the incremental functionality.
  • Starter Pack is the prerequisite to the Extended Pack

 

Packaging of Functionality

A Microsoft Dynamics NAV customer can choose whether to deploy the Starter and Extended Pack through the

  • Microsoft Windows client for Microsoft Dynamics NAV
  • Web client for Microsoft Dynamics NAV
  • Microsoft Dynamics NAV Portal framework for Microsoft SharePoint (also known as the Microsoft Dynamics NAV SharePoint client)

All through the same User types.

2018 Functionality -1

 

2018 Functionality -2

Starter Pack is for companies who need

  • Core Financials
  • Trade functionality
  • Basic Financials Management (General Ledger and Fixed Assets)
  • Basic Supply Chain Management
  • Basic Sales Management (Sales, Purchasing and Inventory)
  • Professional Services (Project management)
  • A broad set of Business Insight and reporting functionality as an integral part of the product.
  • A wide range of tools to customize the solution, to meet the needs of every customer together with deep integration opportunities to be made through web services.

 

Extended Pack is for growing, midmarket, or high-functional-needs companies who are looking for an adaptive solution with a broad set of functionality:

  • Warehousing
  • Manufacturing
  • It comes with additional customization objects for doing more extensive customizations.

 

CONFIGURATION AND DEVELOPMENT

Page Designer

  • Change existing pages and enables you to create 100 page objects (included and numbered from 50,000 to 50,099).
  • The Page Designer also enables you to use the Navigation Pane Designer. This means, for example, that you can create new menu items.
  • This module does not include access to C/AL from pages.

Report Designer

  • Change existing reports and create 100 new report objects (numbered from 50,000 to 50,099).
  • This module provides access to C/AL (the C/SIDE application language) from reports used for defining special calculations and business rules.
  • Create new reports from scratch or copy an existing report to use as a starting point.
  • This module enables you to take advantage of the functionality included for developers in the Navigation Pane Designer (for example, creating new menu items).

Table Designer

  • Change existing table definitions and create ten new tables (numbered from 50,000 to 50,009).
  • You can change properties on fields, such as the field name, decimal places, and maximum value, add new fields to existing tables, and create new tables to store data specific to your business.
  • Create keys for sorting information and change or create new FlowFields and FlowFilters for “slicing and dicing” information in new ways.
  • This module does not include access to C/AL from tables.

XMLports (100)

  • Create new or change existing XMLport objects.
  • XMLport Designer provides access to C/AL (the C/SIDE application language) from XMLports used for defining special calculations and business rules.
  • Every XMLport object in Microsoft Dynamics NAV is created using this tool and can therefore be customized easily.
  • This module enables you to create 100 new XMLport objects (numbered from 50,000 to 50,099) and to take advantage of the functionality included for developers in the
  • Navigation Pane Designer (for example, creating new menu items).

Query Designer

  • The Query Designer provides the ability to modify existing queries in the application, as well as create up to 100 new queries.
  • The Query Designer is the main tool for creating objects of the type Query.
  • Query objects retrieve subsets of data spread across the database and are data pumps for various places within the application such as charts and business logic.

 

Application Builder (A la carte)

  • Change the business rules and special calculations that work behind the scenes. Business rules and special calculations are defined in C/AL (the C/SIDE application language).
  • Although this granule includes access to C/AL, it does not permit access to existing C/AL code that updates write-protected tables (for example, postings).
  • With Application Builder, you can create entirely new areas of functionality for your application, enabling you to tailor Microsoft Dynamics NAV to fit your entire organization.
  • It also enables you to create 100 codeunit objects (numbered from 50,000 to 50,099).
  • You can also take advantage of the functionality included for developers in the Navigation Pane Designer (for example, creating new menu items).

 

Solution Developer (A la carte)

  • Change the business rules and special calculations that work behind the scenes. Business rules and special calculations are defined in C/AL (the C/SIDE application language).
  • This module provides access to code that updates write-protected tables to the Merge and Upgrade Tools.
  • You can also Change or create any object type, Use the menu options Translate/Export and Translate/ Import in the Object Designer.

(These options are not available with the Application Builder module).

 

Application Objects

Codeunits (100)

  • 10 Codeunits are included in the Starter Pack
  • 10 Codeunits are included in the Extended Pack.
  • Additional groups of 100 are available in the Customization suite.

Reports (100)

  • Additional groups of 100 are available in the Customization suite.

Tables (10)

  • 10 tables are included with the Extended Pack.
  • Additional groups of 10 are available in the Customization suite.

XMLports (100)

  • 100 XMLports are included with the Extended Pack.
  • Additional groups of 100 are available in the Customization suite.

Queries (100)

  • Additional groups of 100 are available in the Customization suite.

Pages (100)

  • 100 Pages are included with the Extended Pack.
  • Additional groups of 100 are available in the Customization suite.

 

For more details you can check here.

 

 

 

 

Customers with Enterprise Agreement who already have SQL Server Licenses, can use them on Azure Virtual Machines

Now  Microsoft Enterprise Agreement customers can bring existing licenses to run SQL Server on Azure Virtual Machines. Since the launch of Azure Virtual Machines, customers can already run SQL Server on Azure Virtual Machines through several existing SQL Server images available in the Azure Gallery, or bring their own images to Azure.

These images and capabilities will continue to be supported so customers can continue to take advantage of pay per use licensing for SQL Server on Azure Virtual Machines.

 

Starting this week, customers with Enterprise Agreement who already have SQL Server Licenses, can use them on Azure Virtual Machines with Microsoft-certified (BYOL) gallery images. These images will not charge for SQL Server licensing, just for compute cost.

For more details see the Link.

 

Uploading License to Tenant in Multitenant Environment

When we deploy solution for Multitenant Environment ever Tenant will be required a Separate License. Depending upon the License agreement with Microsoft every Tenant will either share same License or individual License.

Assume we are implementing Distributor Management System. Where every Tenant is a different Business entity linked with the Parent Group.

In this case the Server & Network is provided by the Parent Group and other Business group will share information but they will use their specific License to use the system, doesn’t matter who pays for fee.

In any case we need to upload License to each database in Multitenancy.

Import-NAVServerLicense

Imports a license file into a Microsoft Dynamics NAV database.

Syntax

Parameter Set: __AllParameterSets

Import-NAVServerLicense [-ServerInstance] <String> [-Database <LicenseDatabase> ] [-Force] [-Tenant <TenantId> ] [-Confirm] [-WhatIf] [ <CommonParameters>]

Parameter Set: LicenseDataSet

Import-NAVServerLicense [-LicenseData] <Byte[]> [-Force] [-Confirm] [-WhatIf] [ <CommonParameters>]

Parameter Set: LicenseFileSet

Import-NAVServerLicense [-LicenseFile] <String> [-Force] [-Confirm] [-WhatIf] [ <CommonParameters>]

Detailed Description

Use the Import-NAVServerLicense cmdlet to import a license file into a Microsoft Dynamics NAV database. If the Microsoft Dynamics NAV Server account specified does not have access to the location where the license file is stored, an error results. Check the Event Log on the Microsoft Dynamics NAV Server computer to see what permissions are required.

After importing a new license, restart all Microsoft Dynamics NAV Server instances to activate the license for client users.

Parameters

-Database<LicenseDatabase>

Specifies the database into which to import the license file. The possible values are described in the following list:

Default = 0

Default; overrides the license file currently in use.

Master = 1

Forces the license file to be global.

NavDatabase = 2

Forces the license file to be local and stored in the Microsoft Dynamics NAV database that is used by the specified Microsoft Dynamics NAV Server instance.

Tenant = 3

Forces the license file to be local and stored in the Microsoft Dynamics NAV database that is used by the tenant that is specified in the Tenant parameter.

Aliases none
Required? false
Position? named
Default Value none
Accept Pipeline Input? false
Accept Wildcard Characters? false

-Force

Forces the command to run without asking for user confirmation.

Aliases none
Required? false
Position? named
Default Value none
Accept Pipeline Input? false
Accept Wildcard Characters? false

-LicenseData<Byte[]>

Specifies the content retrieved from the certificate file by using the Get-Content cmdlet. For more information, see the examples.

Aliases none
Required? true
Position? 2
Default Value none
Accept Pipeline Input? false
Accept Wildcard Characters? false

-LicenseFile<String>

Aliases none
Required? true
Position? 2
Default Value none
Accept Pipeline Input? false
Accept Wildcard Characters? false

-ServerInstance<String>

Specifies the name of a Microsoft Dynamics NAV Server instance. The default instance name is DynamicsNAV80. You can specify either the full name of an instance (such as MicrosoftDynamicsNavServer$myinstance) or the short name (such as myinstance).

Aliases none
Required? true
Position? 1
Default Value none
Accept Pipeline Input? True (ByValue, ByPropertyName)
Accept Wildcard Characters? false

-Tenant<TenantId>

Specifies the ID of the tenant in which you want to import the license, such as Tenant1. This parameter is required unless the specified service instance is not configured to run multiple tenants.

Aliases Id
Required? false
Position? named
Default Value none
Accept Pipeline Input? True (ByPropertyName)
Accept Wildcard Characters? false

-Confirm

Prompts you for confirmation before running the cmdlet.

Required? false
Position? named
Default Value false
Accept Pipeline Input? false
Accept Wildcard Characters? false

-WhatIf

Shows what would happen if the cmdlet runs. The cmdlet is not run.

Required? false
Position? named
Default Value false
Accept Pipeline Input? false
Accept Wildcard Characters? false

<CommonParameters>

This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer, and -OutVariable.

Inputs

The input type is the type of the objects that you can pipe to the cmdlet.

  • System.String

You can pipe a string that contains a Microsoft Dynamics NAV Server instance name to the cmdlet.

Outputs

The output type is the type of the objects that the cmdlet emits.

  • None

This cmdlet does not generate any output.

Examples

This example imports a license file that is named “fin.flf” from the current directory into the default database.

C:\PS>Import-NAVServerLicense DynamicsNAV80 -LicenseData ([Byte[]]$(Get-Content -Path “fin.flf” -Encoding Byte))

This example imports a license file that is named “fin.flf” from the current directory into the local Microsoft Dynamics NAV database that is used by the MyInstance Microsoft Dynamics NAV Server instance.

C:\PS>Import-NAVServerLicense MyInstance -LicenseData ([Byte[]]$(Get-Content -Path “fin.flf” -Encoding Byte)) -Database NavDatabase

This example imports a license file that is named “fin.flf” from the current directory into the master database.

C:\PS>Import-NAVServerLicense ‘MicrosoftDynamicsNavServer$MyInstance’ -LicenseData ([Byte[]]$(Get-Content -Path “fin.flf” -Encoding Byte)) -Database Master

This example imports a license file that is named “fin.flf” from the current directory into the database that is used by the specified tenant, Tenant1.

C:\PS>Import-NAVServerLicense ‘MicrosoftDynamicsNavServer$MyInstance’ -LicenseData ([Byte[]]$(Get-Content -Path “fin.flf” -Encoding Byte)) -Database Tenant –Tenant Tenant1

Let import the license to the Tenants which we created in our earlier post.

If you missed previous post you can find it here. Adding Tenants to multitenancy Environment

I have created the Folder and placed my Tenants License in this.

License-1

Set-ExecutionPolicy unrestricted -Force

Import-Module ‘C:\Program Files\Microsoft Dynamics NAV\80\Service\NavAdminTool.ps1’

Import-NAVServerLicense MTenantDemo -Tenant ‘Tenant-1’ -LicenseData ([Byte[]]$(Get-Content -Path “C:\User Data\NAV 2015\MultiTenantDemo\Tenant License\Tenant-1.flf” -Encoding Byte))

Import-NAVServerLicense MTenantDemo -Tenant ‘Tenant-2’ -LicenseData ([Byte[]]$(Get-Content -Path “C:\User Data\NAV 2015\MultiTenantDemo\Tenant License\Tenant-2.flf” -Encoding Byte))

Import-NAVServerLicense MTenantDemo -Tenant ‘Tenant-3’ -LicenseData ([Byte[]]$(Get-Content -Path “C:\User Data\NAV 2015\MultiTenantDemo\Tenant License\Tenant-3.flf” -Encoding Byte))

Import-NAVServerLicense MTenantDemo -Tenant ‘Tenant-4’ -LicenseData ([Byte[]]$(Get-Content -Path “C:\User Data\NAV 2015\MultiTenantDemo\Tenant License\Tenant-4.flf” -Encoding Byte))

Import-NAVServerLicense MTenantDemo -Tenant ‘Tenant-5’ -LicenseData ([Byte[]]$(Get-Content -Path “C:\User Data\NAV 2015\MultiTenantDemo\Tenant License\Tenant-5.flf” -Encoding Byte))

Copy the above Script and paste into the Microsoft Dynamics NAV 2015 Administration Shell.

License-2

Our License have now successfully uploaded to respective databases. As the message suggest we need to re-start the service so that new License comes into effect.

You can use above Script to Upload License to individual Tenants, License could be different or same depends how you discussed with Microsoft and purchased.

AccessByPermission Property – in Navision 2015

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.

AccessByPermission-1
AccessByPermission-2
AccessByPermission-3

Depending on the setting in the UI Elements Removal field in the Microsoft Dynamics NAV Server Administration tool, only user interface (UI) elements on objects in the license or on objects that the user has permissions to will appear in the user interface.

AccessByPermission-4

To make full use of the LicenseFileAndUserPermissions option in the UI Elements Removal field, it is recommended that you assign the special permission set, FOUNDATION, along with the relevant permission sets that define which application objects the user will access.

AccessByPermission-5

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. You must first create or edit the relevant permission sets to avoid that the user is blocked from performing the involved tasks.

If you only use the LicenseFile option in the UI Elements Removal field, then you do not have to edit any permission sets as they will not affect which UI elements are removed.

To specify when UI elements are removed
  1. Open the Microsoft Dynamics NAV Server Administration
  2. In the UI Elements Removal field, choose the relevant option as described in the following table.
Option Description
None All UI elements are displayed, even if the license file does not include the related object and the user does not have permissions to the related object.
LicenseFile A UI element is removed if the related object is not included in the license file.
LicenseFileAndUserPermissions A UI element is removed if the related object is not included in the license file and the user does not have permissions to the object as defined in the AccessByPermission property for the related UI element.

By default, this option is selected.

AccessByPermission-6

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.

When you develop in Microsoft Dynamics NAV, you should make sure that the UI Elements Removal field is set to its default, None, to make sure that all UI elements are visible when you review your development in the UI.

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 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.

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

Note

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

Property Value

When you choose the AssistEdit button, the Access By Permission window opens. Fill the fields as described in the following table.

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.
or Insert Specify if Insert permission is required to display the UI element.
or Modify Specify if Modify permission is required to display the UI element.
or Delete Specify if Delete permission is required to display the UI element.
or Execute Specify if Execute permission is required to display the UI element.

AccessByPermission-7

Note

If multiple permissions are selected, then one or the other applies.

Example: Remove the Unit Price field if the user does not have permission to the Sales Price table

Open table 27, Item Card, with the Table Designer.

View the properties of field 18, Unit Price.

For the AccessByPermission property, choose the AssistEdit button in the Value field.

In the Access By Permission window, fill the fields as described in the following table.

Field Description
Object Type TableData
Object ID Sales Price
Read Select
Insert Select
Modify Leave blank
Delete Leave blank
Execute Leave blank

Close the Access By Permission window and save the changes on table 27.

All instances of the Unit Price field on pages are now removed if the user does have Read or Insert permission to the Sales Price table.

AccessByPermission-8

Important

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.

Note

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.

Not 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.

To experience how UI elements are removed for a user performing the task to create and edit a new customer, you can create a sample user interface based on default permission sets provided with Microsoft Dynamics NAV.

Special Permission Sets

The following permission sets have special definitions that you should be aware of as you implement permissions and security for Microsoft Dynamics NAV users.

Permission set Definition
SUPER Can read, use, update, and delete all data and all application objects in the scope of your license. Microsoft Dynamics NAV requires that at least one user be assigned this permission set in each database.

You cannot modify permissions for the SUPER permission set.

SUPER (DATA) Can read, use, update, and delete all data. You typically assign this permission set to an accounting manager who needs to work with all data but does not need to change Microsoft Dynamics NAV.

This permission set does not give access to the Object Designer.

SECURITY Can create new users and assign them the same permission sets. Must be able to access the User, User Property, Permission Set, and Access Control tables.

For example, you can create a SECURITY permission set that includes the four required tables and any additional permissions that you want to include. You can then assign this permission set to a user who is a department administrator. This user can then administer permissions for other users in their department.

Only a user who has the SUPER permission set can create and modify a SECURITY permission set. Users who have this permission set can assign the same permissions to other users, but they cannot assign themselves the SUPER permission set.

BASIC Grants Read access to almost all application tables and all system tables.

The main purpose of this permission set is to enable the client to open and show all pages.

When you create a new database, you must import the BASIC permission set from an XML file.

FOUNDATION 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.

Note

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

Important

Most of the contents you find in this blog will be either inherited from MSDN or Navision Developer IT Pro Help. Some places images are also directly taken from these sites. Purpose is simple to try those stuffs and re-produce adding few things as per my understanding to make easy understanding for others and quick reference.

Here nothing under my own brand or authorship of the content. At any point of time we are just promoting Microsoft stuffs nothing personnel with same.

Hope stuffs used here will not violate any copyright agreement with them. In case by mistake or in-intestinally it happens and the Microsoft feels these should not be used Microsoft have full right to inform me about same and will be glad to take down any such content which may be violating the norms.

Purpose is to promote Navision and share with community.

FB Profile

Like FB Page

%d bloggers like this: