Skip to main content

Error 47-1 During Export Objects as Text

Hi all,

Sometime we face an error message while exporting objects as Text file, but when we try to export as .fob it works fine.

Today i require to compare some object so i needed them in text file, when i tried to export as text i get below listed error.

There are errors in the text conversation (text no. 165-205 does not exist in the .stx file).

 Internal error: 47-1

Reason of Error -
The reason of the error is due to objects version conflict. The objects which i was trying to export as text file are of higher version and were in the older version of database. In my case the objects were from NAV 2009 SP1 and were in NAV 5 SP1.

 Resolution of Error -

1) Export the objects into .fob format.
2) Create a new temporary database in new version.
3) Import the exported objects into new created database.
4) export objects into text file.

Regards,
Saurav Dhyani
http://saurav-nav.blogspot.com/
Labels:
Location: Sector 22, 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 »