The module is included in the NAV 2017 Administration Shell, but you prefer to use the PowerShell ISE (like I do ) you always need to install the required NAV modules with these lines first:
The module is included in the NAV 2017 Administration Shell, but you prefer to use PowerShell ISE (like I do ) you always need to install the required NAV modules with these lines first:
Thank you very much. I've seen earlir about the NAV2017 Admin Shell, and I tried to use it, but it appears the same error. But I found another way to uninstall it. With the NAV client, I have the oprtion to manage the extension. I uninsttal it from the extension manager, and after that, the sinchronization has finished succesfully.
Thank you again for your help, I am new working with NAV,and all this issues sound really extrange to me at this moment
After having different conflict, we've decided to merge the different version txt files. The original version, is the one I'm gonna get from the Demo version of NAV2013, and the modified, of course, from mi modified version of NAV2013. But, where can I get the target version if I don't have the NAV2017 installed yet? Is there any repositorie or something to get it?
Thank you very much
Just a suggestion instead of manually comparing and merging the txt files just export the following 3 text files
1. Old Base
2. Old Customized
3. Target Base
and use merge tool to compare and merge these files.
Merge tool is a great tool which literally understands the context of your code and give you conflicts. This will reduce your compare and merging process time.
I have upgrade from NAV 4 to NAV 2016 in 10 hours.
Best Regards
Zohaib Ahmed
Dynamics NAV ERP Technical Consultant.
please like / agree / verify my answer, if it was helpful for you. thanks.
Just a suggestion instead of manually comparing and merging the txt files just export the following 3 text files
1. Old Base
2. Old Customized
3. Target Base
and use merge tool to compare and merge these files.
Merge tool is a great tool which literally understands the context of your code and give you conflicts. This will reduce your compare and merging process time.
I have upgrade from NAV 4 to NAV 2016 in 10 hours.
Thank you. I've used those tools, but I'm sure I'mgonna spend more than 10 hours, I've spent more than 10 hours indeed... The first issue was to achieve that the developmetn environmet imports all the target txt. And after that, to repair all the conflicts when compiling the txt. That is what I'm doing at the moment.
Thank you all for your help, hopefully the next time I write here will be with good news!
Hello everyone(again)
I've almost got it. I achieved to run the demo database in the 2017, everything OK. Also, importing the fob file that previously was exported from the NAV2013, is working perfectly with the demo database. But I'm finding an error with the SQL backup from NAV2013. This are the steps I've follow:
-In SQL, I've created a new database, restoring the backup from our old machine NAV2013
-I created a NEW instance in the NavServer, pointing to the new database I've created in the previous step.
-In the development studio, I've openned the new database, and it has been converted to NAV2017 format without any problem.
-I have imported the fob file with all the application objets.
-When I compile the objects, I found the next objects with errors:
It's important to say, that I have another instance for the Demo database, and works correctly. I have change the databae on that instance, to take the database brought from NAV2013, and the errors occurs, so it seemos not to be an error from the instace.
When compiling, all the objects have this error:
"Cannot load the type:...."
Except the CodeUnit 7152, that has the next error:
"Cannot load the selected library type"
HOw could be this fixed? Probably could be a database error...
I have solved the Outlook error installing the outlokk AddIn, it wasn't installed.
Now I only have the error from the codeunit 7152, "Export Item Analysis View".
It seem to be an error with the automation servers, exactly with this variables:
I'm having issues to find the automation server to find the subtypes for this items.
Where can I find the correct automation server?
Thank you very much!
Migration succeded!! Thank you all for your help, after all the efforts, I finally get the NAV2017 upgraded running, also in one azzure machine.
THanks all for your patience and help!!
Comments
https://blogs.msdn.microsoft.com/nav/2016/11/04/dynamics-nav-2017-creating-new-opportunities/
As you can see, still some bugs here, but you can remove it for the time being and re-install it later if necessary.
Also keep in mind that extensions are not visible in the exported C/AL code.
If you need to check for existing ones:
https://msdn.microsoft.com/en-us/library/mt584145(v=nav.90).aspx
Thank you very much, it was driving me crazy. How can I remove it? Synchronizing with force may be?
I see I have to use the cmdlet, and for that, I shouel import a module, because it's not included in the powershell, am I right??
https://msdn.microsoft.com/en-us/library/mt584146(v=nav.90).aspx
The module is included in the NAV 2017 Administration Shell, but you prefer to use the PowerShell ISE (like I do ) you always need to install the required NAV modules with these lines first:
To make life easier with the ISE I would recommend using this:
waldo.be/2015/07/20/load-dynamics-nav-cmdlets-in-powershell-ise-with-profiles/
Thank you very much. I've seen earlir about the NAV2017 Admin Shell, and I tried to use it, but it appears the same error. But I found another way to uninstall it. With the NAV client, I have the oprtion to manage the extension. I uninsttal it from the extension manager, and after that, the sinchronization has finished succesfully.
Thank you again for your help, I am new working with NAV,and all this issues sound really extrange to me at this moment
Thank you very much
-Mohana
http://mohana-dynamicsnav.blogspot.in/
https://www.facebook.com/MohanaDynamicsNav
https://blogs.msdn.microsoft.com/nav/2016/12/07/cumulative-update-01-for-microsoft-dynamics-nav-2017-has-been-released/
1. Old Base
2. Old Customized
3. Target Base
and use merge tool to compare and merge these files.
Merge tool is a great tool which literally understands the context of your code and give you conflicts. This will reduce your compare and merging process time.
I have upgrade from NAV 4 to NAV 2016 in 10 hours.
Zohaib Ahmed
Dynamics NAV ERP Technical Consultant.
please like / agree / verify my answer, if it was helpful for you. thanks.
Thank you. I've used those tools, but I'm sure I'mgonna spend more than 10 hours, I've spent more than 10 hours indeed... The first issue was to achieve that the developmetn environmet imports all the target txt. And after that, to repair all the conflicts when compiling the txt. That is what I'm doing at the moment.
Thank you all for your help, hopefully the next time I write here will be with good news!
https://www.microsoft.com/en-us/download/details.aspx?id=54609
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
I've almost got it. I achieved to run the demo database in the 2017, everything OK. Also, importing the fob file that previously was exported from the NAV2013, is working perfectly with the demo database. But I'm finding an error with the SQL backup from NAV2013. This are the steps I've follow:
-In SQL, I've created a new database, restoring the backup from our old machine NAV2013
-I created a NEW instance in the NavServer, pointing to the new database I've created in the previous step.
-In the development studio, I've openned the new database, and it has been converted to NAV2017 format without any problem.
-I have imported the fob file with all the application objets.
-When I compile the objects, I found the next objects with errors:
It's important to say, that I have another instance for the Demo database, and works correctly. I have change the databae on that instance, to take the database brought from NAV2013, and the errors occurs, so it seemos not to be an error from the instace.
When compiling, all the objects have this error:
"Cannot load the type:...."
Except the CodeUnit 7152, that has the next error:
"Cannot load the selected library type"
HOw could be this fixed? Probably could be a database error...
Now I only have the error from the codeunit 7152, "Export Item Analysis View".
It seem to be an error with the automation servers, exactly with this variables:
I'm having issues to find the automation server to find the subtypes for this items.
Where can I find the correct automation server?
Thank you very much!
-Mohana
http://mohana-dynamicsnav.blogspot.in/
https://www.facebook.com/MohanaDynamicsNav
No... Do I have to??
-Mohana
http://mohana-dynamicsnav.blogspot.in/
https://www.facebook.com/MohanaDynamicsNav
Thank you!!!!
"It already exist the origin code, ID fields and values: Code:="PAYMTRECON" (more or less)
What should I change??
Ihave to say that I have use the Upgrade Toolkit from "Local Objects", not from "Data Conversion Tools"
THanks all for your patience and help!!
Thank youk I dind't use any of them. Now I only finde this error:
forum.mibuso.com/discussion/68495/problem-with-click-once-in-azure#latest
Any clue?
-Mohana
http://mohana-dynamicsnav.blogspot.in/
https://www.facebook.com/MohanaDynamicsNav