Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 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
Options
Copy Document - jumps to another record when different sort order is defined
Jut
Member Posts: 72
Hello everyone,
has anyone ever experienced an issue when using the copy document function with sales or purchase documents on the card while having defined a sort order the sales/purchase list page that could be affected by the copy document?
For example I may change the sort order on the sales list to bill-to customer name. Now I create a new sales document form the list - new; I only populate the number field; use copy document (include header). After running the copy document report, instead of showing the record that I was working on, a totally unrelated record will show. It seems to be related to the fact that the copy document function in this case changed the bill-to customer name while that field was used in the list as the sort order. I was able to replicate that problem in NAV 2015 Cronus and also in NAV 2016. Is this a known issue?
The manual workaround would be to store the document no. prior to calling the copy document and to get the right record afterwards. However I would like to avoid such a "dirty" solution.
Best regards
Jut
has anyone ever experienced an issue when using the copy document function with sales or purchase documents on the card while having defined a sort order the sales/purchase list page that could be affected by the copy document?
For example I may change the sort order on the sales list to bill-to customer name. Now I create a new sales document form the list - new; I only populate the number field; use copy document (include header). After running the copy document report, instead of showing the record that I was working on, a totally unrelated record will show. It seems to be related to the fact that the copy document function in this case changed the bill-to customer name while that field was used in the list as the sort order. I was able to replicate that problem in NAV 2015 Cronus and also in NAV 2016. Is this a known issue?
The manual workaround would be to store the document no. prior to calling the copy document and to get the right record afterwards. However I would like to avoid such a "dirty" solution.
Best regards
Jut
0