Jump to content

Ming Han Chung

Members
  • Posts

    5
  • Joined

  • Last visited

Reputation

0 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The question I have (as i've verified sometimes we just get this 502) is that since it doesn't return a success or fail -> we had assumed fail -> the system retried and doubled up the invoices as the sage side did process it. Is there anyway to make sure if it gets retried that it doesn't double up a data send?
  2. Im having a problem where I can use CUSTOMER.CUSTTYPE in my readbyquery . In the new Query it works but readby it doesn't. Is there anyway to access this field in the query? ?xml version="1.0" encoding="UTF-8"?> <request> <control> <senderid>REDACTED</senderid> <password>REDACTED</password> <controlid>1715270549</controlid> <uniqueid>false</uniqueid> <dtdversion>3.0</dtdversion> <includewhitespace>false</includewhitespace> </control> <operation transaction="false"> <authentication> <login> <userid>REDACTED</userid> <companyid>REDACTED</companyid> <password>REDACTED</password> </login> </authentication> <content> <function controlid="a0736698-dff3-495d-915a-c5fbb18d2de5"> <readByQuery> <object>ARINVOICE</object> <query>WHENCREATED <= '01/30/2024' and TOTALDUE != '0.00' and CUSTTYPE = CLAIMS </query> <fields>RECORDID,CUSTOMERID,CUSTOMERNAME,CUSTOMER.CUSTOMERID,CUSTOMER.STATUS,TOTALPAID,TOTALDUE,TRX_TOTALDUE,WHENCREATED,CUSTOMER.CUSTTYPE,WHENDUE,DOCNUMBER</fields> <pagesize>500</pagesize> <returnFormat>xml</returnFormat> </readByQuery> </function> </content> </operation> </request> This is the xml. when doing customer.custonerid it works fine.
  3. We're having an issue using the Sage SDK PHP library in which at times we get a Bad Gateway response. This seemed to trigger a retry and ended up doubling up the transaction as it actually went through on the sage side eventhough we got the Bad Gateway on the response. Are there anyways that we can prevent this double up? <html> <head><title>502 Bad Gateway</title></head> <body> <center><h1>502 Bad Gateway</h1></center> <hr><center>cloudflare</center> </body> </html>
  4. <html> <head><title>502 Bad Gateway</title></head> <body> <center><h1>502 Bad Gateway</h1></center> <hr><center>cloudflare</center> </body> </html>
  5. We're having an issue using the Sage SDK PHP library in which at times we get a Bad Gateway response. This seemed to trigger a retry and ended up doubling up the transaction as it actually went through on the sage side eventhough we got the Bad Gateway on the response. Are there anyways that we can prevent this double up?
×
×
  • Create New...