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
- 310 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
Upgrade from 2015 to 2017, different number of dimension set id records
Rodtmclean
Member Posts: 89
Hi All,
I have ran an upgrade from 2015 to 2017 and there is a slight difference in the number of dimension set id records.
In one company it started out as 4627 and ended up as 4444, losing 183 records
In another company it started out as 8440 and ended up as 8511, gaining 71 records
Can the upgrade modify Dimension Set ID as it runs through and is this anything to be concerned about?
Many thanks
Roddy
I have ran an upgrade from 2015 to 2017 and there is a slight difference in the number of dimension set id records.
In one company it started out as 4627 and ended up as 4444, losing 183 records
In another company it started out as 8440 and ended up as 8511, gaining 71 records
Can the upgrade modify Dimension Set ID as it runs through and is this anything to be concerned about?
Many thanks
Roddy
0
Comments