Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>You're picking the wrong column and/or searching for a field value rather than the text or itemfield:name instead. I'll edit my answer and add more as I find it. This is from my ns experiences though with suitescript.</p> <p><strong>using the referencedocs I see: Posting TRX summary field:</strong></p> <p><code>&lt;complexType name="PostingTransactionSummaryField"&gt; &lt;sequence&gt; &lt;element name="period" type="xsd:boolean" minOccurs="0" maxOccurs="1"/&gt; &lt;element name="account" type="xsd:boolean" minOccurs="0" maxOccurs="1"/&gt; &lt;element name="parentItem" type="xsd:boolean" minOccurs="0" maxOccurs="1"/&gt; &lt;element name="item" type="xsd:boolean" minOccurs="0" maxOccurs="1"/&gt; &lt;element name="entity" type="xsd:boolean" minOccurs="0" maxOccurs="1"/&gt; &lt;element name="department" type="xsd:boolean" minOccurs="0" maxOccurs="1"/&gt; &lt;element name="class" type="xsd:boolean" minOccurs="0" maxOccurs="1"/&gt; &lt;element name="location" type="xsd:boolean" minOccurs="0" maxOccurs="1"/&gt; &lt;element name="subsidiary" type="xsd:boolean" minOccurs="0" maxOccurs="1"/&gt; &lt;/sequence&gt; &lt;/complexType&gt; </code></p> <p>or also <strong>using the referencedocs I see: GetPostingTransactionSummaryResult:</strong></p> <p><code>&lt;complexType name="GetPostingTransactionSummaryResult"&gt; &lt;sequence&gt; &lt;element ref="platformCore:status" minOccurs="1" maxOccurs="1"/&gt; &lt;element name="totalRecords" type="xsd:int" minOccurs="0"/&gt; &lt;element name="pageSize" type="xsd:int" minOccurs="0"/&gt; &lt;element name="totalPages" type="xsd:int" minOccurs="0"/&gt; &lt;element name="pageIndex" type="xsd:int" minOccurs="0"/&gt; &lt;element name="postingTransactionSummaryList" type="platformCore:PostingTransactionSummaryList" minOccurs="0" maxOccurs="1"/&gt; &lt;/sequence&gt; &lt;/complexType&gt; </code></p> <p>On a seperate unrelated topic, I found this:</p> <p> Specifying Web Services Context<br> To cause a form to behave differently in Web Services versus the UI, you can do one of the following:<br> <br> Write context-specific SuiteScript code and use the nlapiGetContext function to branch the code<br> <br> Disable SuiteScript in Web services<br><br> However, both Client and Server SuiteScripts are written to enforce customized business rules that may need to be enforced regardless of the mechanism by which a record is created or updated within NetSuite. This is particularly true for customers who deploy a SuiteCloud partner application and want to be sure their business rules are still respected. Since Client SuiteScript often has browser-specific behavior that requires user action and cannot automatically run during a Web Services call, NetSuite recommends that you disable Client SuiteScript and deploy Server SuiteScript for those business conditions that need to be enforced in all cases.<br><br> To specify that Server SuiteScript should never execute during a Web services call, enable the Disable Server-side Scripting preference on the Web Services Preference page at Setup &gt; Integration &gt; Web Services.<br><br> Important:<br> Only enable this preference when data submitted via Web services does NOT need to adhere to custom business logic and workflows that may be executed via Server SuiteScript.<br> <br> <br></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload