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
Remnants of List Page shown on Card Page
lvanvugt
Member Posts: 774
Recently we did run into the following issue on some pages. Have a look at the screen shot. Hopefully you can see it clear enough as we experienced different resulst on different monitor.
So what's the case?
After opening a list page we open a card/document page and parts of the card/document page still shows 'remnants' of the list page (like in the screen shot).
It first was noticed by a colleague (A) that was running a newer NAV 2009 R2 platform build (32572) than the person (B) who had build the database (i.e. imported and compiled all the objects). The latter was using the RTM buid 32012.
Reverting colleague A to build 32012 did solve his issue. But some what later another colleague (C) encuntered a similar issue on build 32012 (from this we took the screen shot).
Anyone of one had a similar experience?
So what's the case?
After opening a list page we open a card/document page and parts of the card/document page still shows 'remnants' of the list page (like in the screen shot).
It first was noticed by a colleague (A) that was running a newer NAV 2009 R2 platform build (32572) than the person (B) who had build the database (i.e. imported and compiled all the objects). The latter was using the RTM buid 32012.
Reverting colleague A to build 32012 did solve his issue. But some what later another colleague (C) encuntered a similar issue on build 32012 (from this we took the screen shot).
Anyone of one had a similar experience?
0