![]() The d/l completed before I found the answer so I abandoned the container idea for NAV2017 and just installed it. At some point I just started the NAV2017 DVD download as I was researching a problem. I have a terrible memory though, so I always start from scratch, and what I could find was outdated. I spent quite some time trying to make NAV20 work in containers, because I have used them successfully in the past. What does and does not work? This, to me, is a pragmatic problem. Mind you though, the localization for the US is called ‘na’ in NAV, not ‘us’ like in BC. You can find this information on Freddy’s blog. Both of these versions are available in containers, and supposedly all you need to do is put together the correct artifact URL. The end user is on NAV2017, and the ‘new’ version of the add-on is in NAV2018. ![]() Since this version is not available in containers, I had to actually install this version. To be able to identify the mods of the original add-on, I needed a C/SIDE environment for NAV2013R2. I won’t bore you with the details of the actual ‘upgrade’, nobody wants to read about those. Technically, this was a downgrade of the add-on objects so I had to be careful to avoid any incompatible object attributes. The task at hand was to implement a newer version of the add-on, which was developed in NAV2018. They had an older version of this add-on, which was developed on NAV2013. Just to paint a picture… First of all, the end user is on NAV2017. This post describes what I found is what does and does not work if you want to do this using Docker containers. It’s been years since I’ve done any C/AL development, and I thought this would be a cool task to work on. For this task I would have to get a working C/SIDE in a number of versions. ![]() One of my clients asked me if I would be able to help them with an ‘upgrade’ of an add-on for Dynamics NAV for one of their customers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |