Skip to main content

MSDYN365BC - Export-NAVApplicationObject '"' is not an option. The Existing options are:No,Yes.

Hi Readers,

Today while working on a project we faced an issue. The issue occurs while using the Powershell cmdlet Export-NAVApplicationObject.

The version that can be replicated in -
  • Microsoft Dynamics 365 Business Central April'19 on-premises.
  • Cumulative Update 10.
  • Application Build 14.11.41204
  • Platform Build 14.11.41143

In this article, we will discuss why this error and How to Solve this issue?

When is the error? 

When you try to use Powershell cmdlet Export-NAVApplicationObject  either using Dynamics NAV Development Shell or using Powershell after loading the Dynamics NAV Module.

What is the error?

'"' is not an option.
The existing options are:
No, Yes

What we tried?
  1. Removed Filter in the cmdlet to see maybe we are applying filter incorrectly. 
  2. Check License Saved in Database.
  3. Check Permission in the Folder where the file is to be written/saved.

Why is the error? 

So after tried all standard processes and solutions when nothing got fixed, this problem was brought to my notice.

Spun up a Microsoft Dynamics 365 Business Central April'19 on-premises CU 09 docker environment and test Export-NAVApplicationObject and everything worked file.

Now thought to compare NAV Modules from CU09 and CU10 to see what was changed. 

What was Changed? - 

I don't know How PowerShell is written but when I did compare I see Microsoft added a New parameter in Function RunNavIdeCommand. 

This Parameter is SuppressElevationCheck as shown below.

So I think Microsoft will fix the issue with this new parameter in the upcoming cumulative Update.

Temporary Fix?

As a temporary fix, you can replace Microsoft.Dynamics.Nav.Ide file from Business Central 14 Cumulative Update 09 to Installed Folder of Cumulative Update 10.

After the Replacing file, all PowerShell cmdlets will run successfully.

Let me know your views as a comment on this article.

Stay connected for more.

Saurav Dhyani


  1. Hi,

    Freddy also blogged about this issue here:
    He also shows how to patch the powershell to fix the issue.

    Best Regards,
    Gert Lynge


Post a Comment

Popular posts from this blog

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 2014 Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.

NAV 2013 Upgrade Part III - Data Upgrading.

Hi all, As per agenda we need to discuss the data upgrade in NAV 2013. The process is similar to what used to be till NAV 2009 R2 but with some changes. Let's start the process. Remember -  1) You can only upgrade a database to NAV 2013 from NAV 2009 SP1 / R2 SQL Only. 2) The Synchronization of users with SQL Server is no more required.