Developer’s Toolkit for NAV 2009

drayorama · 2009-01-06

Hi
I need to upgrade from NAV 5.0 SP1 to NAV 2009 (classic). The running database is heavily modified; therefore I will definitely need to do some merging. The problem is that I didn't find any newer Developer’s Toolkit than 2.0 SP3.

Should I wait for a newer version or I can use the existing one?

P.S. In the Upgrade Toolkit for NAV 2009 documentation it’s mentioned that I have to use Developer’s Toolkit but nothing said regarding it's versions.

mthomsen · 2009-01-06

Hi,

We hope to have an updated NDT ready later this month. There are some known issues with the existing one due to some of the new object types we have introduced in NAV 2009, so I would recommend waiting.

Thanks.

ara3n · 2009-01-06

that's great news. I haven't updated my DTK version for a couple of years.

drayorama · 2009-01-07

That's great!

Michael, thanks for the info.

Saga · 2009-02-13

Hi Michael,

are there any good news regarding an upgraded version of the NDT to work with NAV 2009 objects?
The toolkit is a very powerfull tool and I use it often. Now I need a version working with pages (and later with RDL reports, too ;-))...

Regards
Heinz

davmac1 · 2009-02-13

There is one out there right now on the NAV2009 download page

ara3n · 2009-02-13

The Developer toolkit is not available yet. It's just the upgrade toolkit.

mthomsen · 2009-02-26

We have unfortunately encountered a small delay. It should be ready in another 1-2 weeks.

Kind regards, Michael

mthomsen · 2009-03-05

I'm happy to annouce that the Developers Toolkit for NAV 2009 (NDT_v3.00.400) has been released on PartnerSource:
https://mbs.microsoft.com/partnersource ... page=false

Regards, Michael

ara3n · 2009-03-05

that's great news

gvolkov · 2009-03-06

Hey guys, i am trying to understand something. and it may be the fact that i am just missing something, or just not understanding.

in the DevKit manual it says:

Exporting Application Objects
To create an object file with all object data, do the following:
1 Start the Microsoft Dynamics NAV client.
2 Connect to your application database and open the Object Designer window.
3 Click All on the left side of the Object Designer window and mark all objects.
4 Export these objects to an object file using text format.
You do not always need to export all objects of your application database. For example,
if you have changed only some objects and you want to analyze them, you can select
and export only these objects.
Note
If you want to use objects in a compare and merge process, you must export all object
versions with the same Microsoft Dynamics NAV client version (for example Microsoft
Dynamics NAV 2009), because of changes in the Microsoft Dynamics NAV text file
format between the versions.

Where bold, does it actually mean that if i am upgrading from version 4.0 i have to open 4.0 base database in NAV 2009 and export all objects in text format from 2009 client? If i am not mistaken, and i may be, before i used to export text file with a version that corresponds to the database version.

ara3n · 2009-03-06

Yes you need to open the 4.0 db with 2009 exe and then export it.

DenSter · 2009-03-06

Really? Does that mean you have to make a copy of your non-2009 database, convert to to 2009 so that you can use the DTK every time you need to refresh your objects?

gvolkov · 2009-03-06

Really? Does that mean you have to make a copy of your non-2009 database, convert to to 2009 so that you can use the DTK every time you need to refresh your objects?

looks like it. unless you mean something else by "refresh your objects"

ara3n · 2009-03-06

DenSter wrote:

Really? Does that mean you have to make a copy of your non-2009 database, convert to to 2009 so that you can use the DTK every time you need to refresh your objects?

One reason to get all your clients to do exe upgrade to 2009.

I've done on 3 clients and moving forward.

jreynolds · 2009-03-06

From the new developer toolkit manual:

When importing objects from Microsoft Dynamics NAV, be aware of the following
restrictions:
(1) Objects of type PAGE will not be imported.
(2) The RDLDATA and REQUESTPAGE sections of the object type REPORT are not
imported in this version of Developer’s Toolkit. Be especially aware of this when
exporting Report objects from the Developer's Toolkit, as the exported versions will not
contain these two sections and therefore may be inconsistent with the original versions
of the objects.

I can understand the difficulty with the RDLDATA and I'm not even sure what form it would take or how useful it would be. But not having pages - what a disappointment!

Any idea when we will have a version that supports pages?

kine · 2009-03-06

mthomsen wrote:

I'm happy to annouce that the Developers Toolkit for NAV 2009 (NDT_v3.00.400) has been released on PartnerSource:
https://mbs.microsoft.com/partnersource ... page=false

Regards, Michael

Have problem with the toolkit. Try to use "Where used with..." e.g. on field "No." of table 18. For me it ends with error (DB is on SQL2008):

Developer's Toolkit for Microsoft Dynamics NAV
The Code Line table contains a Boolean field that does not use a BIT SQL Server data type. A value other than 0 or 1 has been found in this field:Field: TransferFieldsExistsSQL type: TINYINTValue: 1701734732
OK

I have used objects already imported in the default backup i the installation...

kirtangor · 2010-02-15

I agree with jreynolds; I too am disappointed with the new NDT release because it doesn't support pages.

Is there any new release in sight in the near future containing support for pages?

PureHeart · 2010-04-21

Yes I agree why doens't support pages?
Is there any plan to support them?

Howdy, Stranger!

Quick Links

Categories

Developer’s Toolkit for NAV 2009

Comments