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
- 305 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
Dimension not selected error
mpg802
Member Posts: 9
We just upgraded from 2.6 to 3.7. We are getting the above error sporadically when we post gl journals even though the dimension is entered. The user reselects the dimensions and it posts fine. This mainly happens with recurring journals the 1st time it is run after the upgrade. It also occurs in regular journals.
Has anyone else run into similar errors after the upgrade?
Has anyone else run into similar errors after the upgrade?
0
Comments
As you might be aware that in 2.6 you had Departments and Projects, now in 3.7 they have been replaced by Dimensions, hence when the upgrade was done the appropriate codeunit which converts the 2.6
Departments and Projects were not run and hence the system is forcing you to select a Department and Project when posting.
I would write a routine to update the Global Dimension 1 code and Global Dimension 2 code. This would solve your problem.
Regards
Suresh.