Skip to main content

NAV 2013 - Import & Export as XML not supported.

Hi all,

Just an informative post, suggested by +Saheli Mukherjee.

When Navision moved to three tier Architecture (NAV 2009), we had a new File type option during export & Import window, i.e XML.





We used this file type for importing pages that have been converted by Transformation Tool released with NAV 2009.

Transformation tool was introduced to convert Forms into Pages. We use Transformation Tool for converting Customized Forms into Pages.

With Release of NAV 2013, Microsoft Have again removed this File Type Option from export & Import window.


I Found this while doing an upgrade project from NAV 5 to NAV 2013 R2.

I converted forms to pages using transformation tool and tried to import them into NAV 2013 R2 directly but there was no file Type as XML.

So HOW we can import output of transformation tool to NAV 2013 R2.

Resolution -

For this you need to import converted pages, first into NAV 2009/SP1/R2.
Once imported successfully export Pages with file Type fob/txt.
Import the FOB/TXT file into NAV 2013.

Regards,
Saurav Dhyani
saurav-nav.blogspot.in
Labels:
Location: Sector 62, Noida, Uttar Pradesh, India

Comments

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 »

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 »

🚀 Exploring Vibe Coding with GitHub Copilot for Business Central.

Hi All, In a recent #BCOpenDiscussion session, we delved into the fascinating concept of Vibe Coding —a new way of building software where developers collaborate with AI (like GitHub Copilot) to co-create solutions.  The session covered practical setup, how AI understands context, and even touched on Microsoft's new Model Context Protocol (MCP) integration for enhanced learning. Let’s break down the journey, step by step.
Post a Comment
Read Complete Article »