Introducing Acumatica Cloud ERP: 2026R2
Technical discussions focused on Web Services and APIs for developers
Recently active
I’m trying to create credit memos via REST API and to do that I need the invoice related to a certain refunded sales order so that I can apply the credit memo on it, I looked the docs but I can only see how to retrieve all invoices, I also looked up the interface and apparently there’s no mention on the sales order anyway on the invoice page, if anyone has had a similar issue please advise !!
When querying the Activity entity I am able to retrieve the RelatedEntityDescription field.However, filtering Activity by RelatedEntityDescription leads to an error as shown below.http://52.168.110.150/AcumaticaNew/entity/Default/23.200.001/Activity?$select=RelatedEntityDescription&$filter=RelatedEntityDescription+eq+%27Test+Value%27&$skip=0&$top=1000This looks like a bug from the API. Is there any solution to this? If not, is there a way to detect such fields? The swagger definition does not contain any information on such columns.{ "message": "An error has occurred.", "exceptionMessage": "Invalid column name '[Activities_CRActivity].[Source]'\r\n", "exceptionType": "System.Exception", "stackTrace": " at PX.Data.PXSqlDatabaseProvider.throwInvalidColumnName(SqlException e, IDbCommand cmd) in C:\\build\\code_repo\\NetTools\\PX.Data\\Database\\MsSql\\MsSqlDatabaseProvider.cs:line 483\r\n at PX.Data.PXSqlDatabaseProvider.<ExecuteReaderInternalAsync>d__24.
I am trying to add line items to an existing order via the API. I am able to create orders with line items via the API, but I have found that if the number of line items is too high, the process times-out/fails.So I am attempting to create the order header, then loop through the line items and add them in batches of a certain # of lines (TBD, possibly 100). My script is creating the order header no problem, but I can’t get it to add any line items. This is the error msg:Specified argument was out of the range of valid values.\r\nParameter name: Invalid uri structureThis is the URL: https://xyz.com/entity/Default/22.200.001/SalesOrder/1712261/DetailsI then modified the URL to be: https://xyz.com/entity/Default/22.200.001/SalesOrder?$expand=Details&$select=OrderType,OrderNbr,Details/OrderQty,Details/InventoryID,OrderedQty,OrderTotal I do not get an error with this 2nd URL, but it just hangs. My script hangs and I do not see activity in Acumatica. This is the request payload: {"
We’ve created a simple BLC object named SOShipmentMutex. We are editing it via a listview page with a custom DAC.When we delete a row from the Shipment Mutex grid via the UI, it deletes successfully. However, when we try to delete via the REST API, the delete is not performed. The RowDeleting event is hit when using the UI, but it is not hit via the API.We are able to successfully add a new row via the API, but delete is not fired.Can someone help us figure out why we can’t delete via the API? public class SOShipmentMutexMaint : PXGraph<SOShipmentMutexMaint> { public SelectFrom<SOShipmentMutex> .View ShipmentMutex; public PXSave<SOShipmentMutex> Save; public PXCancel<SOShipmentMutex> Cancel; protected virtual void _(Events.RowDeleting<SOShipmentMutex> e) { var row = e.Row; } } [Serializable] [PXCacheName("SOShipmentMutex")] public class SOShipmentMutex : PXBqlTable, IBqlT
HelloI followed the documentation to import Rest Schema https://help.acumatica.com/(W(29))/Help?ScreenId=ShowWiki&pageid=41be41d9-05cb-4536-a7a8-b38610760065 when I opened the solution in visual studio I see the generated models have duplicate constructor parameterany help would be appreciated
i am not able create check after upgrade acumatica in october 2024got this error{"message":"The request is invalid.","modelState":{"":["An exception occurred during input parsing"]}}please suggest me but missing my endpoint https://local//entity/Acumatica/1.0.3/Checkjson body this {"CuryOrigDocAmt":{"value":0},"CashAccount":{"value":"10060"},"Type":{"value":"Check"},"Vendor":{"value":"V001097"},"CurrencyID":{"value":"USD"},"Hold":{"value":false},"PaymentAmount":{"value":10.19},"PaymentMethod":{"value":"CREDITCARD"},"Details":[{"CashAccount":{"value":"10060"},"PostPeriod":{"value":"102024"},"BranchID":{"value":null},"InventoryID":{"value":null},"OrderQty":{"value":0},"WarehouseID":{"value":null},"AmountPaid":{"value":10.19},"Balance":{"value":10.19},"CashDiscountBalance":{"value":null},"DocType":{"value":"Bill"},"ReferenceNbr":{"value":"001301"}}],"PostPeriod":{"value":"102024"}}
We’re exploring using blanket orders with line splits based on Customer Order Nbr. values, and it appears to be working well! We ran into some odd behavior: when creating a sales order with the REST API (using the /SalesOrder endpoint), we’ve observed that the value specified in the a detail line’s CustomerOrderNbr field is apparently discarded in the generated order whenever that line’s OrderQty is greater than one. This does not seem to happen when creating orders using the web UI; only with API-created orders. Is this expected? Anyone have suggestions for how to troubleshoot? Thanks again!
Hello, Occasionally, when adding a new payment to an existing sales order with a PUT to the /Payment endpoint, the request succeeds (HTTP 200) but the response body is nearly empty. Rather than containing a Payment structure with ReferneceNbr and other fields, the server gives us a response body like this: {"id":"912d9149-55a4-4b1c-8575-73ebbfc2027c","rowNumber":1,"note":null,"custom":[]} This is problematic for our use case, because we need to store the payment’s ReferenceNbr, which is missing. Is the expected behavior? It appears to happen rarely, but I haven’t been able to determine the cause. Any recommended way to work around it? Any help is appreciated, thanks!
Hi All, We have seen discussions about how to do a bulk update by manually doing an import scenario on the Acumatica system. Is it possible to update a list of customers via a singular API call? Kind regards, Alecia
I am trying to change an Inventory ID on an existing SO Line via REST API. It seems the SOLine_InventoryID_FieldUpdated logic is interfering with this. Setup:Create an SO with an inventory item (mine is 011705) Have at least 2 warehouses available Have another inventory item (mine is 011706)In Postman, I PUT to /entity/Default/23.200.001/SalesOrder?$filter=OrderNbr eq '180214'&$expand=Details&$select=OrderNbr,Details/InventoryID,Details/WarehouseID{ "OrderType": { "value": "SO" }, "OrderNbr": { "value": "180214" }, "Details": [ { "id":"fb135987-eeea-ef11-912e-00d86198c979", "WarehouseID":{ "value":"GREEN" }, "InventoryID": { "value": "011706" }, } ]}If the new part has a default warehouse, this request will go through, but the default warehouse will be used instead of the warehouse I sent:{ "id": "68fc2b59-eeea-ef11-912e-00d86198c979", "rowNum
I’m using version 2024 R2:In Postman I’m trying to create a simple bill that looks like:URL: https://***/entity/Default/24.200.001/bill with body:{ "Type": { "value": "Bill" }, "Vendor": { "value": "MIC001" }, "VendorRef": { "value": "12FF" }, "Amount": { "value": 100.00 }}I do get a 200 OK response but the amount is zero, I’ve tried entering more fields but the results are the same. What am I doing wrong?
I am trying to filter my API response to only make a get request of records from an endpoint of records that have to be greater than a specific date. I have tried to look at the documentation but unfortunately it does not contain any page on the documentation to give knowledge or show how this is done. When I add the filter parameters I get an error message as shown below : The error message is caused when I try to invoke the following endpoint also containing the filters required : {{endpoint_url}}ProjectBudget?$filter=LastModifiedDateTime_value gt datetimeoffset'11/10/2024 12:00:00 AM'The endpoint URL is the specific company URL required to access the endpoints of the specific companyI require some assistance in being able to get past the error message so I can comfortably ingest data that is greater than a specified date.Will appreciate the assistance.
Any one has used case of integration to either Service Pro or Sales Force Field Service and Acumatica Financials.Iam working on a prospect who is seeking this.If not these two solutions any Field Service Solution Integration will help.Please email me at bala@iccg.comBala AnantharamaICCG, Inc.
I have a created a new SQL database table/DAC/Graph to collect some information that will be related to Stocked Items from an outside application. I have extended the Default web services endpoint to include this information. This all works well.My issue is that the custom DAC has a property for InventoryID but it expects an integer value which no one knows, they only know the item number. I have also added a property to the DAC for InventoryCD which is also exposed to the API, I can write to this just fine. Problem is that I can’t join this DAC to others in a GI since all the other DACs want to link on InventoryID.How do I merge these 2 into 1 so that the json payload can submit the InventoryCD and the DAC translate this and store the appropriate integer value. Here is the current DAC definition for these fields: #region InventoryID [PXDBInt()] [PXUIField(DisplayName = "Inventory ID")] public virtual int? InventoryID { get; set; } public abstract cla
Hey there everyone, Is there a way to connect a Google sheet into an Acumatica screen to get real time data?
Setup:Turn on manual numbering for Sales Quotes Make a web endpoint for Sales Quotes with OpportunityID and QuoteNbr mapped along with either of two mapped actions: PrimaryQuote or MarkAsConverted (QuoteEndpoint customization attached) Create an Opportunity Create two Quotes on that OpportunityWhen I attempt to mark the first quote as primary via POST request to /entity/Quote/0.1/SalesQuote/PrimaryQuote:{ "entity": { "OpportunityID": { "value": "261044" }, "QuoteNbr": { "value": "261044R00" } }}I get this error response:{ "message": "An error has occurred.", "exceptionMessage": "Object reference not set to an instance of an object.", "exceptionType": "System.NullReferenceException", "stackTrace": " at PX.Api.ContractBased.EntityService.Invoke(ISystemContract systemContract, String version, String name, EntityImpl entity, ActionImpl action, CbOperationContext operationContext, Boolean throwOnError)\r\n at PX.Api.Con
I am in the process of building an app to transfer reports between two Acumatica environments in batches using the Service Gate API. In reviewing the release notes for Acumatica 2024 R2, I see that the Service Gate API has been removed.Is there any documentation or resources that outline the new API that the 2024 R2 Report Designer tool uses to retrieve and save report data?
We are going live in 2025 with Acumatica. Any experience/advise how to use API to transmit our receving and shipping to our 3PL? Any suggestions who to contact at Acumatica? This is beyond me, but our 3PL is ready to go.
I want to use the Default/Shipment API to create a shipment for a sales order line that isn’t due to ship yet. In the UI, this produces a warning on the SO line saying “Scheduled Shipment Date greater than Shipment Date”. See this topic for a description of the behavior:When this request is sent via API instead, the warning prevents the Shipment from being created. Is there a way to overcome this warning and save the Shipment anyway like you can in the UI?
Looking for some assistance in the correct API method to create a POST for a Production Order Move Entry.
Our organization just upgraded to 24R2 and we are seeing new functionality that did not exist in the prior version.We have a shipment with a single line item, but two packages. When we pack into the Contents, the package that we specify isn’t being used. It seems like it is adding to the package with the highest PackageLineNbr.For example, we have the following: { "id": "74db342b-bf4e-ef11-93aa-00155d1eec41", "rowNumber": 1, "note": { "value": "" }, "Packages": [ { "id": "262d42ac-c04e-ef11-93aa-00155d1eec41", "rowNumber": 1, "note": { "value": "" }, "Contents": [], "LineNbr": { "value": 1 }, "custom": {}, "_links": { "files:put": "/AcumaticaERP/entity/Packing/22.200.001/files/PX.Objects.SO.SOShipmentEntry/Packages/262d42ac-c04e-ef11-93aa-00155d1eec41/{filename}" } }, { "id": "7
Hi folks, I’ve been trying to solve an issue where creating sales order via the REST API can be very slow. To diagnose this issue, I enabled the request profiler and used it observe that--in addition to very large SQL counts and CPU time--the slow requests are generating exactly three exceptions per detail line: two System.InvalidCastExceptions and one PX.Objects.IN.PXUnitConversionException. Not exactly a smoking gun, but it does seem suspect to me (I don’t think we should be generating these exceptions, no?). Perhaps some data was stored in the wrong format (i.e. a string being sent where an integer is expected)? Drilling down into the exception details, it looks like the source of some exceptions may be from PX.Objects.IN.PXQuantityAttribute.CalcBaseQty; but I’m not sure where to go from here. Is there a way I can determine exactly which attributes are being set? Maybe that will help me locate the offending data format mismatch. Failing that, anyone have tips for tracking down the c
Hi Team, We are working with 24R2 (Build version) and created a custom processing screen to create Sales Order but during processing we are getting an error like: 'Another process has updated the 'SOContact' record. Your changes will be lost'. But the same is working in previous build (Build version) On further verification we identified the issue occurs while updating Sales Order Contact and on executing Save action getting another process error, without this code block order created successfully. Please find the below sample code for your verification and review: public static void SetBillingContact(SOOrderEntry graph, ItemResult OrderDetails) { graph.Billing_Contact.Current = (SOBillingContact)graph.Billing_Contact.Select(); if (graph.Billing_Contact.Current != null && OrderDetails != null && OrderDetails.BillingAddress != null) { graph.Billing_Contact.Current.OverrideContact = true; graph.Billing_
Hey everyone. We have done a customisation where we extended the Opening Balances to the Customer screen. Here are the fields in DAC: public class MAKLCustomerBalanceSummaryExt : PXCacheExtension<CustomerMaint.CustomerBalanceSummary> { #region UsrMAKLCurrentBalance [PXBaseCury(null, typeof(Customer.baseCuryID))] [CurySymbol(null, typeof(Customer.baseCuryID), null, null)] [PXUIField(DisplayName = "Current Balance", Visible = true, Enabled = false)] public virtual decimal? UsrMAKLCurrentBalance { get; set; } public abstract class usrMAKLCurrentBalance : BqlType<IBqlDecimal, decimal>.Field<usrMAKLCurrentBalance> { } #endregion }We have then extended this field to the Web Service Endpoint, but it returns 0 every time even though the customer has a balance.I have then added the RowSelected event handler and populated the field in there as well, but to no avail. How can I get this field to display in the Web Service?
Hello, I’m attempting to create a Sales Order via the REST API and I’m running into an error I don’t understand when applying a discount. My DiscountDetails JSON payload looks like this: "DiscountDetails": [ { "Description": { "value": "Coupon Discount" }, "DiscountCode": { "value": "COUPON" }, "DiscountPercent": { "value": 15 }, "DiscountAmount": { "value": 0.6 }, "ManualDiscount": { "value": true }, "SequenceID": { "value": "TATER15" }, "Type": { "value": "Document" } } ]The error I’m receiving is “’Type’ cannot be empty”, but I am providing a “Type”, so I don’t really understand what’s wrong. There are no other errors. The error only seems to occur when using the REST API; I have been able to successfully apply the
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.