NAV 2017 Link Sammlung

Neue Features in Dynamics NAV 2017

  • Release Okotober 2016
  • Support Oktober 2026
  • Neue Features:
    • Verbesserung des OCR Services (E-Services)
    • Untersützung von Paypal für Online Zahlungen

Lizenzpackete

  • Starter-Pack (3 User Standard Umfang)
  • Professional-Pack (3 User erweiterte Features, Produktion, Fertig, Lagerhaltung)

 

Linksammlung:

Anleitung zum einspielen von Content Updates

https://support.microsoft.com/en-ca/help/3204818/how-to-install-a-microsoft-dynamics-nav-2017-cumulative-update

 

OCR in NAV 2017 Implementieren

https://community.dynamics.com/crm/b/microsoftdynamicscrmsolutions/archive/2016/11/14/implementing-ocr-services-in-nav-2017

 

Installationsanleitungen

Wie Konfiguriere ich den Web-Server für NAV 2016

https://msdn.microsoft.com/de-de/library/dd355055(v=nav.90).aspx

 

 

 

NAV2018 Instalaltionsanleitung

Liebe NAV Comunity,

wenn man sich an dieser Anleitung orientiert ist die Installation von Dynamics NAV 2018 einfach.

https://docs.microsoft.com/en-us/dynamics-nav/walkthrough–installing-the-three-tiers-on-three-computers

Allein wenn der SQL Server auf einen anderen Server liegt, muss man entsprechende Windows Service Domain Accounts anlegen unter denen die Dienste laufen sollen.
Entsprechende Rechte innerhalb des Microsoft SQL Servers müssen vergeben werden.

Hierzu hat Mictrosoft ein Papier Dynamics NAV 2016 an den wir uns orientieren.

Link folgt:
https://msdn.microsoft.com/en-us/library/hh166150(v=nav.90).aspx

Provisioning the Microsoft Dynamics NAV Server Account

Gültig: Microsoft Dynamics NAV 2016 Other Versions
Hinweis: Was unter NAV2016 funktionierte funktioniert auch noch wunderbar unter NAV2018

The Microsoft Dynamics NAV Server account is used by Microsoft Dynamics NAV clients to log on to the Microsoft Dynamics NAV Server instance. The Microsoft Dynamics NAV Server then uses the service account to log on to the Microsoft Dynamics NAV database. When you install Microsoft Dynamics NAV Server, you identify an Active Directory account to provide credentials for the server. By default, Setup runs Microsoft Dynamics NAV Server under the Network Service account, a predefined local account used by the service control manager. This account has minimum privileges on the local computer and acts as the computer on the network.

We recommend that you create a domain user account for running Microsoft Dynamics NAV Server. The Network Service account is considered less secure because it is a shared account that can be used by other unrelated network services. Any users who have rights to this account have rights to all services that are running on this account. If you create a domain user account to run Microsoft Dynamics NAV Server, you can use the same account to run SQL Server, whether or not SQL Server is on the same computer.

Because Microsoft Dynamics NAV Setup and the New-NavDatabase cmdlet configure the required permissions for the Microsoft Dynamics NAV Server account, you will typically use the procedures in this topic when you change the Microsoft Dynamics NAV Server account for an existing installation.
To provision a Microsoft Dynamics NAV Server account, complete the following procedures as described in

If you are running the Microsoft Dynamics NAV Server under a domain user account, you must:
Enable the account to log in as a service

Enable the account to register an SPN on itself

Give the account necessary database privileges in SQL Server

Enabling the account to log in as a service
Depending on various factors, the account may or may not already have this ability. For example, if you have already installed SQL Server and configured it to run under the same account, SQL Server will have modified the account to log in as a service.
Instructions for enabling an account to log in as a service are available on TechNet. See Add the Log on as a service Right to an Account. The instructions are for Windows Server 2008. For Windows 7, use this version of the procedure: Add the Log on as a service right to an account.
When this permission is lacking, Microsoft Dynamics NAV Server server instances may not be able to start.
Enabling the account to register an SPN on itself
To enable secure mutual authentication between clients and Microsoft Dynamics NAV Server, you must configure the Microsoft Dynamics NAV Server account to self-register Service Principal Names (SPNs). Mutual authentication is recommended in a production environment but may not be necessary in a testing or staging environment. The following procedure assumes a computer running Windows Server 2008 or Windows Server 2008 R2. On Windows 7 or Windows Vista you would need to install the Remote Server Administration Tools first.
To enable the Microsoft Dynamics NAV Server account to register an SPN on itself
Start the Active Directory Users and Computers snap-in in Microsoft Management Console (MMC):
Choose Run on the Start menu, type mmc on the command line, and the choose OK.

When the console opens, select Add/Remove Snap-In from the File menu, select Active Directory Users and Computers, and choose Add.

If you do not see Active Directory Users and Computers in the list of available snap-ins, you may need to use Server Manager to install the Active Directory Domain Services role on your server computer.

In MMC, select Active Directory Users and Computers in the tree view and choose Advanced Features from the View menu.
Expand the domain node in the tree view and choose Users.
Right-click the service account, select Properties, and then choose to display the Security tab.
Choose SELF in the Group or user names list.
Under Permissions for SELF, in the lower part of the panel, scroll down to Write public information and select the Allow column.
Choose OK to exit the Properties panel, and close Active Directory Users and Computers.
Giving the account necessary database privileges in SQL Server
The Microsoft Dynamics NAV Server account must be a member of the db_owner database role on the Microsoft Dynamics NAV database. When you install the Microsoft Dynamics NAV database by using Microsoft Dynamics NAV Setup or the New-NAVDatabase PowerShell cmdlet, you can specify the Microsoft Dynamics NAV Server account. In these cases, the server account that you specify should already have the necessary privileges in SQL Server. If you change the Microsoft Dynamics NAV Server account for an existing installation, then you should verify the account has the required privileges in SQL Server.
To verify database privileges after you create your Microsoft Dynamics NAV database, use SQL Server Management Studio and, if necessary, modify database privileges. If you have installed SQL Server with the guidelines in Installation Considerations for Microsoft SQL Server, then SQL Server Management Studio is already installed on your computer. Otherwise, update your SQL Server installation to include the Management Tools – Complete option for SQL Server.
Hh166150.note(en-us,NAV.90).gifNote
If you installed the Demo option in Microsoft Dynamics NAV Setup, then the Network Service account already has the necessary database privileges.
To assign necessary database privileges for the Microsoft Dynamics NAV Server account
Start SQL Server Management Studio and connect to the instance where the Microsoft Dynamics NAV database is installed.
Create a login for the Microsoft Dynamics NAV Server account.
Navigate the tree view: Security, Logins

Right-click Logins and choose New Login.

Choose Search, and use the Select User or Group dialog box to identify the Microsoft Dynamics NAV Server account.

Choose OK to exit the New Login dialog box.

Add the login as a user on the master database.
Navigate the tree view: Databases, System Databases, master, Security, Users.

Right-click Users and choose New User.

Choose the ellipse button at the far right of the second line in the Database User – New dialog box.

In the Select Login dialog box, enter or browse for the login you created for the Microsoft Dynamics NAV Server account.

Enter a name in the User name field (the first line in the Database User – New dialog box).

Choose OK to exit the Database User – New dialog box.

Grant the Microsoft Dynamics NAV Server login permissions on the master database. In the tree view, right-click master and choose Properties. Then do the following in the Database Properties – master dialog box.
Under Select a Page, choose Permissions.

Under Name, choose the login you created for the Microsoft Dynamics NAV Server account name.

Under Permissions for , on the Explicit tab, scroll down to down to the Select line, and select the check box in the Grant column.

Choose OK to exit the Database Properties – master dialog box.

Navigate the tree view: Databases, System Databases, master, Tables, System Tables.

Right-click the dbo.$ndo$srvproperty table and choose Properties.

Under Select a Page, choose Permissions.

Choose Search, and use the Select User or Group dialog box to identify the login for the Microsoft Dynamics NAV Server account.

Under Permissions for , on the Explicit tab, scroll down to down to the Select line, and select the check box in the Grant column.

Choose OK to exit the Table Properties – dbo.$ndo$srvproperty dialog box.

Grant the login the necessary database roles on the Microsoft Dynamics NAV database.
Navigate the tree view: Databases, , Security, Users.

Right-click Users and choose New User.

In the Database User – New dialog box, choose the ellipse button at the far right of the second line.

Select the login you created for the Microsoft Dynamics NAV Server account name and choose OK.

Under Database role membership, select the db_owner check boxe.

Choose OK to exit the Database User – New dialog box.

Right-click your Microsoft Dynamics NAV database and choose Properties.

Under Select a Page, choose Permissions.

Choose Search, and use the Select User or Group dialog box to identify login you created for the Microsoft Dynamics NAV Server account.

Under Permissions for , on the Explicit tab, scroll down to down to the View database state line, and select the check box in the Grant column.

Choose OK to exit the Database Properties dialog box for your Microsoft Dynamics NAV database.

It is also possible to script these steps in SQL Server Management Studio:
USE [master]
GO
CREATE LOGIN [domain\accountname] FROM WINDOWS
CREATE USER [domain\accountname] FOR LOGIN [domain\accountname]
GRANT SELECT ON [master].[dbo].[$ndo$srvproperty] TO [domain\accountname]
GO
USE [Microsoft Dynamics NAV Database]
GO
CREATE USER [domain\accountname] FOR LOGIN [domain\accountname]
ALTER ROLE [db_owner] ADD MEMBER [domain\accountname]
GRANT VIEW DATABASE STATE TO [domain\accountname]

Provisioning the Network Service Account
The only circumstance where it is necessary to take any action with regard to the Network Service account is when change the Microsoft Dynamics NAV Server account on an existing installation from a domain account to the Network Service. In this situation you must verify that the account has the necessary database privileges in SQL Server, as per Giving the account necessary database privileges in SQL Server, above.

Gruß,
Kim

NAV 2018 – Was gibt es neues?

https://community.dynamics.com/nav/b/dynamics365nav/archive/2017/09/17/what-is-new-in-microsoft-dynamics-nav

Anbei eine Übersicht was es neues in NAV2018 gibt.

Hinweis:
NAV2018 – gibt es eine neue Entwicklungsumgebung für Extensions. Die Zukunft von NAV ist Updat Fähig, Version von Version, wenn sie komplett nach der Microsoft Philosophie der Zukunft mit Extensions Arbeiten.
Zu lernen wie man Extensions Programmiert wird sicher die Herausforderung sein. Alelrdings gibt es auch dafür bereits eine neue Entwicklungsumgebung die von Microsoft zur Verfügung gestellt wird.

Microsoft Dynamics NAV 2018 Entwicklung – Neues Toolkit

LINK: http://msdynamicsnav.guru/wp/tag/nav-2018/

Wie installiere ich NAV 2018?
http://msdynamicsnav.guru/wp/totovic/how-to-install-nav-2018/0089047/

Dienste (Serivce) Einstellungen für NAV 2018
http://msdynamicsnav.guru/wp/roberto-stefanetti/nav-2018-service-options-recap/0088701/

Wie connecte ich Visual Studio mit der App?
http://msdynamicsnav.guru/wp/kauffmann/how-to-connect-visual-studio-code-with-nav-2018/0092221/

Visual Code – Beispiel Code – YouTube Viedeo von Lern4Nav

Dynamics NAV Design und Programmierung: Anlegen von zusätzlichen Felder in Tabellen

Beispielzitate

Announcing the Preview of Modern Development Tools for Dynamics NAV

Wie erstelle ich eine neue Extension V2?
https://docs.microsoft.com/de-de/dynamics-nav/developer/devenv-get-started

Schreibe Deinen ersten Beispiel-Code
https://docs.microsoft.com/de-de/dynamics-nav/developer/devenv-extension-example

Wie installiere ich eine Extensions V2?
https://docs.microsoft.com/de-de/dynamics-nav/developer/devenv-extension-install-code

Wie veröffentliche ich eine Extensions V2?
https://docs.microsoft.com/de-de/dynamics-nav/developer/devenv-how-publish-and-install-an-extension-v2

Links von MBesoeo

https://mibuso.com/downloads/nav-techdays-2017-rock-n-roll-with-vscode

Auszug vom NAVGURU
Quelle:
http://msdynamicsnav.guru/wp/kauffmann/how-to-connect-visual-studio-code-with-nav-2018/0092221/
https://mibuso.com/downloads/nav-techdays-2017-easier-and-devops-friendly-nav-environments-using-docker-windows-containers

Siehe Screenshoots

Last couple of days, I got a number of questions from people that all came down to the same issue: how to set the correct settings in the launch.json so Visual Studio Code can connect to NAV 2018. In most cases I saw the same mistake being made. A logical mistake, but also one that leaves you probably wondering why it works that way.
Let’s assume you have enabled the development port in your NAV 2018. Look here to read how that is done.
When you create a new workspace in VS Code with the AL:Go! command, you get by default a launch.json that looks like this:

Basically the only thing you need to change is the servername. In my case that would be navserver. Some people also change the default developer port 7049 to another port number, let’s say 7149. A common mistake is to put that port number into the server url.

Let’s see what happens when we try to download the symbol files.

It uses port number 7049! How is that possible?
The port number in the server url is just ignored. Instead you should specify the port number with a separate setting. If that setting is missing, then the default port number 7049 is used. Let’s specify the port number and see what happens.

Let’s download the symbol files again, and watch the url.

Conclusion: do not specify a port number in the server url. Instead, use the port setting to specify the developer port number.
Another common mistake is that the server url and the web client url are assumed to be the same. That is not the case. The two settings we talked about above, the server url and the developer port number, are the only settings you need in the launch.json.
When VS Code publishes the extension to the NAV server, the NAV server returns the web client url as a response. This url is then opened in the browser. No setting needed in the launch.json at all.
The NAV server reads that setting from the Web Client Base Url server setting.
Let’s prove that with an example. In the next screenshot, I set the key to a different value. Sorry, it’s PowerShell, I only have NAV 2018 installed with docker images.

How to check the output? Well, I can of course show a browser screen with that url, but would that prove my point? So I figured that a Fiddler trace would probably more convincing. Here is the Fiddler trace when VS Code publishes the extensions to the server.

Look at the response, it contains the setting that I did with the PowerShell command.
And here is what happens when the Web Client Base Url is not set:

I hope this demystifies how VS Code and the NAV server work together!

NAV wird Dynamics 365 (OnPremise) – Projekt Green

NAV 2018 Release steht kurz bevor (geplant 02.12.2018).

Danach wird es kein neues NAV mehr geben. NAVISION oder NAV ist damit auf keinen Fall beerdigt, ganz im Gegenteil. NAV hat sich durchgesetzt und im Untergrund von Dynamics 365 liegt in Zukunft NAV (ehemals NAVISION). Das heisst der Release Herbst 2018 für NAV 2018 R2 – wird kommen und dann heisst das selbe Produkt was wir kennen Dynamics 365 (OnPremise). Der Sourcecode zwischen der Cloudvariante und der OnPremise Lösung wird identisch sein.

Wir finden das sind eindeutig gute Neuigkeiten und Microsoft stellt NAV damit auf die richtigen Beine für die Zukunft.

Auch die Erweiterungen am SQL Server für die Datenhaltung, Mandantenfähigkeit usw. sind genau die Punkte gewesen die wir damals als „altmodisch“ bemängelt haben. Microsoft hat sein Produkt kontinuierlich verbessert.

Alle Neuerungen wurden durch Microsoft konsequent mit Visual Studio entwickelt.

Microsoft hat das gesamte Datenbankmodel entsprechend angepasst, um die Basis Plattform für die Zukunft zu gestalten.

Was mal als Projekt Green gestartet hat nähert sich (Herbst 2018) mit dem Release von NAV 2018 R2 (es wird dann nur noch Dynamics 365) heissen den Ende.

Ein ERP System, eine Datenbank für tausend Mandanten ist damit möglich. Der SQL Server bietet dennoch uneingeschränkte Performance.

Das Produkt ist für die Cloud bereit und es ist gleichzeitig jederzeit weiterhin als OnPremise Variante einsetzbar.

Das Video von LeBit Software & Consulting GmbH zeigt sehr aufschlussreich die Produktentwicklung und Roadmap von Microsoft.

Wir wünschen Euch viel Spaß und sagen – mit NAV seid ihr in Sachen Zukunft genau richtig unterwegs.

Partnerlösungen, die Klassische Programmierung .FOB Objekte werden, weiter unterstützt, allerdings sind alle neuen Module und Features von vornherein mit den Neuen Programiermechaniken erstellt wurden.

Wir empfehlen von vorn herein bei der NAV Einführung darauf zu achten, die neue Denkweise zu unterstützen. Sein Produkt Upgradfähig halten, damit auch die monatlichen CU (Updates) eingespielt werden können. So wird in Zukunft ein teure Versionsmigration vermieden.

Viel Spaß beim Video

Euer Kim

NAV2017 – CU Update installiert, welche Buildnummer habe ich jetzt?

Anbei ein Link zur Übersicht.

https://support.microsoft.com/en-us/help/3210255/released-cumulative-updates-for-microsoft-dynamics-nav-2017

Für NAV 2017 gibt es jetzt 12 CU’s

Knowledge
Base ID

Title

Release date

Build no.

Local versions included

Version 10.0 steht für NAV 2017. Die Nummer die dann folgt steht für die Buildnumber. In Meinem Fall die 18976, diese steht wiederrum für das CU 12 das im November von Microsoft veröffentlicht wurde.

Buildnr. 18976 – KB 4052195 – Cumulative Update 12 for Microsoft Dynamics NAV 2017 November, 2017 – 18976 – AT, AU, BE, CH, CZ, DE, DK, ES, FI, FR, IS, IT, IN, NA, NL, NO, NZ, RU, SE, UK
Buildnr. 18609 – KB 4045671 – Cumulative Update 11 for Microsoft Dynamics NAV 2017 October, 2017 – 18609 – AT, AU, BE, CH, CZ, DE, DK, ES, FI, FR, IS, IT, IN, NA, NL, NO, NZ, RU, SE, UK
Buildnr. 18197 – KB 4040570 – Cumulative Update 10 for Microsoft Dynamics NAV 2017 September, 2017 – 18197 – AT, AU, BE, CH, CZ, DE, DK, ES, FI, FR, IS, IT, IN, NA, NL, NO, NZ, RU, SE, UK
Buildnr. 17972 – KB 4037309 – Cumulative Update 09 for Microsoft Dynamics NAV 2017 August, 2017 – 17972 – AT, AU, BE, CH, CZ, DE, DK, ES, FI, FR, IS, IT, IN, NA, NL, NO, NZ, RU, SE, UK
Buildnr. 17501 – KB 4034492 – Cumulative Update 08 for Microsoft Dynamics NAV 2017 July, 2017 – 17501 – AT, AU, BE, CH, CZ, DE, DK, ES, FI, FR, IS, IT, IN, NA, NL, NO, NZ, RU, SE, UK
Buildnr. 16996 – KB 4024642 – Cumulative Update 07 for Microsoft Dynamics NAV 2017 June, 2017 – 16996 – AT, AU, BE, CH, CZ, DE, DK, ES, FI, FR, IS, IT, IN, NA, NL, NO, NZ, RU, SE, UK
Buildnr. 16585 – KB 4021396 – Cumulative Update 06 for Microsoft Dynamics NAV 2017 May, 2017 – 16585 – AT, AU, BE, CH, CZ, DE, DK, ES, FI, FR, IS, IT, IN, NA, NL, NO, NZ, RU, SE, UK
Buildnr. 16177 – KB 4018437 – Cumulative Update 05 for Microsoft Dynamics NAV 2017 April, 2017 – 16177 – AT, AU, BE, CH, CZ, DE, DK, ES, FI, FR, IS, IT, IN, NA, NL, NO, NZ, RU, SE, UK
Buildnr. 15601 – KB 4014101 – Cumulative Update 04 for Microsoft Dynamics NAV 2017 March, 2017 – 15601 – AT, AU, BE, CH, CZ, DE, DK, ES, FI, FR, IS, IT, IN, NA, NL, NO, NZ, RU, SE, UK
Buildnr. 15140 – KB 4011763 – Cumulative Update 03 for Microsoft Dynamics NAV 2017 February, 2017 – 15140 – AT, AU, BE, CH, CZ, DE, DK, ES, FI, FR, IS, IT, IN, NA, NL, NO, NZ, RU, SE, UK
Buildnr. 15052 – KB 3216190 – Cumulative update 2 for Microsoft Dynamics NAV 2017 January, 2017 – 15052 – AT, AU, BE, CH, CZ, DE, DK, ES, FI, FR, IS, IT, IN, NA, NL, NO, NZ, RU, SE, UK
Buildnr. 14199 – KB 3209071 – Cumulative update 1 for Microsoft Dynamics NAV 2017 December, 2016 – 14199 – AT, AU, BE, CH, CZ, DE, DK, ES, FI, FR, IS, IT, IN, NA, NL, NO, NZ, RU, SE, UK

Die selben Informationen gibt es natürlich auch für die Version 2016, 2015 usw.

Microsoft hält sich daran monatliche Updates herauszubringen.

Es ist zu empfehlen diese Regelmäßig zu installieren um damit seine Version auf den aktuellen Stand zu halten und so später mühsame und teure Versionsupgrades zu umgehen.

Kim Sancken