Skip to main content

Application Merge Utilities - How to Use - SPLIT & JOIN NAVApplicationObjectFile

Hi All,

This is Fourth Post in this series. If you would like to read earlier post please visit Index of Application Merge Utilities.

As Promised In This Post we will see about Next Two Commands Available in the the Module "Microsoft.Dynamics.Nav.Model.Tools".

1. Split-NAVApplicationObjectFile

2. Join-NAVApplicationObjectFile

Let's Load the Module again and see the Available Functions.
Import-Module "${env:ProgramFiles(x86)}\Microsoft Dynamics NAV\71\RoleTailored Client\Microsoft.Dynamics.Nav.Model.Tools.psd1" -force
Get-Help "NAV"

Export all objects in the database as Text File or any set that you want. My Exported File Name is Obj.txt.

1. Get-NAVApplicationObjectProperty == 

This cmdlet will Splits a text file that contains two or more application objects into separate text files for each application object.The Output of the Cmdlet will be Multiple Text Files Where each file will contain a application Object.

This Cmdlet have Following Input Parameter 

  •  Source - Name of the Source File Containing Multiple Navision Objects.
  •  Destination - Folder Path Where Output Files Should be Stored.
  •  PreserveFormatting - Specifies if you want to keep the structure of the application objects as in the source text file. (Would Suggest to Keep YES always)
  •  PassThru - Specifies if the cmdlet must return a FileInfo object for each text file that is created. (You Can keep it NO beacause its just display information)
  •  Force - Forces the cmdlet to overwrite any existing files in the Destination folder.
Below is the command that have been generated in Powershell. 

Split-NAVApplicationObjectFile -Source C:\Users\sdhyani6995\Desktop\Blog\Temp\Obj.txt -Destination C:\Users\sdhyani6995\Desktop\Blog\Temp\Target -Force -PassThru -PreserveFormatting

Below is the Cmdlet window.

Here is the output of the Cmdlet -

2. Join-NAVApplicationObjectFile == 

This cmdlet will Use the combine the application objects in the specified folder into a single text file. The Output of the Cmdlet will the Single Merged File for all the objects in a Folder.

This Cmdlet have following Parameters -

  • Destination - Path and Name of the Target File.
  • Source - Path and Name of the Source Folder.

Below is the command that have been generated in Powershell.
Join-NAVApplicationObjectFile -Destination C:\Users\sdhyani6995\Desktop\Blog\Temp\MergedObject.txt -Source C:\Users\sdhyani6995\Desktop\Blog\Temp\Target

Below is the Cmdlet windows of the Cmdlet.

Below is the Merged File.

Hope some of you will be find the article useful.

Stay Tuned for More..

Saurav Dhyani


Popular posts from this blog

Welcome - Microsoft Dynamics 365!

Hi All, In this article we will discuss the new introduced member of Dynamics Family. Yes you heard it correctly, one more new member with Name "Microsoft Dynamics 365" . #ProjectMadeira   #Dynamics365

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

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.