I recently downloaded a copy of Acumatica’s Test SDK and began running through the pdf class. After writing the first classes test, I came across a maddening FileLoadException involving TestApiCore.dll
This is due to Windows determining the location of the .dll coming from a internet source, and attempting to sandbox it into running with a limited set of permissions. To temporarily fix it you can right click on the dll and select Unblock under the General tab, but this is inefficient because there are several files that are flagged in this way.
Instead, user the following Powershell command: dir C:\*YourTestSDKDir*\TestProject\*.* | Unblock-File -confirm
Be sure to use the path pointing to the downloaded files, not to your projects \bin\ folder, because Visual Studio copies several .dlls from the TestProject folder of the TestSDK directory, and the files that overwrite s will continue to have this flag applied
Product : Sage MAS500
Description : Custom EDI integration for orders, shipments and stock status reports
Project Type : Custom integration
Customized : None
New Screens : None
Versions : 6.3 and later
The requirements for this customization was to enable the transmission of EDI documents in .csv format between an originating organization and a MAS500 user who was going to do shipping fulfillment on behalf of them. Documents were transmitted via FTP between the two sites. On the MAS500 side the EDI documents were imported into MAS500 using a custom EDI connector written in VB.net which moved data from the FTP site .csv files into custom SQL staging tables in MAS500. The standard MAS APIs were then used to create sales orders, pick lists and then shipments. After the shipment were completed a shipment confirmation was then transmitted to the origination company.
This document was intended for quick reference with regards to the most common fields you want to access from the web endpoint. For more in-depth help, take a look at the section titled “Working with the Contract-Based REST API” located here: API HELP
Authentication
Login
Type: POST
Format: JSON
URL: <URL>/entity/auth/login
BODY:
Additionally, fields ‘ShippingContact’ and ‘BillingContact’ can be specified separately from ‘MainContact’ shown above. If these are not specified then a new PurchaseOrder will use the MainContact as both.
Retrieving Customer data
Type: GET
Format: JSON
URL: <URL>/entity/Default/17.200.001/Customer
Use query parameter $filter: To specify filtering conditions
Use query parameter $expand: To expand specific detail entities
Otherwise all current customer data will be sent
Update Existing Customer
Type: PUT
Format: JSON
URL: <URL>/entity/Default/17.200.001/Customer
Use parameter $filter: To specify filtering conditions on key fields that identify the record to be updated
Key Field: CustomerID (string(10))
Example: URL: <URL>/entity/Default/17.200.001/Customer?$filter=CustomerID eq ‘ABARTENDE’
Body: { "CustomerName": {"value": "Stuffffff"} }
This will update customer ABARTENDE’s name to ‘Stuffff’
This will create a new sales order for the CustomerID, at an alternate Location ID (applies to ‘Ship To Address’, BillToAddress will always default to the default ‘BillToAddress’ specified in the Customer Record (see this document’s relevant section under Customers):
This will create a new sales order for the CustomerID, using a ship to address that is not currently saved as a location under the CustomerID record (the same can be done with ‘BillToAddress’):
Type: PUT Format: JSON URL: <URL>/entity/Default/17.200.001/SalesOrder
Use the same format as “Add a Sales Order”, however you must
specify existing records using query parameter $filter, or else a new record
will be added
Example: PUT to <URL>/entity/Default/17.200.001/SalesOrder?$filter=OrderNbr eq ‘SO004573’
Body: { "CustomerID" : {value : "ABCVENTURE"} }
This sets Sales order # ‘SO004573’ value of CustomerID to ABCVENTUREKey Field: OrderNbr (string(10)
Status of a Sales Order
Date received, date entered into the system and current status Open, closed, backordered, shipped If shipped – shipping information
Cancel a Sales Order
Type: PUT Format: JSON URL: <URL>/entity/Default/17.200.001/SalesOrder/CancelSalesOrder
You must create a new request in this format for every
SalesOrder you want to cancel
Further Documentation
Download the Acumatica provided swagger.json file for a full openAPI 2.0 documentation of the existing web endpoint here:
You can then use an Open Api GUI of choice to navigate it
Send a GET Request to any Endpoint with the addition of $adHocSchema to get a list of fields associated with it Example:<URL>/entity/Default/17.200.001/SalesOrder/$adHocSchema