Skip to main content

Application Merge Utilities - Introduction.

Hi All,

As Promised long back In this post we will discuss about a New Feature Released by Microsoft with Rollup 9 of NAV 2013 R2.

Microsoft have released a set of Cmdlet for Merging Application Object Source Files.

This Feature can be used with and after NAV 2013 R2 with Update Rollup 9 Installed.

Here is what Microsoft Says about it -
"Microsoft Dynamics NAV includes Windows PowerShell cmdlets that help you apply changes to Microsoft Dynamics NAV solutions. You can use Microsoft Dynamics NAV cmdlets to modify application object source files in the Microsoft Dynamics NAV 2013 R2 Development Shell, or by importing the Microsoft.Dynamics.NAV.Model.Tools.psd1 module into the Windows PowerShell Integration Script Environment (ISE). "


We will see the complete Procedure and Current Limitation in a Multiple Post.

As post will be Released this page will contain link of all the Post Related to Merging Application objects Source Files.

Below will the future articles which will be released for the same -

1. Introduction To - Merging Application Object Source Files. (This Post)

2. Things To Keep in Mind Using Merging Application Object Source File.

3. How to Use - GET & SET NAVApplicationObjectProperty.

4. How to Use - SPLIT & JOIN NAVApplicationObjectFile.

5. How to Use - Compare & Update NAVApplicationObject.

6. How to Use - Merge NAVApplicationObject. (BEST ONE)

So Let's Begin. If you would like to read the details please refer the PDF released with Rollup 8 or Refer to Microsoft Team Blog Article.

If your Build is Greater than Rollup 8  then you can navigate to STEP 6.

Work Around (If you want to use feature Before Build 9) -

STEP 1. IF my current Build is Lower than Rollup 9 how can i use the Merging Application Object Source File Cmdlet.

** You Should always keep your solution to latest Build OR at least Rollup 5 (Before this build there are critical Issues).

So Below is a sample -

My Build is 36281 (i.e Rollup 5). But i would like to use the Merging Application Cmdlet.

STEP 2. Extract the Rollup 9 Build, Unzip DVD_BUILD37221.

STEP 3. Navigate to RoleTailoredClient\program files\Microsoft Dynamics NAV\71\RoleTailored Client.

STEP 4. Copy Below Listed Files from the Folder.

Files to Copy ==>

1.Microsoft.Dynamics.Nav.Model.dll
2.Microsoft.Dynamics.Nav.Model.Tools.dll
3.Microsoft.Dynamics.Nav.Model.Tools.dll-Help.xml
4.Microsoft.Dynamics.Nav.Model.Tools.format.ps1xml
5.Microsoft.Dynamics.Nav.Model.Tools.psd1
6.Microsoft.Dynamics.Nav.Model.TypeSystem.dll



STEP 5 - Paste them in the Installed Role Tailored Client Folder.
Default Path - C:\Program Files (x86)\Microsoft Dynamics NAV\71\RoleTailored Client



STEP 6.So Let's try to Load the Module in PowerShell. (How to Open Powershell?)

In the Command Window We will type the Below Command to Load Cmdlet.

This Command Will Import the Cmdlet which will be Used to Merge Application Objects and the second Line will get the list of Function we have after importing module.
---------------------------------------------------------------------------
Import-Module "${env:ProgramFiles(x86)}\Microsoft Dynamics NAV\71\RoleTailored Client\Microsoft.Dynamics.Nav.Model.Tools.psd1" -force
Get-Help "NAV"
---------------------------------------------------------------------------
** This might ask you to update the help, if required you can do the same.



So with this Cmdlet we got 7 Functions (as listed below) we will see all of them in Next Couple of Post.

Update-NAVApplicationObject - Applies a set of deltas to the specified application objects.
Split-NAVApplicationObjectFile - Splits a text file that contains two or more application objects.
Set-NAVApplicationObjectProperty -Sets Microsoft Dynamics NAV application object properties.
Merge-NAVApplicationObject - Compares the changes that have been made to application objects.
Join-NAVApplicationObjectFile - Combines multiple application object files into one text file.    
Get-NAVApplicationObjectProperty -Gets Microsoft Dynamics NAV application object properties
Compare-NAVApplicationObject - Compares text files with Microsoft Dynamics NAV application object.

Stay Tuned for More.

Regards,
Saurav Dhyani
saurav-nav.blogspot.com

Comments

Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

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.