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

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.