Jump to content

Search the Community

Showing results for tags 'web api'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Welcome
    • General
    • Feature Requests
    • Content Requests
    • Ideas Exchange
  • Products
    • Sage Business Cloud Accounting
    • Sage X3
  • Services
    • Banking Service
  • SAGE X3 Developers's Topics

Categories

  • What's New?
  • Innovate and Co-create
  • Scale and Grow
  • Supporting You

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me


Job Title

Found 2 results

  1. When launching a request via REST web service with the ASYRRESTCLI.EXEC_REST_WS instruction against a third party Endpoint, I need to control a certain time in which, if the Endpoint does not respond, to exit the call and return error by TimeOut. Currently, if the Endpoint is stopped, the process runs and I don't know for how long, because when it took more than 15 minutes I stopped it. Looking for information, I have tried putting this in the header parameters: # Add a parameter HCOD(1) = 'xxx-api-key'. HVAL(1) = '"'+PCONEXPWD+'"'' HCOD(2) = 'Content-Type' HVAL(2) = '"application/json"'' HCOD(3) = 'Keep-Alive' HVAL(3) = '"timeout=1"'' But it still does not stop at one minute Thank you very much, in advance, for the answers.
  2. We're intermittently getting a crash while sending a POST command through the Web API (Sage 300 2020 PU7) when trying to create new OE Orders. Based on the Event Viewer, our Sage 300 Application Pool crashes and there appears to be a disconnect from the SQL Native Client. We have turned on Microsoft debugging with DEBUGDIAG for crash dump criteria which returned no results, ODBC Admin trace, all inetpub logs show successful postings (201) and no failures, increased logging in IIS and the failed request tracing gives no results. When there's a failed transaction, Just-in-time debugging screen pops up on the server. Subsequent POST attempts can be successful immediately or maybe after a few attempts. When we change the payload to override the Tax Group to bypass "AVATAX", we have yet to see a crash after about 80 orders. We now believe it is an Avalara issue using the Web API. Does anyone know about an DBSPY equivalent for the Web API so we can track down the exact issue? Has anyone ran into the same or similar issue?
×
×
  • Create New...