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.

Regards,
Saurav Dhyani
www.sauravdhyani.com
Labels:
Location: House No. 1, Shivlok Colony, 2, near Himalayan Academy Post Office, Shivlok Colony, Sewla Kalan, Majra, Dehradun, Uttarakhand 248171, India

Comments

  1. Gert LyngeApril 16, 2020 at 6:37 PM

    Hi,

    Freddy also blogged about this issue here: https://freddysblog.com/2020/02/22/small-issue-in-bc-2019-wave-1-cu9/
    He also shows how to patch the powershell to fix the issue.

    Best Regards,
    Gert Lynge
    www.dabbler.dk

    ReplyDelete

Post a Comment

Popular posts from this blog

Microsoft Dynamics NAV 2016 - How to Configure Phone Client.

Hi All, In this article we will discuss how we can connect Microsoft Dynamics NAV 2016 with New Client Launched i.e. Phone Client. This Article Contain Steps for a Android Phone as I have Only Android Phone. I am doing it having all tiers on my windows 8 machine, steps remain same for multiple servers but issues might be different. What we Need (Other what we discuss in this article) -  The Service Tier should be on Public IP . Some of the Data-card does not Provide you Public IP. check it for sure.
28 comments
Read Complete Article »

How to Set Up NavUserPassword Authentication in Business Central.

Hi Readers, In this article we will discuss steps to Setup NAVUserPassword in Business Central on-prem. NavUserPassword is an authentication method that's handled by Business Central Server, but isn't based on Windows users or Active Directory. Each user is set up with a username and password that's configured inside Business Central only. The user is prompted for username/password credentials when they start the client. #msdyn365bc, #credentialtype
1 comment
Read Complete Article »

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.
21 comments
Read Complete Article »