Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 269 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Set powershell to use an older nav version installed
martinhocosta88
Member Posts: 27
Hello,
I need to use Export-NAVdata on a NAV 2015 database, and even though I've imported the modules from that build, powershell tells me i need to convert the database since I have 2016 also installed on the same machine. Any workaround for this?
Thanks in advance!
I need to use Export-NAVdata on a NAV 2015 database, and even though I've imported the modules from that build, powershell tells me i need to convert the database since I have 2016 also installed on the same machine. Any workaround for this?
Thanks in advance!
0
Answers
Try the Remove-Module before Import-Module. Like:
IF ( Get-Module -Name Microsoft.Dynamics.Nav.Apps.Tools ) { Remove-Module -name Microsoft.Dynamics.Nav.Apps.Tools -force }It sometimes looks to me that powershell can keep things (modules) in memory after I force a stop on a script and then I have to restart powershell.
Good luck.