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.

 

 

 

 

Advertisements

Multiple namespace support in XML Ports – Microsoft Dynamics NAV 2016

Microsoft Dynamics NAV 2016 now enables developers to create XMLPorts which contain more than one namespace. Namespaces are used to distinguish fields and provide uniqueness.

The inclusion of namespaces enables parties to tag elements and resolve any ambiguity.

What is default Namespace?

This property specifies the default namespace for both import and export. The default value is unique for different XMLports.

For example, the following string specifies a namespace: urn:microsoft-dynamics-nav/xmlports/x100, where 100 is the ID of the XMLport.

What is Namespace?

You can use this property to declare one or more namespaces on the XMLport.

To add a namespace, you can choose the AssistEdit button or enter the namespaces directly in the field.

A namespace declaration consists of prefix and the namespace name, which has the format prefix=namespace. Separate multiple namespaces with a comma.

In the XML documents exported or imported by the XMLport, the namespaces declarations are only supported in the <root> element.

For example, if an XMLport has the namespace mynavprefix=mynavnamepace and the default namespace urn:nav:schema:all, then the root element will be as follows:

<Root xmlns:mynavprefix=”mynavnamespace” xmlns=”urn:nav:schema:all”>

To specify a default namespace, leave the Prefix field blank.

You can also specify the default namespace by specifying the namespace in the DefaultNamespace Property and setting the UseDefaultNamespace Property to Yes.

However, there can only be one default namespace. So if you want to specify a default namespace in the Namespace property, you must set the UseDefaultNamespace Property to No.

How to Define Namespace:
Namespace-1

Using Namespace:
Namespace-2

The final XMLport will be as below:
Namespace-3

Now save your XMLport and execute it.
Namespace-4

The output will be similar to below:
Namespace-5

Conclusion:

  • Multiple namespaces are defined in the root element of the XMLport and have their own property editor for defining them.
  • Developers can easily select the namespace via lookups on the element record.
  • XMLports are accessible both for developers and super users. Including the namespace prefix in the core editor lets you see key data while developing.

I will come up with more information in my upcoming posts.

TextEncoding Property (XMLports)

Specifies the text encoding format to use when you use an XMLport to export or import data as text.

Note

The TextEncoding property is only available when the Format Property (XMLports) of the XMLport is set to Fixed Text or Variable Text.

Values

  • MS-DOS (default)
  • UTF-8
  • UTF-16
  • Windows

Remarks

Text encoding is the process of transforming bytes of data into readable characters for users of a system or program. There are several industry text encoding formats and different systems support different formats. Internally, Microsoft Dynamics NAV uses Unicode encoding. For exporting and importing data with an XMLport, Microsoft Dynamics NAV supports MS-DOS, UTF-8, UTF-16, and Windows encoding formats.

You should set the TextEncoding property to the encoding format that is compatible with the system or program that you will be exporting to or importing from. The following sections describe the available text encoding formats.

Tip

You can also set the TextEncoding property in C/AL code. For example, if your XMLport can import or export different formats based on certain conditions, you can change the encoding on the fly depending on the conditions. For example, you can write code such as the following:

currXMLport.TEXTENCODING := TEXTENCODING::Windows;

Example

The following code example illustrates how you can set the encoding during run time.

TextEncoding

Above screenshot is from XMLport 1220 in the CRONUS International Ltd. demonstration database.

Sample Code:

      CASE MyDefinitionTable.”File Encoding” OF

MyDefinitionTable.”File Encoding”::”MS-DOS”:

currXMLport.TEXTENCODING(TEXTENCODING::MSDos);

MyDefinitionTable.”File Encoding”::”UTF-8″:

currXMLport.TEXTENCODING(TEXTENCODING::UTF8);

MyDefinitionTable.”File Encoding”::”UTF-16″:

currXMLport.TEXTENCODING(TEXTENCODING::UTF16);

MyDefinitionTable.”File Encoding”::WINDOWS:

currXMLport.TEXTENCODING(TEXTENCODING::Windows);

The table, MyDefinitionTable, (Imaginary Table) has a field, File Encoding, (imaginary Field) that specifies the encoding for this part of an import.

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: