• How to figure out errors ViewExceptions .NET API

    I'm trying to insert an order using the API - and I'm getting back an error that just says 6666 How can I find what this means, and in general, is there a way to get the COM exceptions and error codes? I know how to get session.Errors, but that is empty…
  • Payables Workflow with PJC Retainage Integration

    Does anyone knows of a web-based Payables Workflow that is able to process and approve job-related PJC invoices with retainage? Both Pacific Technologies and Norming's solutions do not handle PJC retainage. Thanks.
  • Error adding an item to a sales order

    I have created a C# web service suing the Sage 300 objects, and all is working well except when I try to add another line to an existing order I get: "Order Detail. Attempt to modify a different record than was retrieved." This occurs on the code…
  • Event Viewer Exception from Accpac internal dlls

    I am using the Accpac.Advantage dlls to communicate from a third party .net app into Sage 300. The processes we are doing are simply to open a connection and then return various pieces of information from view calls (I use the CS query view through an…
  • Issue sending AP/AR Adjustments using SAGE300WebAPI calls ARReceiptAndAdjustmentBatches/APPaymentAndAdjustmentBatches

    I'm sending adjustments to Sage 300 ERP Server for 'posted' invoices and I know that the transaction are successful because the webapi call returns a reponse code is 201 and the response message contains the information I sent but when I open the adjustment…
  • Website integration to Sage 300 ERP

    How can we restrict or reserve one LANPAK from one IP address. We have a web store where we selling items . a customer purchases item on web store and it goes and creates an order and an invoice in sage.. The service is configured to use a sage LANPAK…
  • Connectivity problem with Excel

    Hi, MS released an update this past weekend and it seems to have affected connections to excel. I was wondering if anybody else has experienced this. Before the MS updates our macros were programmed to connect to Excel with Microsoft.ACE.OLEDB.12.0…