Develop Customizations

Hi everyone,I’m trying to customize the Acumatica UI by adding a custom icon to the top header area (the element with id navBarMaster). My goal:Add a new icon/button in the header (similar to notification/user icons) When clicking the icon → trigger an action (e.g., show a dropdown or popup list of items)What I’ve explored so far:Injecting JavaScript via MasterPages (e.g., FormDetail.master) → works but not safe for deployment Looking for a solution using Customization Project (C# / Graph / PXPage) instead of modifying core filesQuestions:Is there a supported way to extend the header (navBarMaster) via Customization Project? Can this be done purely with C# (Graph/Page customization), or is JavaScript

We are working on a custom form/workflow to print the Pick List (SO642000) and Packing Slip (SO644000) via a processing form to DeviceHub. The problem we are having is that for some reason, devicehub will print these out of order.If I don’t print to devicehub it is combining the reports and will show them in a single window. Both are set to use PDF. When this goes to devicehub it prints each report as a separate job and then often they are no longer in order.Is there a way to 1) get this combined report to print as a single job on devicehub or 2) have better control of what order devicehub is printing in? Obviously I’d love both to be true, but will settle for one.The code looks like this:                    // Define report parameters (keys must match report parameters in RPX)                    Dictionary<string, string> parameters = new Dictionary<string, string>();                    parameters["ShipmentNbr"]

I have received some requirements from users. They want to display a QR code payment image that is generated as a base64-encoded PNG from an external API.I need to show this base64 image on an Acumatica form. Once the user scans the QR code and completes the payment, we will receive a response from the API and continue with the next process.Please guide me on how to display a dynamic base64 image in Acumatica 2025 R2, for both the Classic UI and the Modern UI.

I want to add Middle Name (MidName) field to the common html for the common Contacts thingy.This is my code.  It publishes without any errors, but the field does not show up.This is the first time trying to modify a “common” view.  I’m sure something is wrong but I don’t know what.I was not able to find anything on the web for this specific need. //THIS IS THE TSimport { PXFieldState,} from "client-controls";import { Contact } from "src/screens/common/form-contact-person/form-contact-person";export interface ExtendedContact extends Contact { }export class ExtendedContact { MidName: PXFieldState;}//this is the HTML<template> <qp-include url="src/screens/common/form-contact-person/form-contact-person"> <field append="#{{fs-id}}" name="MidName" config-allow-edit.bind="true"></field> </qp-include></templa

Hi Everyone,We have customized the mobile app for the Scan and Transfer screen. Currently, the Save action is displayed; however, our requirement is to show the Release action instead, once all the steps are completed.Could you please guide us on how to achieve this?  

Similar to an older post, I ran into the same situation but have some more context and a more specific question. The ‘Invoice Payment Link Update’ is a straightforward quality of life process that triggers the payment link of an invoice to update when an invoice becomes ready for synchronization; very nice - clicks saved. However, we are seeing this out-of-the-box Business Event fail regularly.Digging into the notification itself in the Process Push Notifications screen, I noticed that every failed push notification JSON looks roughly like this:{Inserted values: {{INV: 000010}{needs_sync: true}, {INV: 000011}{needs_sync: true}},Deleted values: {{INV: 000010}{needs_sync: false}, {INV: 000011}{needs_sync: false

 I needed to restrict the SalesPersonID selection in ARTran so that users can only choose salespersons assigned to their organization, based on a custom field (UsrInternalCompanyID) added to the SalesPerson DAC. To achieve this, I attempted to override the selector using a CacheAttached event with a custom PXSelector that joins the Branch table and filters records according to the current user’s branch/organization. While this approach successfully limited the list of salespersons shown in the UI, it resulted in an issue where the selected value was cleared upon saving the document.Salesperson DAC extention public class SalesPersonAccessRestExtP : PXCacheExtension<PX.Objects.AR.SalesPerson> { #region UsrInternalCompanyID [PXDBInt] [PXUIField(DisplayName = "Company ID")] [PXSelector(typeof(Organizatio

​Hello everyone,I’m having the following problem: I’m trying to convert a Classic UI screen into Modern UI and 3 of the buttons are not getting hidden for some reason but there’s a try that my colleague tried doing a while ago and the buttons are working as expected there but I’m unable to recreate them for some reason using the automatically converted screen into Modern UI. The buttons I’m having that issue are “Confirm, Generate and Change Order” also another thing I noticed is that we cant reuse the Transactions variable because if we do, the Subcontracts grid is not being automatically loaded on page refresh or load.The version of Acumatica I’m working with is 2025 R2. Here’s the automatically generated source code: I’ll have to paste the source code into pastebin since the source code is a bit too long and the post cannot be created

Hello there,We can add side panels to Entry screens now, and that’s awesome!  However, I can’t figure out a way to add a side panel, that would be filtered according to the selection on the SO Line.  I have created a couple GIs, added them onto a Dashboard that uses InventoryCD as a parameter.  Now, I would like to be able to add this Dashboard as a side panel to Sales Orders screen, and filter data based on what line item is selected on the sales order.Any ideas?  Thank you!

I have a custom field in the header of a screen.  I cannot find a way to add the hyperlink button to the field.This was addressed for a grid field here:I’ve added the [PXDBWeblink] to the DAC field, but that does not make the link button show.I think I might have to modify the TS file, but I cannot adapt the code from the above topic.export class CROpportunityHeader_Combined_generated {    UsrURL: PXFieldState; Any help would be super appreciated.  

I’d like to get a feedback on my Open source project of performance comparison of three databases: MS SQL, MySQL and PostgreSQL for 26 R1 preview. I’d like to hear how deep is my analysis, what else can be added or removed? And of course if that is worthy of attention. 

When setting the OrderQty field to 0 on the SO Line, a popup is triggered as expected. However, once the popup appears, the Details tab disappears immediately. After closing the popup by clicking OK, the Details tab becomes visible again. <template>  <qp-tab id="tab-Dsco-SO301000" caption="Dsco Info" after="#tab-Addresses">        <qp-template id="form-Dsco-SO301000" name="17-17-14">            <div id="divColumnAB-Dsco-SO301000" slot="A">                <qp-fieldset id="fsColumnA-Dsco" view.bind="CurrentDocument" caption="Dsco Information" wg-container="CurrentDocument_Dsco">                    <field name="UsrBZStoreCode"></field>                    <field name="UsrBZDscoPuNumber"></field>                    <field name="UsrBZDscoOrderCancelAfterDate"></field>                    <

I have the following issue with Modern UI:In one package I create a column.In another package I add a field / logic that depends on that column.Everything works fine when I develop Modern UI in Visual Studio — after build, all changes are visible on the screen and work correctly.But when I add Modern UI files into packages and publish them in another instance of Acumatica ERP, I get errors (field/column not found).I understand that this approach is not recommended, but I still need to make it work.Is there any way to handle this scenario? [2026-03-26 14:54:27.199] npm run build failed with output:> screen@0.1.0 build> cross-env node --max_old_space_size=6144 --optimize_for_size --stack_size=6144 --trace-warnings ./node_modules/webpack/bin/webpack -- --env production --env tenant=Company screenIds=AR301000,AR303000,BZ101001,BZ101007,BZ201520,BZ401005,BZ401022,BZ501011,BZ501012,BZ501013,BZ501014,BZ501015,BZ501017,BZ501041,

I am creating a purchase order approval workflow for a client. They previously used Purchase Requests with an approval workflow and are wanting to replace this with Purchase Order approvals.Their Request Approval Workflow conditions are based off Department and $ amount.  Currently it is not possible to setup Purchase Order workflows in the same way, as the Department Entity is not available.Can we add the department field to the Purchase Order header and add the department entity to the Purchase Order workflow?Additionally we would probably get the Purchase Order department field to default to the PO Owner (employee’s) department but they could select any department, as it

Hello! The below code is running great in 25R1. It tells the system to look at the UsrQUOTECOST field on SOLine when create a PO through Create Purchase Order. If UsrQUOTECOST is empty, then system should behave the same, if user inputs value in UsrQUOTECOST, then when PO is created, the unit cost field should pull from this udf.The issue I am running into is that when I try to publish this code in a 25R2 tenant, I get the following error: The PX.Objects.PO.POLine FindOrCreatePOLine(PX.Objects.PO.POOrderEntry, PX.Objects.CS.DocumentList`1[PX.Objects.PO.POLine], System.String, PX.Objects.PO.POFixedDemand, SOLineSplit3, FindOrCreatePOLineDelegate) method in the PX.Objects.PO.POCreate_Extension graph extension is marked as [PXOverride], but no original method with this name has been found in PXGraph.And per the 25R2 developer release notes, looks like the FindOrCreatePOLine method was removed. Any ideas around what the alternative method would be

Hi community,I am trying to apply custom styling (background-color and font-weight) to a custom action button on the Shipments (SO302000) screen header in the Modern UI.Here is my code for the Classic UI:  #region Actions public PXAction<SOShipment> bZProcessShipment; [PXButton(Category = "Processing")] [PXUIField(DisplayName = "Process Shipment", MapEnableRights = PXCacheRights.Select, MapViewRights = PXCacheRights.Select)] // Upgraded to Acumatica 2025 R2 by Biz_Vahe protected IEnumerable BZProcessShipment(PXAdapter adapter) { string shipmentNbr = Base.Document.Current?.ShipmentNbr; if (string.IsNullOrEmpty(shipmentNbr)) return adapter.Get(); var adapterCopy = adapter; Base.Save.Press(); PXLongO

Hi Team,We have modified the Postal Code field using CacheAttached to make it a selector, and it is working fine in Classic UI.However, in Modern UI it is still behaving like a normal text field.In the TS file, I added:@controlConfig({ allowEdit: true })PostalCode: PXFieldState<PXFieldOptions.CommitChanges>;But the selector is not getting applied.Could someone help how to convert Modern UI to support selector fields?Classic UI Thanks In advance!

In my code below, the commented out loggedUserRow line uses an obsolete method.  I tried to implement the ICurrentUserInformationProvider to get the User ID.  When the code runs, the _currentUserInformationProvider variable is null.  I’m not sure what I need to do to instantiate the variable.  This is probably a c# thing.  I tried a bunch of things not shown here, but I couldn’t figure out how to implement that interface.   public ICurrentUserInformationProvider _currentUserInformationProvider { get; set; } #region Events protected virtual void _(Events.FieldUpdated<SOLine, SOLine.inventoryID> e) { if (e.Row == null) { return; } SOLine lineRow = (SOLine)e.Row; //Users loggedUserRow = Users.PK.Find(this.Base, PXAccess.GetUserID()); System.Guid? u = _currentUserInformationPr

Hi,I need to overload confirmshipment action in acumatica 2025 R2. In 2024 version I used such codepublic class SOShipmentEntry_Extension : PXGraphExtension<PX.Objects.SO.SOShipmentEntry>{public delegate IEnumerable ConfirmShipmentActionDelegate(PXAdapter adapter);[PXOverride]public virtual IEnumerable ConfirmShipmentAction(PXAdapter adapter, ConfirmShipmentActionDelegate handler) {}}but in 2025 R2 acumatica I got this error.The System.Collections.IEnumerable ConfirmShipment(PX.Data.PXAdapter, ConfirmShipmentActionDelegate) method in the ClaLimitInvTiger25.ClaConfirmShipmentExtension graph extension is marked as [PXOverride], but no original method with this name has been found in PXGraph. I looked over the code and found they moved to cofirm shipment action into ConfirmShipmentExtension.cs file. I also tried to overl

I created a GI that pulls data from a custom table.  The GI is working perfectly.  I want to add a filter to the GI so that I can use the filter in the Mobile App.  The GI is working in the Mobile App.When I go to the Parameters tab in the GI, there are no fields available to select:Here are some print screens of the GI in case anything looks like it is missing: This is the result of viewing the GI:

I have a grid where two columns are colored in Classic UI, and this works correctly there.However, in Modern UI those same two columns are no longer colored and appear with default styling. Is there a supported way to apply styling to specific grid columns in Modern UI? I also tried applying custom CSS like this qp-grid#grid [data-field="UOMSelect"] { color: #0078d4; } qp-grid#grid [data-field="UOMCost"] { color: #d40000; }but it didnt work

I have a parameter in the report, but it does not work in the Modern UI on the Report Template page. When I click the drop-down, it does not set a value. In the Classic UI, it works correctly. How can I fix this?  

I have a custom screen with a custom grid.  On that grid, the user can lookup the customer.  In my current DAC field, it is restricting the customers to be returned based on whether the current user is linked to the Salesperson.For the customer nbr field in either the header or the grid, I am restricting the selector to only return customers where the current user is a salesperson on that customer.Thie is the DAC field for the grid. #region UsrCustomerID [CustomerActive()] [PXUIField(DisplayName = "Customer Nbr.", Required = true)] [PXSelector(typeof(Search2<Customer.bAccountID, InnerJoin<ICSCustomerSalesPersonLinksSQLView, On<ICSCustomerSalesPersonLinksSQLView.customerID, Equal<Customer.bAccountID>>>, Where<ICSCustomerSalesPersonLinksSQLView.userID.IsEqual<AccessInfo.userID.FromCurrent>>>), typeof(Customer.acctCD), typeof(Customer.acctName), Substitute

Hello Acumatica community 😀I'd like to know the best practice for creating a custom field on screens (Customer Payments and Supplier Payments).I need a boolean value that can be modified even after a payment has been closed.However, a custom field on the corresponding tables doesn't allow modification once it's closed.What's the best practice? Should I create a new extension table with the same key as the payments table?Or is there another solution?Thank you for your feedback.Have a good day everyone 😁

I want to set this screen to the Modern UI. How can I set 4 columns in each row? Is there an original Acumatica screen example like this?