I need to add a filter to the Credit Card Processing for Sales screen (SO.50.70.00) so that only records where the DocType = Invoice will show, based on an additional custom checkbox in the filter section called "Invoices Only".public class SOPaymentProcess_Extension : PXGraphExtension<SOPaymentProcess>{ protected delegate void AddFiltersDelegate(PXSelectBase<ARPayment> view, SOPaymentProcessFilter filter); [PXOverride] protected virtual void AddFilters(PXSelectBase<ARPayment> view, SOPaymentProcessFilter filter, AddFiltersDelegate baseMethod) { baseMethod(view, filter); SOPaymentProcessFilterExt filterExt = PXCache<SOPaymentProcessFilter>.GetExtension<SOPaymentProcessFilterExt>(filter); if (filterExt.UsrInvoicesOnly != null) { // filtering code here } }}public class SOPaymentProcessFilterExt : PXCacheExtension<PX.Objects.SO.DAC.Unbound.SOPaymentProcessFilter>{ #region UsrInvoicesOnly
I would like to dynamically change the color (“Connotation”) of the Confirm Shipment action button (Shipment Entry screen) depending on a condition in 21R2.Example use case: If the Package Weight is not within an allowable range of the Shipped Weight, then change the Confirm Shipment action button connotation to "Warning". Otherwise, use “Success”. This color change would provide another visual indicator to my fulfillment staff that a shipment is okay to confirm.I’m currently using the `SOShipment_PackageWeight_FieldUpdated()` event to raise a SetPropertyException, but the warning icon is so small that it’s easily missed. I want to provide more visible feedback to the end-user to help prevent costly packaging errors.In the 21R2 workflow editor, the color appears to be controlled by the “Connotation” selection.It does not appear to be possible to conditionally change the connotation of the Action button using the 21R2 workflow editor. How can it be done using code? Maybe using PXScreenC
I'm trying to add a column to the Inventory Summary (IN.40.10.00) grid and I feel like I must be missing something simple.I need to output the INLocation.PickPriority value as a column which corresponds to the LocationID.I've created this DAC extension:public class InventorySummaryEnquiryResultExt : PXCacheExtension<PX.Objects.IN.InventorySummaryEnquiryResult>{ #region UsrPickPriority [PXInt] [PXDBScalar(typeof(Search<INLocation.pickPriority, Where<INLocation.locationID, Equal<InventorySummaryEnquiryResult.locationID>, And<INLocation.siteID, Equal<InventorySummaryEnquiryResult.siteID>>>>))] [PXUIField(DisplayName = "Pick Priority")] public virtual int? UsrPickPriority { get; set; } public abstract class usrPickPriority : PX.Data.BQL.BqlInt.Field<usrPickPriority> { } #endregion}The PickPriority value is set to 999 in the Warehouses (IN.20.40.00) screen, but I can't get it to display on the Inventory Summary
I’m currently upgrading to 21r2. I have a business need for a warehouse restocking report. This is different than a replenishment or purchasing report.My goal is to make it so a warehouse picker never arrives at an empty Default Issue From location because it’s already been refilled by restocker. FIFO must be factored, when applicable.Consider an example Inventory ID `12345` that is Lot Tracked with a FIFO issue method. This item is stored in 4 different locations within a single warehouse:Location IDs for `12345`:——————PRIMARYPICK — Default Issue From location (this is where we pick from)STORAGE1 — Lot #3 (newest inventory)STORAGE2 — Lot #2 (older inventory)STORAGE3 — Lot #1 (oldest inventory)I need a report (or generic inquiry) to tell my restockers to refill the PRIMARYPICK for `12345` *before* the inventory runs out. It needs to direct them to the correct Location ID that should be used for restocking the PRIMARYPICK. In the example above, this would be STORAGE3 because it’s the ol
I'm working to upgrade from 2019R1 to 2021R2.Credit card processing is quite different in 21R2 than I'm familiar with. I need some direction for how to process Sales Orders with Credit Cards using the REST API in 21R2.I'm currently using the REST API to insert Sales Orders with a credit card payment (authorized only, not captured) using the SalesOrder endpoint. As part of the API call to the SalesOrder endpoint, I only have to provide the PaymentMethod and external PreAuthorizationNbr. This corresponds to a tab in the SO called "Payment Settings". It works great, but no longer exists in 21R2. I understand that I now need to use the Sales Order -> Payments tab, but it's not clear to me how to associate the external pre-authorization with the Payment and Application using the REST API.Can anyone point me to documentation or examples or using the REST API to insert Sales Orders with pre-authorized (or even captured) credit card transactions.Should I use the REST API to build a Payment
In Acumatica 2021r2, is it possible to hide/show Action buttons in the main toolbar based on conditions within the selected state? (I’m willing to use the Workflow Editor or by custom code, if that is possible.)Example scenario for Shipment Entry screen (SO302000):When the active state is Confirmed, I want to duplicate the Print Labels action as a button in the main toolbar, but only if labels haven't already been printed. The labelsPrinted boolean in the SOShipment DAC can be used for the conditional. But it does not appear that you can associate a conditional with the Duplicate on Toolbar checkbox.I still need to retain Print Labels as an option in the More (...) menu regardless of the labelsPrinted boolean within the same Confirmed state. It's possible labels need to be reprinted, but I don't want to give the action the same prominence in the toolbar if they have already been printed once.Can anyone point me in the right direction?
In Acumatica 2021R2, the long running process message is more visible and prominent. This is a welcome change. It was difficult to detect the small red and green icon in previous versions.In 21R2, the only way I’ve found to remove/hide this overlay is to click the close icon "X".I'd like to hide the success overlay via code after a specific event, for example, so the end user doesn’t have to manually click the “X” icon. Is there any way to hide or change this overlay programmatically?
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.