Strange problem when import txt source in 2009R2

badguy
Member Posts: 1
Hello.
I found strange behavior at one of our bases today.
When importing a file with the source code, where there is an action with additional properties after RunObject, for examle:
the classic gives me an error and stops the import.
Microsoft Dynamics NAV Classic
You cannot enter ' RunObject=Codeunit 15;' in ObjectID.
ОК
But when I remove the porperty
or change the order of properties
or change the codeunit number to the codeunit name
the file is imported successfully
As I found out in experiments, the main requirement is the absence of "extra" characters after the codeunit number (i.e. ";").
The problem is that when unloading the source texts, the classic decides in what order to unload the properties and corrupt the source code. That is, even if you try to export and import the file without changes, an error occurs.
And the most important thing is that this happens only on one of our bases (so are the development bases derived from it). The rest of the bases work as usual.
I found strange behavior at one of our bases today.
When importing a file with the source code, where there is an action with additional properties after RunObject, for examle:
{ 42 ;1 ;Action ; RunObject=Codeunit 15; Image=EditLines }
the classic gives me an error and stops the import.
Microsoft Dynamics NAV Classic
You cannot enter ' RunObject=Codeunit 15;' in ObjectID.
ОК
But when I remove the porperty
{ 42 ;1 ;Action ; RunObject=Codeunit 15 }
or change the order of properties
{ 42 ;1 ;Action ; Image=EditLines; RunObject=Codeunit 15 }
or change the codeunit number to the codeunit name
{ 42 ;1 ;Action ; RunObject=Codeunit Gen. Jnl.-Show Card; Image=EditLines }
the file is imported successfully
As I found out in experiments, the main requirement is the absence of "extra" characters after the codeunit number (i.e. ";").
The problem is that when unloading the source texts, the classic decides in what order to unload the properties and corrupt the source code. That is, even if you try to export and import the file without changes, an error occurs.
And the most important thing is that this happens only on one of our bases (so are the development bases derived from it). The rest of the bases work as usual.
0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions