Howdy, Stranger!
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
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 304 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Very long time of importing single codeunits from txt
asdasty
Member Posts: 26
Hello guys,
we are currently working on update from NAV 2009 to NAV15. We had to manually change some codeunits and merge them with existing changes so now we are trying to import our new objects to NAV 2015. We have .txt files from even single codeunits and still many problems. Import lasts very long and stucks very often in some place. There are no messages at all so we don't know what is the problem. I've noticed that common problematic objects are that one connected with Outlook. Do you have any ideas why do we have this kind of problems?
It's worth to mention that few days earlier we were importing tables and there was no problem at all.
we are currently working on update from NAV 2009 to NAV15. We had to manually change some codeunits and merge them with existing changes so now we are trying to import our new objects to NAV 2015. We have .txt files from even single codeunits and still many problems. Import lasts very long and stucks very often in some place. There are no messages at all so we don't know what is the problem. I've noticed that common problematic objects are that one connected with Outlook. Do you have any ideas why do we have this kind of problems?
It's worth to mention that few days earlier we were importing tables and there was no problem at all.
0