Qxtend 1.6
>> HPUX (rx4640. 24 gig RAM, 8 Cores).
>> Progress 10.1C
>>
>>
>> <SOAP-ENV:Envelope
>> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
>>    <SOAP-ENV:Header>
>>        <ns0:To
>> xmlns:ns0="urn:services-qad-com:eb">http://www.w3.org/2005/08/addressing">urn:services-qad-com:eb
>> 21_live_receiver</ns0:To>
>>    </SOAP-ENV:Header>
>>    <SOAP-ENV:Body>
>>        <maintainItemMaster xmlns="urn:schemas-qad-com:xml-services">
>>            <urn:dsSessionContext
>> xmlns:urn="urn:schemas-qad-com:xml-services:common">
>>                <urn:ttContext>
>>                    <urn:propertyQualifier>QAD</urn:propertyQualifier>
>>                    <urn:propertyName>version</urn:propertyName>
>>                    <urn:propertyValue>eB2_2</urn:propertyValue>
>>                </urn:ttContext>
>>                <urn:ttContext>
>>                    <urn:propertyQualifier>QAD</urn:propertyQualifier>
>>                    <urn:propertyName>domain</urn:propertyName>
>>                    <urn:propertyValue>NZ</urn:propertyValue>
>>                </urn:ttContext>
>>            </urn:dsSessionContext>
>>            <dsItemMaster>
>>                <itemMaster>
>>                    <operation>U</operation>
>>                    <ptPart>1063758</ptPart>
>>                    <ptPrice>999.99</ptPrice>
>>                </itemMaster>
>>            </dsItemMaster>
>>        </maintainItemMaster>
>>    </SOAP-ENV:Body>
>> </SOAP-ENV:Envelope>
>>
>> Craig Love
>> Progress Programmer
>>
>> Aperio Group
>> t +61 2 9794 8659 | e [email protected] | f
>>
>> a 149 Orchard Rd, Chester Hill NSW 2162 Australia | w aperiogroup.com.au

Hi Michael,

further to Garys reply, for the data you are sending, definitely use the Item Cost Maintenance function instead of Item Master Maintenance. When using the UI API, every field that QXtend has to traverse costs around 30ms give or take. This is a factor of the TCP lag on a telnet screen, since this is how the UI API communicates with the QXtend Java application. So reducing the number of fields that have to be traversed will speed up processing by a large amount. This is also true where you don't want to include nodes in the Qdoc that do not add information, since QXtend will do the equivalent of F1 if there are no more fields to process. For example, in your case, if you were calling Item Master Maintenance, and you only wanted to update the Item Description field, the Qdoc would be processed much faster, because after it reached the Item Description field it would skip the remaining fields by doing an F1 until it reached the end.

This particular Qdoc also has an equivalent SI API if you have 2009SE and above. The structure of the Qdoc is exactly the same, but it has a different version number. You would find this one would take anywhere between 150ms to 1sec, depending on whether code in the backend was previously executed (since OOABL code instantiates much faster 2nd time it is run).

I will almost always disagree with Gary about the scopeTransaction setting being set to true, except in some cases. Functions with header-child relationships you MAY want to have it set so that there is full rollback on an error in the child record. But for Item Master Maintenance you should have it set to true, because you will notice when navigating through the normal UI that an error in the Item Planning frame will not rollback the data entered in the first frame, as it has been coded to work in separate transactions. This is not the functionality you would expect from a single-level API. But be aware that having scopeTransaction set to true on any Qdoc will cause the application to behave differently than it was written. This can cause performance and locking problems for all other users in the system.

Best regards

Evan