Developers Toolkit error Bug

Belias

i couldn't find this in google, i suppose there's not in mibuso, too...
Do anyone have ever seen this?
This happens when i'm trying to import a text file in dev toolkit, version 2.00.291 (the last one before the one that support nav2009)

---

Developer's Toolkit for Microsoft Dynamics NAV

---

The Object Imported table contains a field with a date value that cannot be used with SQL Server:Record: Entry No.='1111'Field: Date='01/01/0001'

---

OK

---

kapamarou

Are you using DevToolkit on SQL server?
Do you have an object with modification date blank?

Belias

1. yes
2. no

einsTeIn.NET

Looks like it has something to do with the 1111st object you want to import. Maybe modification date is not blank but older than 01/01/1753?!

kapamarou

It has to do with the SQL date being too early.

Do you have a clue as to which object the import stops?

Belias

yes, for sure, but the date is new! here's a slice of the "wrong" object

OBJECT Table 60259 Intent Declaration
{
  OBJECT-PROPERTIES
  {
    Date=17/09/09;
    Time=12.04.59;
    Modified=Yes;
    Version List=EV1.0;

i've also tried to modify the text file like this

OBJECT Table 60259 Intent Declaration
{
  OBJECT-PROPERTIES
  {
    Date=17/09/2009;
    Time=12.04.59;
    Modified=Yes;
    Version List=EV1.0;

but without results!

kapamarou

Are you importing to a new database or just importing this text file with a single object?

Belias

found it (maybe, i don't know why this is happening...it's a bug, i think).
the object right before the wrong one, goes error for another reason (i don't know why, maybe an unexpected character), but it's only a warning, because you can continue the import
after that, the tool screws up something and maybe nullify the date...devtool sucks a bit... ](*,)

kapamarou

Ok. You could open the database with the appropriate Nav client and take a look into table 99003600 Object Imported to see what got written there.

Belias

[-X
No commit guys...

kapamarou

Belias wrote:

[-X
No commit guys...

What do you mean?

Belias

i've bee a little hermetic, sorry
there's no commit in the process: the error automatically roll backs all the inserts, which means the table Object Imported is empty.
anyway, i finally managed to import the text file. there were 2 similar errors: one is the one i've described here, and the other was a true error: there was a report without modification date and time.

Ravi_Prakash_Goyal

I got the same error and fortunately found the solution. Actually, in my case, the errorneous object have Date in different format. All objects was having Date=01-01-13, while the errorneous object was having Date=18/01/13. Both are in DDMMYY format but the Special characters are different. In correct object it is hyphen (-), while in incorrect object it is backslash (/). I changed '/' to '-' and the file imported successfully.

Hope this will help someone.

Ravi_Prakash_Goyal

Along with the above solution, the another issue could be the format of the Object Date. I mean some objects are in DDMMYY format while the others are in MMDDYY format. Please keep the same Date format across the file and then try to import the file.

Reedberg

I had the same issue. In my case the scenarion was the following:

1. Have a NAV version 5.
2. Upgrade to NAV version 6.
3. System created certain tables with empty "Date" and "Time" fields*
4. Export all objects into txt file and import into Dev Tool Kit gives the error message exactly as described above.

The solutions are:
1. In a text file find all Objects with empty date and time, provide some values in these fields (Date = ;, Time = ; )
2. In the Object Designer, reset all filers, set filter on the Date field with empty date, populate date and time manually. Export all objects in a txt file in a second time.

* The list of tables with empty date and time after upgrading to NAV6:
2000000054 Windows Login
2000000068 Record Link
2000000073 User Personalization
2000000075 User Metadata