Share
Report
26Hi!
I'm planning to upgrade our business central version 20.0 to 22.2. For that purpose I have followed the guide https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-technical-upgrade-v22 . After reading and executing it all with success and finally get my testing env upgraded (and working) to the 22.2 version (full upgrade all BC components and application in version 22.2) the following doubts have issued to me. I hope you could help me.
- In task 1 and point 4, it says you need to copy three directories from the add-in's folder in the 20.0 instance. Later when you setup the new 22.2 version, it says to replace the corresponding existing elements in the addins folder of the new BC version. But, if I do that, later I have issues due to that replacing. If I ignore this /task 1 point 4/ all works... Is it really needed?. Am I missing something?.
- In task 2 I assume I could keep working with the permission sets and permissions the way they are in production in version 20. By what I have read, permissions stored in database keep there and work, although by default BC22 seems to set UsePermissionSetsFromExtensions to true. So in 22.2, should I assume I can really keep on working the way in 20, although BC22 too enables UsePermissionSetsFromExtensions to true for being able to define too AL permissions?.
- In task 7, it does the repair-navapp for the non upgradable (of version) add-ins for the current version of BC (22). Can I first at least (which the guide does not), publish the new System, Base and application versions of the current version of BC?. I would say it's even important publishing them and unpublishing the old ones, prior to issuing the repair-navapp for all the extensions (I do /
Get-NAVAppInfo -ServerInstance $NewBcServerInstance | Repair-NAVApp/)... am I wrong?.- In some guides I have seen that you should change the application version near the end of the proccess (Set-NAVApplication -ServerInstance XXXX -ApplicationVersion XX.XX.XX.XX -Force). Is it convenient setting it?. And by the way, if it is... by what I have seen, it says you should launch later that command the commands /Sync-NAVTenant -ServerInstance XXXX -Mode Sync/
and /Start-NavDataUpgrade -ServerInstance XXXX -FunctionExecutionMode Serial/ (I do it with Serial because I prefer company by company..). This commented commands in this paragraph are not documented in the Microsoft office guide for doing this upgrade... perhaps should they exist?.
and /Start-NavDataUpgrade -ServerInstance XXXX -FunctionExecutionMode Serial/ (I do it with Serial because I prefer company by company..). This commented commands in this paragraph are not documented in the Microsoft office guide for doing this upgrade... perhaps should they exist?.
Now, a couple of questions about commands...
- The difference between sync-navapp and sync-navtenant is that sync-navapp is for invoking after each extension publish and sync-navtenant is valid for doing the sync for all the extensions?. Because finally, apart from /Platform/, all are extensions... system, base and application are finally extensions... so... perhaps sync-navtenant is the longer way of having the same result?.
- More or less the same for Start-NAVAppDataUpgrade and Start-NavDataUpgrade?. One it's a way of calling for upgrade data and install each extension for which you call it AND the other one for the whole totality of the extensions?.
Basically are sync-navtenant and Start-NavDataUpgrade the corresponding commands for performing it's job but tenant wide?.
Thank you much for all your time. I have not been able to clarify this doubts by reading information like office guides, ebooks and some Youtube videos...
Best regards,
All responses (
Answers (
