Develop Customizations

 Hi, there is a custom field in Invoices and Memos screen called ‘Rental Agreement Nbr’ and this is also added in Application History tab of Payments and Applications screen. When sorting this column, I get the error: Unknown column 'ARRegister.UsrRANbr' in 'order clause' even though I have set the AllowSort to True. How do I allow sorting on this column?  

How can I change the selector in the Customer Number field so that it searches by Customer CD, Customer Name, and Telephone number as well? How can I do this?

Hi Team,I need to override the Email Quote button on the Sales Order screen to change the default From and To email addresses.How can I properly override this action in a Graph Extension and update these fields? Thanks in advance!

In the Classic screen, I use an action to highlight (change the row color of) records in the grid based on the value of the UsrFRCanShip field. When I click the action, the row colors update as expected (see the screenshot below).   After migrating the screen using the conversion tools:  The screen loads correctly in Modern UI, but the action no longer applies the row coloring in the grid.  Could you please advise how to implement this grid row coloring behavior in Modern UI? 

I have created a 25R2 Modern UI instance, added all 25R2-related dependencies into the automation framework, and created wrappers for CS201010 using 25R2 (ClassGenerator.exe.config). However, when I run the automation test script, the automation report shows errors, such as the “Add” button not being present, even though it is visible in the UI. 

I’ve been extolling the virtues of the Modern UI to my colleagues, especially how straight forward it is to code. Unfortunately I’ve found myself stuck on a screen where I simply cannot see the issue. The classic UI version of the screen is working fine, but I cannot get the Modern UI screen to work. The environment is 2025R2.The screen is supported by the following DACusing System;using PX.Data;using PX.Objects.CS;namespace SoImportDemo{ [PXCacheName(Helpers.Messages.ZZSoImportSetup)] [PXPrimaryGraph(typeof(ZZSoImportSetupMaint))] public class ZZSoImportSetup : PXBqlTable, IBqlTable { #region NumberingID [PXDBString(10, IsUnicode = true, InputMask = "")] [PXSelector(typeof(Numbering.numberingID), DescriptionField = typeof(Numbering.descr))] [PXUIField(DisplayName = "Numbering Sequence")] [PXDefault("SOIMPORT")]

Hi all,I am experiencing an issue with the Modern UI. When I click the ADD & CLOSE button, I receive the following message on the screen.How can I resolve this?Here is the relevant HTML/TypeScript code for reference: export class BZLines extends PXView { @columnConfig({ allowSort: false, width: 60, allowCheckAll: true }) Selected: PXFieldState; InventoryID: PXFieldState<PXFieldOptions.Disabled>; SiteID: PXFieldState<PXFieldOptions.Disabled>; InventoryID_description: PXFieldState<PXFieldOptions.Disabled>; OpenQty: PXFieldState<PXFieldOptions.Disabled&g

Highlights Additional Fixes AcknowledgementsHi everyone,We are pleased to announce that the new Acuminator 4.0.1 has been released.This is a hotfix release that addresses feedback that we received after the release of Acuminator 4.0.0. It includes several targeted improvements and bug fixes. You can download Acuminator from its page on Visual Studio Marketplace:https://marketplace.visualstudio.com/items?itemName=Acumatica.Acuminat

Hi everyone,I’m trying to customize SOLine.AlternateID, but the original Acumatica logic is interfering with my functionality. Specifically, I need to remove the AlternativeItemAttribute from SOLine.AlternateID.Here’s what I tried so far: #region AlternateID [PXMergeAttributes(Method = MergeMethod.Merge)] [PXRemoveBaseAttribute(typeof(AlternativeItemAttribute))] [PXDBDefault(null, PersistingCheck = PXPersistingCheck.Nothing)] [BZAlternativeItemAttribute(INPrimaryAlternateType.CPN, typeof(SOLine.inventoryID), typeof(SOLine.subItemID), typeof(SOLine.uOM))] protected virtual void SOLine_AlternateID_CacheAttached(PXCache sender) { } #endregionHowever, this doesn’t seem to remove the attribute completely. Has anyone successfully removed or replaced the AlternativeItemAttribute fro

​Hi,I’m creating the payment programmatically but payment status is showing Pending Processing.Even tried setting the status to balanced and it didn't worked.Payment is captured in the External system so we are filling the ExtranalTrsnaction table and below is the code that we used create the payment. ARPaymentEntry docgraph = PXGraph.CreateInstance<ARPaymentEntry>();                ARPayment objPayment = new ARPayment();                objPayment.DocType = ARDocType.Payment;                objPayment.Status = ARDocStatus.Balanced;                objPayment.CustomerID = order.CustomerID;                objPayment.PaymentMethodID = filter?.PaymentMethod;               // objPayment.CuryID = order.CuryID;                objPayment.ExtRefNbr = filter?.PaymentRefNbr;

How can we copy the OwnerID field from rhw sales order when creating a shipment in 2025 R2? In prior versions we were overriding the method SetShipmentFieldsFromOrder in SOShipmentEntry.  In 2025 R2 there is a new CreateShipmentExtension and it looks like the override may need to be moved to the method SetShipmentFieldsFromOrigDocument(SOShipment shipment, CreateShipmentArgs args, bool newlyCreated)?Below is our existing code.  It does not compile on 2025 R2 because the SetShipmentFieldsfromOrder method has been removed.   public class SOShipmentEntry2_Extension : PXGraphExtension<PX.Objects.SO.SOShipmentEntry> { [PXOverride] public virtual bool SetShipmentFieldsFromOrder( SOOrder order, SOShipment shipment, int? siteID, DateTime? shipDate, string operation, SOOrderTypeOperation orderOperation,

Hello Community, I am working on a small customization to simply pull up the Stock Items screen in a side panel when changing the detail row. It seemed like I couldn’t accomplish this on the POLine level and only choose header fields when adding the side panel, so I went with an unbound field on POOrder. How can I make it when changing the detail selection to successfully update the unbound field “Selected Item” below? You’ll notice I have the side panel popped up and open to the PNF item, but I have the EMP item selected. Any ideas? I did try forcing a “Note” update on change to refresh UI, but no luck. It does update by changing the side panel to something else and then back to stock item. See below for my code and screenshot: #region UsrReadInventoryNbr [PXString(60)]

Hello,We've added a new screen that displays the UserReportEx DAC in a table and created an action to move reports (with a specific checkbox selected) to another tenant on the same instance. For example, reports SO641010 and SO642000 are currently in Tenant A, and we want to move them to Tenant B.We discovered that the Report Designer uses the ServiceGate API, accessible under /api/servicegate.asmx for any instance, but we’re struggling to make it work.Here’s the code we currently have https://pastebin.com/sfd6AYdp, but it always returns the following error:Report Response: System.InvalidOperationException: Not authenticated. at PX.Api.WebServiceBase.VerifyLogin() in C:\build\code_repo\NetTools\PX.Data\Api\Legacy\AbstractServiceGate.cs:line 572 at PX.Api.WebServiceBase.ReportSave(String name, String xml) in C:\build\code_repo\NetTools\PX.Data\Api\Legacy\Ab

Hi Community Team,I would like to report a gap observed during screen conversion from Classic UI to Modern UI.When custom fields are created using a DAC Extension, those fields are correctly visible and functional in the Classic UI screen. However, after converting or working with the same screen in Modern UI, the extended DAC fields are not automatically included in the Modern UI layout.Observed Behaviour: DAC extension fields exist in the database. They are properly configured and visible in Classic UI. After switching to or converting the screen to Modern UI, the extended fields are not visible. No automatic synchronization happens between Classic UI layout and Modern UI layout. This creates confusion during conversion because developers expect the existing extended fields to be carried forward automatically.

How can I customize the system to not allow a user to change the Branch if certain conditions are met?  

Hi everyone. I have encounter. on my server every time I run the screen ID with PL. e.g. “SO.30.10.PL”. I got this error and continuous loading almost 30 mins but no result and try to stop it.I hope you can help me. 2025R2Build 25.200.0248 

When I open the browser console and write something like:function disableBranchSelector() { console.log("Disabling branch selector"); $('.branch-selector__button.dropdown-toggle').prop('disabled', true); } it works from the console and the dropdown is locked. But when I write this code in the Customization Project Screen Editor (as I usually write JS), it doesn’t work. I think the Sales Order screen JS doesn’t have access to this part of the screen, and that’s why it doesn’t work. How can I disable or hide this dropdown? What can I actually do with it? 

Hi everyone,Has anyone successfully added an external URL (for example a Power BI report) to the Acumatica Site Map so users can open it from the menu?I created a Site Map entry pointing to the Power BI report URL, but when clicking it Acumatica tries to display it inside the page (iframe) and I get an error like: “app.powerbi.com refused to connect”. Is there a recommended way to handle external links like this from Site Map? Can Site Map be configured to open the URL in a new tab/window instead of embedding it? Or is the best practice to use the Power BI reportEmbed URL / another approach (tile, dashboard link, custom screen)?

I need to add a custom field to the Applications tab on AP302000 - Cheques and Payments. I’ve followed the instruction elsewhere to append my field as the last column of the grid, but I need to put it somewhere that users will see it :-)So I have a TypeScript file containing export interface APPost_MyProject_generated extends APPost {}export class APPost_MyProject_generated {  APAdjust2__UsrPartPaymentAmt: PXFieldState;  APAdjust2__UsrPartPaymentPct: PXFieldState;} And HTML<template><field id="APAUsrPPPct" name="APAdjust2__UsrPartPaymentPct" after="#gridApplicationHistory"></field><field id="APAUsrPPAmt" name="APAdjust2__UsrPartPaymentAmt" after="#APAUsrPPPct"></field></template>And while that works, it means that the field is the final column in the table.(I found that having added the firs

Hello Community,I am facing an issue related to creating a POOrder from a Service Order using the standard POCreate process screen.Scenario:Service Order Type: InternalFor this type, the Customer field is not mandatory by design.The requirement is to create a POOrder from such a Service Order.Problem:When attempting to create the POOrder via the POCreate screen, the system throws an error indicating that the Customer field in the Service Order is required.In standard functionality, the required validation for the Customer field is removed dynamically in RowSelected depending on the Service Order Type. However, when the Service Order is updated from the POOrder creation process, RowSelected does not appear to be triggered. As a result, the Customer field remains required and the validation error is raised.Additionally, I noticed that the Service Order is being overwritten during the attempt to save the POOrder, which seems

I want to create a PDF from a report in code and then send it to print. How can I do it?

Using an instance of 25.200.0020 (clean install), I need to customise screen AP303000 to add some fields (specifically AddressLine3), but on opening the Modern UI Editor from the Customization Project Editor for that screen, I get the error message: In HTML extension “C:\..\FrontendSources\screen\src\screens\AP303000\extensions\AP303000_PersonalDataPrivacy.html” for screen ‘AP303000’ child node ‘QP-FIELDSET’ has AFTER attribute with ‘#groupAccountAddress’ but screen HTML doesn’t contain any elements that satisfies such querySelector.I can work around this locally by renaming the source files AP303000_PersonalDataPrivacy.html and .ts (adding a suffix of .x). But I’m concerned that the same hack won’t be possible in production. 

Hey all    One of the things we do to maintain our customer base is have our customization send the customer’s Acumatica version back to the office so we can track where everyone is.  Does anyone know how to retrieve the site’s patch status in code?  It’s not in the version table, but i figure someone her might know.Thanks!

Hello,I am trying to add two custom fields (UsrMXFEPedimentoNbr and UsrMXFEImportDate) to the Line Details (Line Splitting) grid in the Shipments screen.Acumatica Version: 2025 R2SO302000 - Line Details panelFollowing the standard extension pattern, I created the .ts and .html files. However, when running npm build, I get an error stating that #grid-LineSplitting does not exist.After investigating, I noticed that SO302000_LineSplitting.html references a shared component: ../../../IN/common/line-splitting/panel-line-splitting/panel-line-splitting.html. Since the grid is defined in that shared template and not directly in the SO302000 main files,

I have added custom fields (UsrInDocType and UsrInRefNbr) in FSAppointmentDet to link to INRegister. When I try to delete the related INRegister from a button on FSAppointment using INIssueEntry, I get the following error:"Cannot mark the record as updated because another record with the same key exists in the cache."