Monthly Archives: February 2021

BC14 – Generate Symbols and Build Object Search Index

The ‘Build Object Search Index’ feature in the BC14 Development Environment makes objects searchable in the webclient according to the Microsoft documentation: https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-pages-report-for-search

However in another Microsoft article:

Running C/SIDE and AL Side-by-Side https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-running-cside-and-al-side-by-side

you should run a command in order to generate symbols. But actually the Build Object Search Index performs the same action. In my opinion it’s just easier sometimes to generate symbols by using the ‘Build Object Search Index’ instead of opening a Console and running the command as mentioned AND with the disadvantage of no progress in the Console which you do have in the Development Environment:

Export-NAVApplicationObject : $NavIde was not correctly set. Please assign the path to finsql.exe to $NavIde ($NavIde = path).

One step of convertering C/AL to AL is to import the fob in BC14 and then export it to text with the new syntax. This exporting can be achieved by using the Export-NAVApplicatieObject cmdlet. However I got an error I recognized but I didn’t know how to resolve it anymore. So I started Googling but couldn’t find the right answers quickly. That’s why I think this post could help also someone else or at least myself when I encounter this ‘issue’ ever again.

When executing the cmdlet you will get this error:

The term ‘Export-NAVApplicationObject’ is not recognized as the name of a cmdlet, function, script file, or operable program.

In order to fix this we need to load the module which contains this cmdlet. I loaded the module using the Import-Module cmdlet:

Import-Module 'C:\Program Files (x86)\Microsoft Dynamics 365 Business Central\140\RoleTailored Client\NavModelTools.ps1'

this results in an error however:

Export-NAVApplicationObject : $NavIde was not correctly set. Please assign the path to finsql.exe to $NavIde ($NavIde = path).
At line:1 char:1Export-NAVApplicationObject

CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException

FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Export-NAVApplicationObject

The cause is the loading of the incorrect module. Perform the following steps to resolve the issue:

  • Close your PS (Powershell) environment
  • Run the following Cmdlet:
  • Import-Module 'C:\Program Files (x86)\Microsoft Dynamics NAV\100\RoleTailored Client\Microsoft.Dynamics.Nav.Model.Tools.psd1'

Now the Export-NAVApplicationObject works without problems!

Cumulative update CU 51 for Microsoft Dynamics NAV 2017 has been released

For a complete list of updates please take a look at Microsoft Support: https://support.microsoft.com/en-us/topic/released-cumulative-updates-for-microsoft-dynamics-nav-2017-99f042ca-81ed-9fd5-2645-75fa9590dfd1

The CU only contains only minimal improvements. Depending on the localization other objects can be fixed. On platform level the fixes are really minimal:

Bron: https://support.microsoft.com/en-us/topic/cumulative-update-51-for-microsoft-dynamics-nav-2017-build-30443-887d362a-9dc7-4cac-a8e9-81ff9a57b9bc