You can download NavDesk from the following links: These files can be used for installing international maps whilst you are overseas or you have lost your install disc. You can also use this software to load custom POIs, installing subscriptions, travel guides, recovering software keys or registering a PiN against a Device. Your Mac OS X desktop has a Dashboard, dock, and trash can. Widgets and icons provide easy access to applications and tools no matter what your Apple computer's desktop wallpaper or theme. Knowing how to add Dashboard widgets or delete dock icons helps you work faster. NPlus allows you to update NDrive 11 application and maps running on Portable Navigation Devices (PNDs) and Car Radio (In-Dash units). Maps, voices, aerial photography, TTS, funny voices. 62.0k members in the osx community. Reddit's community for users, developers, and hackers of Mac OS X – the desktop operating system from Apple.

-->

Syntax

Description

Download

Use the New-NAVServerUser cmdlet to create a new Business Central user.Anonymous accounts such as S-1-1-0 (Everyone) and S-1-5-7 (Anonymous) are not allowed.

Examples

EXAMPLE 1

This example creates a new Business Central user based on the built-in NT AUTHORITYNETWORK SERVICE account in Windows.

EXAMPLE 2

This example creates a new Business Central user based on a Windows user account that has the user name Chris from the domain Cronus.

EXAMPLE 3

This example creates a new Business Central user that has the user name Chris and a password that is entered as a secure string (****).

EXAMPLE 4

This example creates a new Business Central user that has the user name Chris and password Password1234.

EXAMPLE 5

This example creates a new Business Central user that has the user name Chris and a web services access key for logging on to Business Central.The web services acces key expires on 01-01-2014.

Parameters

-ApplicationId

Identifies the application this user represents.This requires that the application is registered in Azure Active Directory.The application is identified by its 'client id' in Azure Active Directory.

Type:Guid
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

Specifies the Microsoft account that this user uses to access Office 365 and SharePoint.The authentication email address must be the Microsoft account that the users log in to Office 365 with, such as an account from Windows Azure Active Directory (AAD).

Type:String
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

Specifies the authentication key for authentication with Windows Azure Access Control Service (ACS). This key must be at least 8 characters and contain combination of uppercase and lowercase letters and numbers. The authentication key is entered by the user the first time that the user logs on to Business Central.

Type:String
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

Forces the user to change the password the next time that the user logs on.

Type:SwitchParameter
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

Specifies which of the Business Central companies will be used as the user�s default company in the clients. Be aware that if you set this parameter, you will not be able to remove the user later if desired. You will only be able to disable the user.

Type:String
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

Prompts you for confirmation before executing the command.

Type:SwitchParameter
Aliases:cf
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

Specifies the contact email address for the Business Central user.

Type:String
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

Creates a web services access key for the user. The web service access key is automatically generated. This parameter is relevant only when Business Central is configured to use either the NavUserPassword or AccessControlService credential type for authenticating users.The web service access key is used instead of a password to authenticate web service requests, such as SOAP and OData.

Type:SwitchParameter
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

Specifies when the user's access to Business Central expires.

Type:DateTime
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

Forces the command to run without asking for user confirmation.

Type:SwitchParameter
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

Specifies the user's full name.This is typically includes the user's first and last name.On the User card in Business Central, this value appears in the Full Name field.The value typically includes the user's first and last name.

Type:String
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

Specifies which of the installed Business Central languages will be used as the user�s default language in the clients. Set the value to a valid language culture name, which typically has the format nn-NN, such as en-US or da-DK. Be aware that if you set this parameter, you will not be able to remove the user later if desired. You will only be able to disable the user.

Type:String
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

Specifies the license type to assign the user.The parameter has the following values (you can use either the text value or the integer in parenthesis):

Full (0)

Limited (1)

DeviceOnly (2)

WindowsGroup (3) - Use this license type if the Business Central user is based on a Windows group in Active Directory. This user account cannot log on to Business Central.Instead, it is used to map the permission set to the individual Windows users in the Windows user group. You must apply the license type to the individual users in the Windows user group.

External (4)

Type:LicenseType
Accepted values:Full, Limited, DeviceOnly, WindowsGroup, External, ExternalAdmin, ExternalAccountant, Application
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

Specifies a protected password for the Business Central user.The password is only used when the credential type for authenticating users who try to access Business Central is set to NavUserPassword.

Type:SecureString
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

Specifies the ID of the extension that defines the profile to assign the user. When assigning a profile from the System scope, don't use this parameter.

Type:Guid
Position:Named
Default value:00000000-0000-0000-0000-000000000000
Accept pipeline input:False
Accept wildcard characters:False

Specifies the ID of the profile to assign the user.

Type:String
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

Specifies the name of a Business Central Server instance, for example, BC or myinstance.You can specify either the full name of an instance, such as MicrosoftDynamicsNavServer$myinstance or the short name such as myinstance.

Type:String
Position:0
Default value:None
Accept pipeline input:True
Accept wildcard characters:False

Specifies the security identifier (SID) of the Windows user account for the user that you want to set up as a Business Central user. The SID is a unique value that identifies a Windows user account. You can use the Sid, UserName, or WindowsAccount parameters to create the user. If you use the Sid parameter, then you cannot set the UserName or WindowsAccount parameters.

Type:String
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

Specifies the state of the user's account and access to Business Central.The parameters has the following values (you can use either the text value of the integer value in parenthesis:

Enabled (0)

Disabled (1)

Type:NavUserState
Accepted values:Enabled, Disabled
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

Specifies the ID of the tenant of the Business Central Server instance on which to add the user. You can omit the Tenant parameter only if the Business Central Server instance is not configured to run multiple tenants.

Type:TenantId
Aliases:Id
Position:Named
Default value:None
Accept pipeline input:True
Accept wildcard characters:False

Specifies the user name for the new Business Central user. The user name appears in the User Name field in a user's account in Business Central. You can use the UserName, WindowsAccount or Sid parameters to identify the user. If you use the Username parameter, then you cannot use the Windows Account or Sid parameters.

Type:String
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

Specifies the date and time that the user's web services access key expires.

Type:DateTime
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

Describes what would happen if you executed the command without actually executing the command.

Type:SwitchParameter
Aliases:wi
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

Specifies the Windows account user name of the user that you want to set up as a Business Central user. The value has the domainusername format. You can use the WindowsAccount, UserName, or Sid parameters to create the user. If you use the WindowsAccount parameter, then you cannot use the UserName or Sid parameters.

Type:String
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

Inputs

System.String

You can pipe a string that contains a Business Central Server instance name to the cmdlet.

Outputs

None

Notes

Because cmdlets do not execute application code, if there is any logic on application objects that are associated with creating or modifying users from the client, be aware that the logic will not be executed when you run the cmdlet.

Related Links

Microsoft Dynamics NAV 2018
Role Center from Microsoft Dynamics 2018, North American edition
Developer(s)Microsoft
Stable release
Microsoft Dynamics NAV 2018 (subsequent versions were rebranded Business Central)
Operating systemWindows Server 2008 and later, Windows 7 SP1 and later
TypeEnterprise resource planning
Websitemicrosoft.com/dynamics365/nav-overview

Microsoft Dynamics NAV is an enterprise resource planning (ERP) app from Microsoft. The product is part of the Microsoft Dynamics family, and intended to assist with finance, manufacturing, customer relationship management, supply chains, analytics and electronic commerce for small and medium-sized companies and local subsidiaries of large international groups. For modifications of the system, the proprietary programming language C/AL is used.

Microsoft Dynamics NAV has been superseded by Microsoft Dynamics 365 Business Central.[1][2]

History[edit]

Microsoft Dynamics NAV originates from Navision, a suite of accounting applications which Microsoft acquired in 2002.

Navision originated at PC&C A/S (Personal Computing and Consulting), a company founded in Denmark in 1984. PC&C released its first accounting package, PCPlus, in 1985—a single-user application with basic accounting functionality. There followed in 1987 the first version of Navision,[3] a client/server-based accounting application that allowed multiple users to access the system simultaneously. The success of the product prompted the company to rename itself to Navision Software A/S in 1995.

The Navision product sold primarily in Denmark until 1990. From Navision version 3 the product was distributed in other European countries, including Germany and the United Kingdom.

In 1995 the first version of Navision based on Microsoft Windows 95 was released.

In 2000, Navision Software A/S merged with fellow Danish firm Damgaard A/S (founded 1983) to form NavisionDamgard A/S.[4] In 2001 the company changed its name to 'Navision A/S'.

On July 11, 2002 Microsoft bought Navision A/S to go with its previous acquisition of Great Plains. Navision became a new division at Microsoft, named Microsoft Business Solutions, which also handled Microsoft CRM.[5]

In 2003 Microsoft announced plans to develop an entirely new ERP system (Project Green). But it later decided to continue development of all ERP systems (Dynamics AX, Dynamics NAV, Dynamics GP and Dynamics SL). Microsoft launched all four ERP systems with the same new role-based user-interface, SQL-based reporting and analysis, SharePoint-based portal, Pocket PC-based mobile clients and integration with Microsoft Office.

In September 2005 Microsoft re-branded the product and re-released it as Microsoft Dynamics NAV.[6]

In December 2008 Microsoft released Dynamics NAV 2009, which contains both the original 'classic' client, as well as a new three-tierGUI called the RoleTailored Client (RTC).[7]

In October 2013, Microsoft released Dynamics NAV 2013, which was available with the RTC only, and introduced support for 64-bit Windows operating systems as well as a redesign of storing dimension sets, interoperability with SharePoint, and a web client.

In October 2014, Microsoft released Dynamics NAV 2015. This version's improvements feature the tablet client, document reporting using Microsoft Word, Bank Integration, and more.

In October 2015, Microsoft released NAV 2016 features enhancements in reporting and email integration, deferral accounting, and posting preview function.

Microsoft continues to invest in Dynamics NAV and is now on an annual release cycle.

The product itself has gone through several name changes over the time. Initially 'Navigator' was used in Denmark, although most Danish users knew it as 'IBM-Navigator', as IBM distributed the software. Internationally it was sold as 'Navision', except in the U.S., where it was called 'Avista'.The names 'Navision Financials', 'Navision Solutions', 'Navision Attain', 'Microsoft Business Solutions - Navision Edition', and—as of 2014—'Microsoft Dynamics NAV' (pronounced [næv] or, contrary to standard rules of reading shortened words, [en ei 'vi:], except in the U.S. where most[quantify] customers simply say 'nav'—short for 'Navision') have all been used to refer to this product.

Versions[edit]

Windows based Navision versions from 1.00 onwards were:

  • Navision Financials 1.00
  • Navision Financials 2.00
  • Navision Financials 2.50
  • Navision Financials 2.60
  • Navision Financials 2.65: Introducing the NAS (Navision Application Server)
  • Navision Solutions 3.00
  • Navision Attain 3.01
  • Navision Attain 3.10
  • Navision Attain 3.60
  • Microsoft Business Solutions Navision 3.70
  • Microsoft Business Solutions NAV 4.00
  • Dynamics NAV 5.00
  • Dynamics NAV 2009: ('6.00') 2009, 2009 SP1, 2009 R2
  • Dynamics NAV 2013: ('7.00') 2013, ('7.1') 2013 R2
  • Dynamics NAV 2015: ('8.00') 2015
  • Dynamics NAV 2016: ('9.00') 2016
  • Dynamics NAV 2017: ('10.00') 2017
  • Dynamics NAV 2018: ('11.00') 2018, ('12.00) 2018 R2
  • Microsoft Dynamics 365 Business Central: ('13.00')
  • Microsoft Dynamics 365 Business Central Spring Release: ('14.00')
  • Microsoft Dynamics 365 Business Central Wave 2: ('15.00')
  • Microsoft Dynamics 365 Business Central Wave 1 2020:('16.00')
  • Microsoft Dynamics 365 Business Central Wave 2 2020:(“17.00”)

Features[edit]

Before NAV 2013, Microsoft Dynamics NAV gave administrators the option of using either a native database server or Microsoft SQL Server, as the DBMS. SQL Server is now the exclusive database option for NAV. Retiring the old 'Native database' has given way to long-awaited improvements in reducing/eliminating database locking, which can occur when hundreds or thousands of users are using the same data at once.

Document reporting in NAV 2013 is based on the RDLC 2008 format (RDLC 2010 in NAV 2013 R2). Reports are edited partly in the NAV Development Environment and Visual Studio. NAV 2013 R2 includes a free report editor. Any reports will render in either Screen preview, PDF, Word or Excel formats, depending on the users needs.

NAV 2013 also supports the OData format. With OData support in NAV 2013, Excel pivoting can now be done without knowledge to SQL specifics, limited to only those fields available for RTC views.

Running NAV on SQL has made it possible to use MS Excel PowerPivot to access all data in NAV via SQL login. But with OData support in NAV 2013, Excel pivoting can now be done without knowledge of SQL specifics, thus giving 100% access to filter any data in NAV, with no restrictions. (Versions 2009 R2 and later allow the default restriction of 5,000 records to be changed via editing a config file.)

With NAV 2009, Microsoft introduced a completely new client interface named the RoleTailored Client (abbreviated RTC). The RTC allows tailoring the NAV experience by individual users, based on their job responsibilities, through toolbar/menu layouts called Profiles and homepages called Roles. In one-person offices this can be a disadvantage as users must re-login, after changing their Role or by configuring a different user name/profile, to access the varying RTCs they would want to use. In multi-person offices, in the absence of either of these options, it can lead to confusion when attempting to help individuals who may have wildly different screen layouts and settings. Roles are assigned either per user or by groups. Individual users can customise their toolbar and navigation pane, or administrators can customise the layouts for all users in a given Profile; they can then disable individual customisation for users in that Profile. Some levels of customisation are only available through the NAV Development Environment.

The NAV client interface previously available in versions 5 and older was retained in NAV 2009, but renamed the Classic Client, making NAV 2009 the only 'hybrid' version, offering both the Classic and the RTC interface.

While the Classic Client supports both Native and SQL databases, the RoleTailored Client requires a SQL database. Additionally, SQL database logins are not supported with the RoleTailored Client.

In October 2012, Microsoft released NAV 2013, which discontinued support for the Classic Client. The RoleTailored Client has been renamed the Windows Client. Additionally, a built-in Web Client and SharePoint Client were added. The Web Client does not require any special add-ins and works on computers and mobile devices alike. The report-building and database access that had been previously available with the Classic Client is still available and used as development tool to modify the system by customers and by a reseller (consultant).

Microsoft Dynamics NAV 2013 Web Client (Order Processor Role)

Relative to Microsoft's other 3 ERP products, the Dynamics NAV's sector is for small distribution and manufacturing companies that want more than 'out of the box' functionality. Very few installations are actually made 'out of the box' as all sales of the product are through Microsoft-approved resellers who base their entire businesses on how many consulting hours they can apply to any given installation. The solution has a standard feature set, but it can also be thought of as an 'ERP System construction set' if, at the end of the installation, you want to end up with every erector piece that was in the box still attached to your system. A better analogy would be to think of the NAV program as a 4'x8' sheet of pegboard, with 4,600 evenly spaced holes. It is used to cover various sized company boxes, ranging in size from shoebox, through pizza box, knockdown furniture box, up to double-doored refrigerator box. No matter the size box the underlying company is, the 4'x8' sheet of pegboard remains the same. It then becomes the reseller's job to link up whichever pegholes are needed to the specific company under the interface. They may not need all of the holes; some company boxes may need less than 1,000 links, but all of the holes remain visible to the end-user after the installation is complete. The Pascal-like development language is easily accessible to appropriate developers and is designed for rapidly customizing the software.

In first quarter of 2014 NAV reached 102,000 current customers.[8] An increase of 8,000 in under a year.

As a native international ERP, Microsoft Dynamics NAV is available with 43 official localizations[9] and several unofficial ones (provided by local partners).

The NAV solution is also compliant with IAS/IFRS.[10]

Microsoft Dynamics NAV delivers integrated functionality to provide support for:

  • Financial management
  • Supply chain management
  • Manufacturing
  • Distribution
  • Customer relationship management
  • Sales and marketing
  • Service management
  • Human resource management
  • Project & Resource management
  • Warehouse management

Architecture[edit]

The Microsoft Dynamics NAV software is composed of three major components:

  • The Database Server, a database that stores the Microsoft Dynamics NAV data (as of NAV 2013 only Microsoft SQL Server)
  • The Application Server (starting from NAV 2009 RTC), a service that controls all aspects of Microsoft Dynamics NAV's operation
  • The Client(s), the actual user interface into Microsoft Dynamics NAV. NAV 2013 includes three clients:
Windows client
SharePoint client
Web client
  • NAV 2015 further introduced a Tablet Client
  • NAV 2016 introduced a Phone Client, Tablet Client

Licensing model[edit]

Microsoft Dynamics NAV uses a concurrent user licensing model only.

In 2006, Microsoft introduced the 'Business Ready License' (BRL) model. The customer purchases user sessions, which have access to certain parts of the system included. There are two types of user—Business Essentials (BE) and Advanced Management (AM); AM provides access to more functionality than BE. Under the previous licensing model, 'Module Based License' (MBL), users came with no functionality—this all had to be bought separately. Microsoft offers a path for customers to transition from MBL to BRL licensing.

With the arrival of NAV 2013, Microsoft introduced a new licensing model called 'Perpetual Licensing', which considerably simplifies the pricing structure. With Perpetual Licensing, customers license the Solution functionality and access to that functionality is secured by licensing users. User licenses are of two types: Full User or a very discounted Limited User. The full user has access to the entire system, where as the Limited user only has read access to the system, except write access key tables such as Time sheets, Warehouse Pick and Commenting plus any three extra tables of choice.[11] The Limited user is 'concurrent' and with 2013 is trust based, as of version 2013r2 the limited user licensing is checked.

NAV Add-ons[edit]

In addition to the base product, Add-ons are sold by ISV's. Because the base program has to focus on generic versions of business cases, software products supplementing/modifying NAV functionality are required, sold and distributed as NAV Add-ons, to improve functionality of NAV system or make it applicable in some business spheres.

There are vertical and horizontal add-on solutions. Horizontal add-on solutions supplement one of the NAV functions or add new function (e.g. financial management, human resources management etc.). Vertical (or industry-specific oriented) add-ons expand NAV functionality to support some industry (e.g. health care, brewery, financial services etc.) The majority of add-on solutions are multilingual with most supporting English.

Utilities are another form of add-on for Microsoft Dynamics NAV that make the resellers' jobs simpler. Utilities are small software modules used by Microsoft Dynamics NAV programmers and database administrators, to make their jobs more convenient and effective. Also it makes program development and implementation processes faster and the cost lower for the resellers.

NAV CfMD (Certified for Microsoft Dynamics)[edit]

With NAV 2013, producing and maintaining Add-on solutions for NAV has become more expensive, since acquiring an exclusive NAV object number range is expensive, unless the solution gets certified. Solutions will have to be certified with every non-minor release of NAV, which happens once a year from NAV 2013 and onwards.

NAV CfMD is an exhaustive quality check of the entire software solution. This helps ensure the quality of the NAV Add-on solutions.

References[edit]

  1. ^Jawad, Hamza (August 9, 2019). 'Dynamics NAV is now Dynamics 365 Business Central, revamped as modular solution'. Neowin. Retrieved September 28, 2020.
  2. ^'Dynamics NAV is now Dynamics 365 Business Central'. Microsoft. Retrieved September 28, 2020.
  3. ^'The history of Dynamics NAV/Navision'. DynamicsUser.net. Archived from the original on May 13, 2014. Retrieved March 13, 2013.
  4. ^'Damgaard and Navision in large merger (Danish)'. Computerworld.dk. Retrieved March 13, 2013.
  5. ^'It's Official: Microsoft buys Navision'. Archived from the original on February 2, 2009.
  6. ^'Microsoft Introduces Microsoft Dynamics Brand'. Microsoft. Retrieved March 13, 2013.
  7. ^'What's New in Developing for Microsoft Dynamics NAV 2009'. MSDN. Retrieved February 16, 2011.
  8. ^'How many companies use MS Dynamics'. Retrieved March 2, 2014.
  9. ^'Product availability'. Microsoft. Retrieved March 13, 2013.
  10. ^'Microsoft Dynamics NAV regulatory compliance'. Microsoft. Retrieved April 29, 2013.
  11. ^'License Types'. MSDN. Retrieved March 3, 2014.

External links[edit]

Retrieved from 'https://en.wikipedia.org/w/index.php?title=Microsoft_Dynamics_NAV&oldid=1007157338'