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
- 301 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
If you are struggling with R121, a tip
Miklos_Hollender
Member Posts: 1,598
Change FilterDetailedCustLedgEntry(DtldCustLedgEntry,STRSUBSTNO('%1..%2',CALCDATE('<-1D>',MaxDate),31129999D)); the -1D to +1D
I observed this bug in NAV2017 18609 (sorry forgot what CU that was, about 7 maybe)
I observed this bug in NAV2017 18609 (sorry forgot what CU that was, about 7 maybe)
0
Comments
Yes we asked Microsoft, and they give us a fix like what you mentioned.