Upgrade from 2013R2 to 2017

aitorEG wrote: »

Kowa wrote: »

"Sales and Inventory Forecast" is an extension which is included in NAV 2017.
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??

Kowa wrote: »

Uninstall extensions with PowerShell: Uninstall-NAVApp
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 PowerShell ISE (like I do ) you always need to install the required NAV modules with these lines first:

Import-Module "${env:ProgramFiles(x86)}\Microsoft Dynamics NAV\100\RoleTailored Client\Microsoft.Dynamics.Nav.Model.Tools.psd1" -WarningAction SilentlyContinue | out-null
Import-Module "C:\Program Files\Microsoft Dynamics NAV\100\Service\NavAdminTool.ps1" -WarningAction SilentlyContinue | Out-Null
Import-Module "${env:ProgramFiles(x86)}\Microsoft Dynamics NAV\100\RoleTailored Client\Microsoft.Dynamics.Nav.Apps.Tools.psd1" -WarningAction SilentlyContinue | Out-Null

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

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...

When I run the data upgrade process, I have the next error:

"It already exist the origin code, ID fields and values: Code:="PAYMTRECON" (more or less)
What should I change??

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!!

Kowa wrote: »

In case you used any of the two Cumulative Updates (in combination with Multi-Tenancy and CRM Integration), note that there is a critical bug for this scenario which led to both of these being withdrawn until further notice (see edited blog article https://blogs.msdn.microsoft.com/nav/2017/01/16/cumulative-update-02-for-microsoft-dynamics-nav-2017-has-been-released/).

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?