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
- 313 Dynamics CRM
- 110 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
Migrating Account Schedules from NAV40 to NAV2009
rsaritzky
Member Posts: 469
Hi,
Has anyone encountered the issue with the Acc. Schedule Line table in NAV40 regarding the field called "Calculate"? It is an option field that has been replaced (from a functional standpoint) with two fields in NAV2009 - "Row Type" and "Amount Type". In order to overlay objects during a data migration on SQL, this field can't have an option value other than 0 (the first option).
Also, related, the Column Layout table has columns for "Dimension 1 Filter", "Dimension 2 Filter" and "Business Unit Filter" which have been replaced with "Dimension 1 Totaling", "Dimension 2 Totaling" and "Business Unit Totaling". These fields have different field numbers in the Column Layout table for NAV2009.
Now, converting these values isn't too big of a deal, but I was surprised to discover that the Upgrade Toolkit apparently does not address these issues. I plan on tweaking the upgrade codeunits, but it's sort of strange (to me) that this was overlooked.
Has anyone encountered this? Or is our client's Account Schedules just a little bit more sophisticated in terms of use of these fields that it's not an issue for a large percent of the upgrades that have been done?
Thx
Ron
Has anyone encountered the issue with the Acc. Schedule Line table in NAV40 regarding the field called "Calculate"? It is an option field that has been replaced (from a functional standpoint) with two fields in NAV2009 - "Row Type" and "Amount Type". In order to overlay objects during a data migration on SQL, this field can't have an option value other than 0 (the first option).
Also, related, the Column Layout table has columns for "Dimension 1 Filter", "Dimension 2 Filter" and "Business Unit Filter" which have been replaced with "Dimension 1 Totaling", "Dimension 2 Totaling" and "Business Unit Totaling". These fields have different field numbers in the Column Layout table for NAV2009.
Now, converting these values isn't too big of a deal, but I was surprised to discover that the Upgrade Toolkit apparently does not address these issues. I plan on tweaking the upgrade codeunits, but it's sort of strange (to me) that this was overlooked.
Has anyone encountered this? Or is our client's Account Schedules just a little bit more sophisticated in terms of use of these fields that it's not an issue for a large percent of the upgrades that have been done?
Thx
Ron
Ron
0
Comments
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
Son of a gun! Looks like our copy of the upgrade toolkit is W1 and not NA! I'll check it out! Thanks for pointing out the obvious!
C:\Navision\Dynamics.NAV60R2.NA.1097436.DVD\UpgradeToolKit\Local Objects\
Upgrade400SP32009SP1.NA.1.fob
Upgrade400SP32009SP1.NA.2.fob
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n