Skip to main content

Application Merge Utilities - Things to Keep in Mind Using Merging Application.

Hi All,

This is the Second Post in the Series. If you haven't read the earlier post please refer the Index of the Post.

Below are points to Note About Application Merge Utilities, which will help you while Using the related Cmdlets.

Object Types supported by the Application Merge Utilities 

The following object types can be merged using the new cmdlets:
• Tables                                
• Pages
• Reports
• Codeunits
• MenuSuites
• Queries
• XMLPorts

The following object types cannot be merged: 
• Dataports
• Forms
• Reports with Classic report sections

So This tool cannot help us with Reports with Classic. This is one challenge that we will have during Upgrade from Version Lower than NAV 2013.

But i would say its still a great tool which should reduce the Upgrade Time Drastically if used correctly. You will find same in Other Post in this series.

Special Handling Required The application merge utilities handle all object types, but some better than others. Also, some parts of some object types require special attention from the tool or from you as described in the following list:

• Application object properties 
(Discussed in How to Use - GET & SET NAVApplicationObjectProperty)

Each of the application object properties in the application object files often calls for hands-on handling. You can run the cmdlets with the default parameters values, but you can also overrule the default behavior by setting parameters specific for application object properties, or you can run other cmdlets for post-processing.

Two cmdlets are available specifically for post-processing: Get-NAVApplicationObjectProperty and Set- NAVApplicationObjectProperty.

• Documentation triggers (Discussed in How to Use - Merge NAVApplicationObject)
In each object, the documentation trigger is used for many different purposes. Documentation, of course, but also for tracking changes with date or history semantics built into it. You can use the cmdlets to modify the contents of the documentation section.

• ControlID (Discussed in How to Use - Merge NAVApplicationObject)
Sometimes, developers in-house or external partners create objects in the same ID range as you. This surfaces in the merge process as conflicts and hence as work to do. The application merge utilities provide ways to handle that, depending on your needs and requirements.

• CaptionML 
Captions are an integral part of the solution, but when you compare two versions of the same object with two different languages, you will see extensive differences. Microsoft plan to add support for handling captions as part of the application merge utilities in a later version. However, you can choose as a temporary workaround to export captions to an external file during the application merge.

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.