I am starting an upgrade from Nav 3.70 to Nav 4.0. I have tried to export the objects in the DB in text format to import into the Dev Toolkit. I cannot do this because of a permissions error for codeunit 'Licensed Employee Count Mgmt', eventhough I am in as administrator.
I also tried importing into the toolkit directly from the DB. The transfer failed because of the same codeunit. (I didn't encounter this when upgrading from 3.60 to 3.70.)
I also tried importing an .fob file, but I got an error relative to the Fin.stx file. I tried every .stx file I have access to and it didn't seem to make a difference.
I am wondering if others have run into these same issues and how you dealt with them?
Thanks for any suggestions.
SGM
0
Comments
If you are customer, you do not have enough permission to do complete upgrade...
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
I downloaded the ToolsCD for 4.0 and put the Dev Toolkit on my machine. I created a new DB in 4.0 and imported the DevTool.fob file in the Toolkit folder, then created a company. I opened up the Devtoolkit and attached the DB. (I tried specifying which fin files to access in the load process and I also loaded it and then put the fin files into the folder manually, but the outcome was the same.)
I tried to export my DB in a textfile format as mentioned, but that didn't work because of the permissions error. I exported an .fob file instead. When I try to import that into the toolkit it gives the error: "The language of the file to import does not match the language of the .stx file. Import stopped!". I have verified both fin files and tried different ones without success. I also tried checking the "Import from Navision Client" box when creating the Import Version in the toolkit, but it also failed on the 'Licensed Employee Count Mgmt' codeunit (37003000) due to permissions. (I also pulled this up in the Object Designer and can only run it, not design it.)
I am following the documentation for the DevToolkit, but I seem to be continually running into issues.
I would still like to know why that one object appears to be different, if others are experiencing the same issues and if so, why it isn't mentioned in any of the documentation. (I haven't checked back, but I believe it was created as of version 3.70).
Thanks!
generally: the addons are not accessible with personal licenses and you need to have special settlement with the owner of this addon. Workaround is situation, when user have bought this addon for use and have application builder or solution developer granule in the license...
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
Regards!
You can create a report that runs through the object table a checks via the licence permission table wheather you have read access with your licence. Then you can put a dummy filter character like ~ in front of the Version List of all the Objects to which you have read access. Then set a filter on this character "~*" in the Import Version Card of the Developers Toolkit. This way you will only import objects that produce no read permission errors.
Don't forget a function to delete the ~ in the Version List afterwards.
RIS Plus, LLC
MVP - Business Apps