Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.6K 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
- 295 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
LS Retail- Waiting ICT Requests clarification.
Deep
Member Posts: 569
Hello all.
This is regarding a clarification for "Retail ICT Process" in LS Retail.
The default code processes the entire waiting ICT requests in one go as a batch. This is troublesome, as if any one ICT record has got any error, the entire waiting ICT records got stuck, and further gets piled and piled up, which takes hours to get processed after fixing the error, which in turn, restricts the other users to post anything.
I am unable to understand the logic behind the same as to why it has been coded as a batch process.
Everytime, we need to filter and exclude the erring document no. in the code and process the remaining records.
Has anyone worked towards tweaking the code locationwise, or ICT number wise, or else?
If so, please share how it is done.
This is regarding a clarification for "Retail ICT Process" in LS Retail.
The default code processes the entire waiting ICT requests in one go as a batch. This is troublesome, as if any one ICT record has got any error, the entire waiting ICT records got stuck, and further gets piled and piled up, which takes hours to get processed after fixing the error, which in turn, restricts the other users to post anything.
I am unable to understand the logic behind the same as to why it has been coded as a batch process.
Everytime, we need to filter and exclude the erring document no. in the code and process the remaining records.
Has anyone worked towards tweaking the code locationwise, or ICT number wise, or else?
If so, please share how it is done.
Regards,
Deep
India
Deep
India
0