Unblock the zip file or unblock all files. Some operating systems (for example Windows 10) may require that you unblock files that are downloaded from the Internet. Unblock the zip file and then extract the files again. Here is fastest way to unblock all NavSherpa files:
Open "File Explorer" in Windows.
Select the zip file containing the NavSherpa files.
Open "Properties" on the zip file.
Check "Unblock" or use the button "Unblock" it depends on Windows version.
Confirm the change using the "OK" button.
Copy the "Add-ins" folder from the NavSherpa installation folder to the "Service" folder where the NAV server instance is running (NAV service tier).
All NavSherpa objects should be recompilable without error. NAV should download all necessary libraries to the client machine during recompilation. But if an error about missing libraries is shown, then NAV didn't download DLLs and this must be done manually. Copy the files "NavSherpa.dll", "Navisys.DragAndDrop.dll" and "Navisys.NAVWebBrowser.dll" from "Add-ins" in the installation folder to the "C:\Program Files (x86)\Microsoft Dynamics NAV\100\RoleTailored Client\Add-ins" folder where NAV is installed. This has to be done on the machine where the objects will be compiled.
Check that the application server using the standard job queue is set and that the job queue is running. The application server is usually installed on the same machine as the NAV service tier.
Import the objects NSPW1xx_yy_zz.fob into database from the folder "Objects" in the NavSherpa installation folder. (where xx = Main NAV version NA2017=10, yy= NAV release NAV2013R2 = 10, zz=NavSherpa version)
Run the "Microsoft Dynamics NAV Development Environment".
Open "Object designer" via Tools --> Object designer (or by using the shortcut Shift+F12) if it isn't opened.
Open the import window via File --> Import.. .
Choose the file NSPW1xx_yy_zz.fob from the folder "Objects" in NavSherpa installation folder.
If NavSherpa is installed for the first time, confirm the dialog that arises with informing that no conflict was found. The "No" button should be chosen, and after that the Import Worksheet is opened. All the objects should have the action "Create". Use the "OK" button to import the objects.
If NavSherpa has been previously installed (NavSherpa is upgrading to newer version), the Import Worksheet is opened. Use the button "Replace All" and the actions will be changed to "Replace" for all objects. Use the "OK" buttonto import all object.
Merge the objects contained in NSPW1xx_yy_zz.txt from "Objects" in NavSherpa installation folder, into the database.(xx = Main NAV version NA2017=10, yy= NAV release NAV2013R2 = 10, zz=NavSherpa version). For this you can use a text compare program.
You can use NSPW1xx_yy_zz_DELTA.zip for merging if you are familiar with Navision PowerShell functions:
Run "Windows PowerShell" as Administrator.
Run the script "Update_ModuleObjects.ps1" from "Objects" in NavSherpa installation folder (Example: C:\NavSherpa\Objects\Update_ModuleObjects.ps1) with the following parameters
APP_Folder - Folder containing the NAV Role Tailored Client.
DatabaseServer - Database server name running the destination database.
DatabaseName - Destination database name. If this is empty, the script doesn't export objects automatically from the destination database. For this action you require permission for the database on SQL server.
Check "Created Date" in the Navision license file.
Run the "Microsoft Dynamics NAV Development Environment".
Open "License Information" via Tools --> License Information.
Look for "Created Date".
If "MS license release date" is newer than "Created Date" in Navision, a new Navision license file will need to be downloaded. Otherwise, skip steps d, e and f.
Go to the Microsoft portal and download a new license file. Customer's license files have to be download too.
Import the new license file to NAV.
Run the "Microsoft Dynamics NAV Development Environment".
Open "License Information" via Tools --> License Information.
Click on the "Upload..." button.
Choose the new license file.
Click on the "Open" button.
Restart the NAV server instance.
Set up automated procedures (NAS).
Start "Dynamics NAV Administration".
Choose the NAV server instance connected to database containing NavSherpa.
Activate edit mode in the NAV server instance configuration via the "Edit" button.
Set the "Startup Codeunit" to "4065010".
Save the change.
Restart the NAV server instance.
Set up an administrator notification:
Run the "Role Tailored Client".
Open the page /Departments/Administration/Application Setup/NavSherpa/NavSherpa Users.
Set up a new user for NST (user to be used for the NST service) via "New Login".
Set up a new user as administrator via "New Login" and enable "Notify Errors From NAS". This will generate notifications for the "My Notification" section in the administrator's home page.
NavSherpa help is prepared in HTML and can be run as standard help for Microsoft Dynamics NAV or by NavHelpServerBypass:
Standard help
Copy the folder "NavSherpa_HelpServer" to a folder with webs on IIS (Example: "C:\inetpub\wwwroot").
Register the new website on IIS.
Run the new website.
Set the new web site as URL for help on NAV.
NavHelpServerBypass can be configured and provides redirections for help. If the F1 key is used on a standard field, the "Application" redirects help to the standard help from Microsoft. If the F1 key is used on a NavSherpa field, the "Application" redirects help to NavSherpa help. It is possible to use both helps at once.
Copy the folder "NavSherpa_HelpServer" to the folder with standard help (Example: "C:\inetpub\wwwroot\DynamicsNAV100Help").
Copy the folder "NavHelpServerBypass" to the folder with standard help (Example: "C:\inetpub\wwwroot").
Register the new website "NavHelpServerBypass" on IIS.
Check that you have the module "AspNetCoreModule” on the web "NavHelpServerBypass" modules. If you don’t have the module in modules you have to install it. The module is available onhttps://go.microsoft.com/fwlink/?linkid=844461. Restarting IIS after installation is required.
Run the new website.
Set the new website as the URL for help in NAV.
Configure redirections in NavHelpServerBypass (appsettings.json).
NavSherpa uses ENU as the default language. Another language can be installed by using these steps:
Look for the folder with required language in the "Languages" folder which is in the NavSherpa installation folder. Folders have the same codes as languages in Microsoft Dynamics NAV. For example: the Czech language is in the folder "CSY". If the folder with the desired language is not in the "Languages" folder, it means that this language is not supported.
Run the "Microsoft Dynamics NAV Development Environment".
Open "Object designer" via Tools --> Object designer (or by shortcut Shift+F12), if it isn't opened.
Import the language into the NavSherpa objects via Tools --> Language Module --> Import... and open the file *.flm from the folder. Confirm the request about importing.
The folder containing the language has a subfolder (Example: cs-CZ) which has to be copied to the "Service" folder in on NAV service tier machine.
Import user permission sets from the file "Permissions.txt" in the "Documentation" folder.
NSP-USER – is used for users who can upload documents to SharePoint, send records to lists and run workflows.
NSP-ADMIN – Has to be used together with the NSP-USER permission set. These users can setup the NavSherpa module. These users can setup the SharePoint lists, mappings etc.
NSP-SYSTEM – is used for the application server that uploads documents to SharePoint.
Continue NavSherpa configuration according to the instructions contained in "..\Documentation\ NavSherpa RapidStart Deployment.docx".
