Acumatica 2021 R2 Override Create Sales Order - acumatica

Question

Acumatica seems to have moved the CreateSalesOrder method from OpportunityMaint to the new CRCreateSalesOrder class. I cannot figure out how to override the CreateSalesOrder method with the new structure. Below is the original code. Any help greatly appreciated.
using PX.Data;
using PX.Objects.AR;
using PX.Objects.CM;
using PX.Objects.Common.Discount;
using PX.Objects.CR;
using PX.Objects.CR.Extensions.CRCreateSalesOrder;
using PX.Objects.CS;
using PX.Objects.IN;
using PX.Objects.PO;
using PX.Objects.SO;
using PX.Objects.TX;
using System.Collections.Generic;
using static PX.Objects.CR.OpportunityMaint;
namespace CH.KV.CPLVendorSOPO
{
public class CHKVOpportunityMaintExt : PXGraphExtension<OpportunityMaint>
{
public delegate void DoCreateSalesOrderDelegate(CreateSalesOrderFilter param);
[PXOverride]
public void DoCreateSalesOrder(CreateSalesOrderFilter param, DoCreateSalesOrderDelegate baseMethod)
{
DoCreateSalesOrderCHKVExt(param);
}
protected virtual void DoCreateSalesOrderCHKVExt(CreateSalesOrderFilter param)
{
bool recalcAny = param.RecalculatePrices == true ||
param.RecalculateDiscounts == true ||
param.OverrideManualDiscounts == true ||
param.OverrideManualDocGroupDiscounts == true ||
param.OverrideManualPrices == true;
var opportunity = Base.Opportunity.Current;
Customer customer = (Customer)PXSelect<Customer, Where<Customer.bAccountID, Equal<Current<CROpportunity.bAccountID>>>>.Select(Base);
//do things
docgraph.Save.Press();
}
}
}

Answer 1

You have to add the CRCreateSalesOrder extension class and overwrite the DoCreateSalesOrder method in there. This works on Acumatica 2022R2. Not sure of 2021R2.
public class CRCreateSalesOrderExt : CRCreateSalesOrder<OpportunityMaint.Discount, OpportunityMaint, CROpportunity>
{
#region Initialization
public static bool IsActive() => IsExtensionActive();
protected override DocumentMapping GetDocumentMapping()
{
return new DocumentMapping(typeof(CROpportunity))
{
QuoteID = typeof(CROpportunity.quoteNoteID)
};
}
#endregion
#region Events
public virtual void _(Events.RowSelected<CROpportunity> e)
{
CROpportunity row = e.Row as CROpportunity;
if (row == null) return;
CRQuote primaryQt = Base.PrimaryQuoteQuery.SelectSingle();
bool hasProducts = Base.Products.SelectSingle() != null;
var products = Base.Products.View.SelectMultiBound(new object[] { row }).RowCast<CROpportunityProducts>();
bool allProductsHasNoInventoryID = products.Any(_ => _.InventoryID == null) && !products.Any(_ => _.InventoryID != null);
bool hasQuotes = primaryQt != null;
CreateSalesOrder
.SetEnabled(hasProducts && !allProductsHasNoInventoryID
&& (
(!hasQuotes
|| (primaryQt.Status == CRQuoteStatusAttribute.Approved
|| primaryQt.Status == CRQuoteStatusAttribute.Sent
|| primaryQt.Status == CRQuoteStatusAttribute.Accepted
|| primaryQt.Status == CRQuoteStatusAttribute.Draft
)
)
)
&& (!hasQuotes || primaryQt.QuoteType == CRQuoteTypeAttribute.Distribution)
&& e.Row.BAccountID != null);
}
#endregion
#region Overrides
public override CRQuote GetQuoteForWorkflowProcessing()
{
return Base.PrimaryQuoteQuery.SelectSingle();
}
public override void DoCreateSalesOrder(SOOrderEntry docgraph, Extensions.CRCreateSalesOrder.Document masterEntity, CreateSalesOrderFilter filter)
{
base.DoCreateSalesOrder(docgraph, masterEntity, filter);
}
#endregion
}

Answer 2

You will need to find where the code was moved too. I have had to do something similar when acumatica shifted up some buttons within the Customer Payment Profile Maint Graph into its own dedicated class.
This is what the new graph extension declaration looked like I'm my case where the original was a direct extension of the Customer Payment Profile Maint Graph
public class APSPaymentProfileHostedFormExtension : PXGraphExtension<
CustomerPaymentMethodMaint.PaymentProfileHostedForm,
CustomerPaymentMethodMaint>
{
For clues, you want to look for something like this that will be declared on the graph the button originally resided. In my case, it looked like this.
public class PaymentProfileHostedForm : Extensions.PaymentProfile.PaymentProfileGraph<CustomerPaymentMethodMaint, CustomerPaymentMethod>
{
Hopefully, this is enough to get you in the right direction. Let me know how you make out?