Obsolete and duplicate actions still visible after Data upgrade from Nav 2013 R2 to Nav 2018 CU2
krishna1235
Member Posts: 4
Hi..We have a customer database which is upgraded from Nav 2013 R2 to Nav 2018 Cu2. After upgrading the database,we where still able to see some obsolete actions in Nav 2018 CU2 as well as duplicate actions for Statistics,Release etc in some page among which only one action performs operations when selected.
For Example:Credit Cards Action is present in Nav 2013 R2 which is obsolete in 2018 CU2

This happens only in the customer environment.
1)Customer environment has Nav2018 CU2 installed.
2)Same database is restored in an other server.Still the problem exists.
3)We imported all upgraded objects set in an other server on top of Cronus database.This problem doesn't occur.
However since its an upgrade customer data needs to be there.
Could you guys let us know valuable inputs.Thanks in advance
For Example:Credit Cards Action is present in Nav 2013 R2 which is obsolete in 2018 CU2

This happens only in the customer environment.
1)Customer environment has Nav2018 CU2 installed.
2)Same database is restored in an other server.Still the problem exists.
3)We imported all upgraded objects set in an other server on top of Cronus database.This problem doesn't occur.
However since its an upgrade customer data needs to be there.
Could you guys let us know valuable inputs.Thanks in advance
0
Answers
-
It looks like errors in merging. Did you do merge manualy (by comparing the text files), or did you just run the pages through some sort of tool, and put results back into the database, without validating them?Slawek Guzek - www.yitron.co.uk
Business Central, MS SQL Server, Wherescape RED;0 -
Hi Slawek_Guzek,
Thanks for your reply.
We have merged the customizations manually to Standard 2018 objects excluding obsolete actions.
However same set of objects when imported in a fresh Cronus database in different server works fine.
Not sure may be any registry kind of thing which is pointing to the earlier Nav version?
0 -
I would double check the code. Things like this one do not appear automagically out of thin air, there must be someting left - most likely in the source code.
I would also try to delete all user personalisations.
Slawek Guzek - www.yitron.co.uk
Business Central, MS SQL Server, Wherescape RED;0 -
Hi Juhl,thanks for the suggestion.
Cleaning Profile metadata table(2000000074) helped in resolving this.0
Categories
- All Categories
- 75 General
- 75 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.8K 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
- 610 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 253 Dynamics CRM
- 103 Dynamics GP
- 6 Dynamics SL
- 1.5K Other
- 991 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 28 Design Patterns (General & Best Practices)
- Architectural Patterns
- 9 Design Patterns
- 4 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1K General Chat
- 1.6K Website
- 77 Testing
- 1.2K Download section
- 23 How Tos section
- 249 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
