Dynamics NAV Developer's Toolkit v3.00.400

Administrator

Dynamics NAV Developer's Toolkit v3.00.400
The Developers Toolkit helps partners work faster and with accuracy, thanks to the direct link between the Microsoft Dynamics NAV development environment and the toolkit. While analyzing or upgrading Microsoft Dynamics NAV, you simply switch between screens as you work. Its well-laid out and color-coded graphical user interface gives you a clear, in-depth picture of all the elements you are working with, application code, and relations between objects.

The Microsoft Dynamics NAV Developers Toolkit, including tools for Source Analysis, as well as a Compare and Merge tool.

http://www.mibuso.com/dlinfo.asp?FileID=1058

Discuss this download here.

sc00by

Got this ... installed it and have setup the NDT database - this must be Dynamics Nav 2009 client created database.

I'm trying to import objects now from my Nav 4.0 SP3 (Update 6.15) client but it shows an error on every table but doesn't really give any clues what the error is :roll:



Anybody had any success loading objects from an older client into this version of NDT?

Rob.

reijermolenaar

I got the same message.
It seems that this version expects the new section FIELDGROUPS.

Bummer...

sc00by

:shock:

Well that's weird isn't it?

The pdf guide refers to V3.70 objects in the compare and merge tool section so it seems to indicate these can be loaded in :-k

So is this a :bug: then?

This is such a useful tool but just tends to be a right pain in the butt to get working properly - we use the SQL Server database version and have 5 developers accessing it but this sort of "Upgrade" just seems to have been poorly tested to me especially as the previous version has a bug http://mibuso.com/forum/viewtopic.php?f=23&t=32184 with any client that has >= hotfix update 6.5 applied (V4 SP3).

Are there any third party tools out there that anybody is successfully using?

Rob.

reijermolenaar

If you are mainly using the Where Used function of the NDT you can try the Object Manager.

http://www.mibuso.com/dlinfo.asp?FileID=826

jm

Hi,

get the same error during import.

Seems to depend on the multiline of the properties to the fields in the table:
e.g. Table 3 "Payment Terms", field 1:

CaptionML=[DEU=Code;
           ENU=Code];
           NotBlank=Yes }

I have opened a new Support Request to solve this problem and will come back if there is an answer.

sc00by

Thanks - it's good to know that it isn't just "Me"

I'll watch this space I guess ... :whistle:

geosava

This toolkit is only for NAV2009??

I want to migrate from NAV4 SP1 to NAV5.0 SP1.
I create my developer's toolkit database with NAV5.0 SP1 client and when i am trying to connect to that database with the toolkit i take a 52017 error.

What toolkit should i use for migrating from 4SP1 to 5.0SP1??

Thank you in advance.

markodrummer

Hey all - I've been receiving the same error trying to import Base NAV 4.0 SP2 code. Anybod had any luck on getting around this one?

Many thanks!

Stryke69

The Developers Toolkit v3.00.400 only works for objects from NAV2009 Databases.
So if you want to use this toolkit for objects from Versions <NAV2009, you have to convert your database (or better a copy of your database ) to NAV2009.
Then you can export your objects and import them into your toolkit.

Or you keep using an older toolkit for that.

sc00by

I know the initial database must be 2009 but it makes no sense that you cannot import objects from previous versions - what is the point of that :?:

In fact, when I had the initial problems attempting to import from a Nav 4 database, I checked through the pdf manual and it actually states that you can import from versions prior to 2009.

Why do you think this is only possible from 2009 databases?
If there is a some documentation I've missed, please point me in the right direction.

Thanks,

Rob.

Stryke69

@ sc00by: You are right, there are no problems in importing tables, forms and codeunits prior to 2009.
But when it comes to reports, you always get an error for each report you try to import. If you confirm that error, the report is imported, but do you really want to confirm an error message for each report you try to import?
I know what the manual says, I just tried these things on my own (importing objects prior 2009 into DevTool 3, importing objects from 2009 in DevTool prior 3,...)

djkdjk

Hi Josef,

Did you have an answer form Microsoft for your Support Request?
I have the same problem.
Thanks

Jeannot Keiser

jm wrote:

Hi,

get the same error during import.

Seems to depend on the multiline of the properties to the fields in the table:
e.g. Table 3 "Payment Terms", field 1:

CaptionML=[DEU=Code;
           ENU=Code];
           NotBlank=Yes }

I have opened a new Support Request to solve this problem and will come back if there is an answer.