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
- 262 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 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
Only Recording one Infocode on a Transaction in LS Retail
Calculator-01
Member Posts: 8
I have an Infocode attached to certain items to collect the Salesperson details for these transactions, but it doesn't always record and I have just discovered that when they select the item - it is correctly requesting the salesperson information (first), but if staff then select the Pricechange button at the POS to change the price, the system is then only recording the Pricechange infocode information and the Salesperson infocode details are not being retained and recorded against the transaction.
How can I force the system to retain and record both sets of infocode information? One is compulsory - attached to the item, but the other is discretionary attached to a POS button. Even it there was some way to prioritise, the Salesperson information is more important - but ideally we want to capture both.
Thanks,
How can I force the system to retain and record both sets of infocode information? One is compulsory - attached to the item, but the other is discretionary attached to a POS button. Even it there was some way to prioritise, the Salesperson information is more important - but ideally we want to capture both.
Thanks,
0