Hi, This is in continuation with the previous post about credit lines checking. If multiple sales orders are selected for update or the select feature is used during on the salesEditLinesForm the Sales order table can be blocked for a prolonged time causing multiple users to experience long delays in creating and updating sales orders. The salesFormLetterClass chooseLines method places the salesTable table and salesLine table in transaction state as it populates the parm table with the selected records. If a user is selecting a large amount of records or the selection criteria is complex this causes the long block on theses two tables and can block work with sales orders for every other user in the system. The block is possibly due to the credit check process which also wants to traverse the salesTable and salesLine tables while checking for open sales order totals during order creation and update. Fix: Modify salesFormLetter::chooseLines, comment out line 20 and line 53 in the unmodified sys layer code. Are these problems authenticated by ms and is it fixed in sp3 or sp4? Please comment. Have a good day! Thanks & Regards, Dilip
Hi, In SP3/SP4 : in first place, they are object methods, not class methods. They are not commented as you suggest, but in CheckSales there is a comment: … ttsbegin; // In transactions in order to get enforce selection of eg. CustTable … Regards, Ciprian
Ciprian, I’m not sure about SP3/SP4, but in SP1 i think there is no need of tts because there’s no insert/update/delete happening, its just readonly then why tts?? if there are multiple users, say in our case we have 115 concurrent users, which may lead to locks/blocking. Thanks and Regards, Dilip