Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 310 Dynamics CRM
- 110 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Import-NAVData not Working
chrisdf
Member Posts: 82
I may be wrong but I believed that the Import-NAVData was a tool whereby we can copy companies from one database to another - given they are the same application of course.
I have a solution database in which I wanted to create a new company (let's say the Cronus company) so I performed the following actions all in NAV2017 CU1.
1. Created a new Cronus database.
2. Exported the objects from my Application and imported them into the new Cronus DB so they are the same object set.
3. Did all the synchronisation in both databases.
4. Checked both databases are the same version etc.
5. Used the Export-NAVData tool to export the default Cronus company from the newly restored Cronus Database.
6. Tried to use Import-NAVData powershell command to import that company into my Application.
The process failed complaining that table with ID 27 had either different fields or keys.
Not sure why it failed on that table (27), as there were several tables below that table with modifications on them.
I exported table 27 to text (both databases) and compared - they are both exactly the same.
Tried using the "Export Data" utility in the RTC to the original database where it came from and that works fine.
So, does this feature actually support copying companies from one DB to another (with the same version and object sets) or am I missing something here?
Any help appreciated - thanks!
I have a solution database in which I wanted to create a new company (let's say the Cronus company) so I performed the following actions all in NAV2017 CU1.
1. Created a new Cronus database.
2. Exported the objects from my Application and imported them into the new Cronus DB so they are the same object set.
3. Did all the synchronisation in both databases.
4. Checked both databases are the same version etc.
5. Used the Export-NAVData tool to export the default Cronus company from the newly restored Cronus Database.
6. Tried to use Import-NAVData powershell command to import that company into my Application.
The process failed complaining that table with ID 27 had either different fields or keys.
Not sure why it failed on that table (27), as there were several tables below that table with modifications on them.
I exported table 27 to text (both databases) and compared - they are both exactly the same.
Tried using the "Export Data" utility in the RTC to the original database where it came from and that works fine.
So, does this feature actually support copying companies from one DB to another (with the same version and object sets) or am I missing something here?
Any help appreciated - thanks!
0
Answers
i had same problem and i'd solved it:
http://forum.mibuso.com/discussion/67877/nav-2017-cronus-db-problem#latest
So to confirm ... are we saying that because my application was built on Cronus 2017 CU0 this will not work because I am trying to import Cronus 2017 CU1 and the CU1 release has some extensions loaded that were not there in CU0?
So running an upgrade from CU0 to CU1 is OK from an object point of view but we now need to consider if MS are adding extensions to the new release?
If so, is there an "idiots guide" as to what extensions are in the different releases and when doing an upgrade, how should we consider this in the "new world" i.e. should we all now think about upgrading objects and then adding in new extensions...