Acumatica Application Architecuture


Hello everybody,

today I want to leave a short note about Acumatica Architecture. Take a look on this picture:

As you can see from the schema business logic controllers is kind of single source of truth. Acumatica doesn't have dependencies between UI and Web services. Also it means, if you hide something from UI on the page, it will be also hidden from Mobile app.

But want to say about few exceptions as well.

Suppose following scenario. You make a graph, and you know for sure, that from UI standpoint, it's logicall to load some visualization data, but from API call there is no reason to call some piece of code. How to inform Acumatica about it?

For this purpose you can use IsContractBasedAPI method of class graph. It may look like this:

if (!Base.IsContractBasedAPI)
    // Do something for UI
    //Do Something for non UI

Among other interesting modes of functionality, it is worthy to mention also IsMobile ( do something only for mobile apps ), IsExport ( do something in scope of export scenario ), IsImport ( do something in scope of Import scenario ), IsCopyPasteContext ( do something in scope of copy/paste functionality )


Taking into account all of these facts, you can be almost certain that in majority of cases Acumatica will execute pieces of logic like on the UI of Acumatica instance. But it will not be 100% times. So next time, when you API call give you data different of what you see in UI, check base source code, maybe there is the issue.



Property From Cropportunity Is Not Loaded


Hello everybody,

today I want to leave short note on issue with CROpportunity DAC class.

For quite a few times I've noticed that someone adds field to CROpportunity, but later notices that field is lost either on moment of loading from database, or lost during persisting record to database.

Reason for such weirdness is that starting from some Acumatica version CROpportunity got following declaration:

		Where2<Where<Optional<CROpportunity.bAccountID>, IsNullAnd<Contact.contactID
Equal<Optional<CROpportunity.contactID>>>>,    Or2<Where<Optional<CROpportunity.bAccountID>, IsNotNull
And<Contact.bAccountIDEqual<Optional<CROpportunity.bAccountID>>>>, Or<Contact.contactTypeEqual<ContactTypesAttribute.employee>>>>>))] [PXEMailSource]//NOTE: for assignment map [PXProjection(typeof(Select2<Standalone.CROpportunity, InnerJoin<Standalone.CROpportunityRevisionOn<Standalone.CROpportunityRevision.noteID
Equal<Standalone.CROpportunity.defQuoteID>>, LeftJoin<Standalone.CRQuote, On<Standalone.CRQuote.quoteIDEqual<Standalone.CROpportunity.defQuoteID>>>>>), new Type[] { typeof(Standalone.CROpportunity), typeof(Standalone.CROpportunityRevision) } )]     public partial class CROpportunity : IBqlTableIAssignIPXSelectableINotable {

List of applied attributes is pretty heavy and can be confusing, but reason of such losts live in this part:

	new Type[] { typeof(Standalone.CROpportunity), typeof(Standalone.CROpportunityRevision) }

As you can see, CROpportunity has decoration of PXProjection. I have one more sample of PXProjection on my blog.

But coming back, how to deal with data loss? Answer is simple: you'll need to make extension for two DAC classes, instead of one. 

Below goes code sample of what I've did for one of my customers:

    public class CROpportunityExt : PXCacheExtension<CROpportunity>
		#region UsrContractLength
		[PXUIField(DisplayName = "Contract Duration ")]
		public virtual int? UsrContractDuration { getset; }
		public abstract class usrContractDuration : IBqlField { }

and one more cache extension:

public class CROpportunityStandAloneCSEXt : PXCacheExtension<PX.Objects.CR.Standalone.CROpportunity>
    #region UsrContractLength
    [PXUIField(DisplayName = "Contract Duration")]
    public virtual int? UsrContractDuration { getset; }
    public abstract class usrContractDuration : IBqlField { }


As usually if field doesn't arrive from db or not to db the problem is in forgeting of DB prefix. Instead of PXDBInt quite often is typed ( or probably would say copy/pasted ) PXInt. Another common reason is override of PXView with delegate, and forgetting of including newly added column in the output, or sometime if delegate has plenty of conditional statements then not including some field into those statements list. Third reason is or could be FieldSelecting/FieldUpdating/RowUpdated behavior which can "kill" value. And fourth by commonality but not by complexity reason can be issues when you have PXProjection over DAC class. 



Lastmodifieddatetime Has Wrong Datetime Information


Hello everybody,

today I want to share interesting use case which raised recently when dealt with syncrhonization of records between Magento and Acumatica.

I had following declaration:

#region LastModifiedDateTime
[PXUIField(DisplayName = "Last Modified Date Time")]
public virtual DateTime? LastModifiedDateTime { getset; }
public abstract class lastModifiedDateTime : PX.Data.BQL.BqlDateTime.Field<lastModifiedDateTime> { }

and for my disappointment as well as disappointment of Magento developers we had to add some hours shift to each call, in order to filter out properly by Last modified Date time.

One of the solutions was to add one more flag to attributes in LastModifiedDateTime: UseTimeZone. By default that attribute is set to true, but in my case it was necessary to set it to false:

#region LastModifiedDateTime
[PXDBDateAndTime(UseTimeZone = false)]
[PXUIField(DisplayName = "Last Modified Date Time")]
public virtual DateTime? LastModifiedDateTime { getset; }
public abstract class lastModifiedDateTime : PX.Data.BQL.BqlDateTime.Field<lastModifiedDateTime> { }

After I've made usage of that attribute, values in UI started to display according to what I've seen on db level.


In case if you see discrepancy between value on db, and UI, and want to have only db level displayed in UI, use flat UseTimeZone set to false.


Selectfrom For Usage In View Select


Hello everybody,

I want to leave a short note on how to use SelectFrom for legacy code, and pass it in View.Select for Acumatica newer versions. 

var cmd = new SelectFrom<PartsCatalog>.
var s = (currentFilter.PageNbr ?? 0) * (currentFilter.PageSize ?? 0);
int startRow = s > 0 ? s : PXView.StartRow;
int totalRows = 0;
int maxRows = (currentFilter.PageSize ?? 0) == 0 ? PXView.MaximumRows : currentFilter.PageSize ?? 0;
var list = cmd.View.Select(new[] { currentFilter }, nullPXView.Searches,
    PXView.SortColumns, PXView.Descendings, PXView.Filters, ref startRowmaxRowsref totalRows).ToList();

As you can see, each time, when field is not converted to a newer Acumatica FBQL, you can refer to Use and AsType.


How To Overrde Authorize Cc Payment Action In Acumatica


Hello everybody,

as it was mentioned in one of my previous blog posts, regarding overriding base actions of Acumatica graphs, family of graph extensions grows and grows. 


Today I want to share one more code snippet which you can use for extending modification of Acumatica actions. Below goes code fragment, which you can use for modification of Authorize CC Payment:

public class PaymentTransactionExt : PXGraphExtension<PaymentTransactionSOOrderEntry>
    public virtual IEnumerable AuthorizeCCPayment(PXAdapter adapterFunc<PXAdapterIEnumerablebaseFunc)
        var result = baseFunc(adapter);
        return result;

Of what I foresee now, is a loooooot of work for Acumatica developers upgrading to a newer versions of Acumatica. 

Why I say so? 

Because as usually ISV have their code in SOOrderEntry extensions. But now they either will need to move their code from SOOrderEntry extensions or for example to reference Base1 ( which is your extension ) as well as Base.

Reason why Acumatica does this is probably following few general programming principles of: SRP ( single responsibility principle ), DRY ( Dont Repeat Yourself ) principle, Open Closed principle on graph level, which in long term will bring more stability to the system.

Basic advice will be this, don't expect that upgrade of your code base to 2019 R2 will be as fast, as it used to be in the past, and before giving estimate which you used to give, pay special attention to how new actions are declared.



How To Override Shoprates Action In Sales Orders Form


Hello everybody,

today I want to leave a short post on how to override Shop rates Action in Acumatica. 

I mean this button:

Below goes C# code, with which you can achieve it:

public class SOOrderEntryExt : PXGraphExtension<SOOrderEntry.CarrierRatesSOOrderEntry>
    public virtual IEnumerable ShopRates(PXAdapter adapterFunc<PXAdapterIEnumerablebaseMethod)
        //your code here
        var retVal = baseMethod?.Invoke(adapter);
        //and possibly here
        return retVal;

As you can see from the code, life in Acumatica becomes more complex, and if in the past you've used to override directly your actions, now you'll need to create extension for extension in order to override some Actions. 

Similar issues I've seen in other places of SOOrderEntry, for example in AuthorizeCCPayment, CaptureCCPayment, etc.


Pxlongoperation Cleans Everything How To Avoid


Hello everybody,

today I want to write a few words about interesting behavior of PXLongOperation.StartOperation in Acumatica.

On the glance that looks pretty simple and straightforward. You have something processing of which will take a long time? Use PXLongOperation.StartOperation. So imagine, you extend ARPaymentEntry graph like this:

public PXAction<ARPayment> StartOperation;
[PXUIField(DisplayName = "Some long running operation")]
protected virtual IEnumerable startOperation(PXAdapter adapter)
   PXLongOperation.StartOperation(Base, () => SomeLongRunningOperation(Base.Document.Current));
return adapter.Get(); }

In this case you may notice interesting behavior. If your ARPayment is saved, then everything will work relatively fine. But if not, any kind of data, that user enetered will be lost. How to deal with it. Below goes implementation that will deal with this:

public PXAction<ARPayment> StartOperation;
[PXUIField(DisplayName = "Some long running operation")]
protected virtual IEnumerable startOperation(PXAdapter adapter)
    PXCache cache = Base.Document.Cache;
    List<ARRegisterlist = new List<ARRegister>();
    PXLongOperation.StartOperation(Base, () => SomeLongRunningOperation(Base.Document.Current));
    return list;

Besides that, in the end of your function SomeLongRunningOperation you may consider adding code like this:

ARPayment arPayment = cuArPayment;
var newGraph = PXGraph.CreateInstance<ARPaymentEntry>();
newGraph.Document.Current =
    Base.Document.Search<ARPayment.refNbr>(arPayment.RefNbr, arPayment.DocType);
//  Some additional lines of code

In that case after SomeLongRunningOperation function will finish it's processing, it will refresh current screen of user.


If you deal with PXLongRunningOperation, you'll need to have following elements:

  1. Save existing item
  2. Return list with one element ( current primary element of view ), which will leave user on the same element
  3. In the end of PXLongRunningOperation call TryRedirect which will refresh currently selected view



How To Make Dynamic List With Check Boxes In Acumatica


Hello everybody,

today I want to share with you a piece of code, with help of which you can get list of all activer order types in Acumatica and also you'll get a chance to select those types with checkbox. Take a look on a screenshot below:

how to achieve this?

Code below without description of DAC class gives you this:

protected virtual void _(Events.FieldSelecting<SetupClassSetupClass.orderTypese)
    if (e.Row == null)
    var orderTypes = SelectFrom<SOOrderType>.Where<<True>>.View.Select(this).Select(a => a.GetItem<SOOrderType>())
    var allowedValues = orderTypes.Select(a => a.OrderType).ToArray();
    var allowedLabels = orderTypes.Select(a => a.Descr).ToArray();
    var returnState = PXStringState.CreateInstance(e.ReturnValue, allowedLabels.Length, true,
        false, -1, string.Empty, allowedValuesallowedLabelsfalsenull);
    (returnState as PXStringState).MultiSelect = true;
    e.ReturnState = returnState;

On aspx level, it look trivial:

<px:PXDropDown ID="PXDropDown1" runat="server" DataField="OrderTypes" CommitChanges="true" />

With help of this code, you'll get list of all order types, which you'll be able to persist in database.


How To Insert Varbinary Data In Ms Sql For Acumatica


Hello everybody,

sometime it is needed to insert some binary information in one or another table inside of Acumatica. Quite often developers just modify existing record in table UploadFile or UploadFileRevision.

But I don't like such approach, as it is prone to errors and potentially can harm some of your existing data. That's why I propose to use cast operator of MS SQL. Take a look at following example:

insert into UploadFileRevision(CompanyID, FileID, FileRevisionID, Data, Size, CreatedByID, CreatedDateTime, CompanyMask) values
								(2, '35b15ad7-b5c3-4a19-aa77-3a24c046d689', 1, 
													CAST('wahid' AS VARBINARY(MAX)),
													'2016-06-08 08:53:50.937',


Take notice of 


line. It will insert into local dev instance database varbinary representation of wahid. 


How To Imitate Click On Confirm Shipment In Acumatica


Hello everybody,

Today I want to describe how to imiate click on menu item "Confirm shipment" in Acumatica. 

Probably your first guess will be just call method ConfirmShiment of graph SOShipmentEntry. But for now Acumatica team has another advice in order to call this action. Instead of calling method ConfirmShipment you'll need to have a bit more steps.

Code sample below demonstrates those necessary steps:

SOShipmentEntry shipmentGraph = PXGraph.CreateInstance<SOShipmentEntry>(); //Create instance of Graph
PXAdapter adapter2 = new PXAdapter(new DummyView(shipmentGraph, shipmentGraph.Document.View.BqlSelect,
						 new List<object> { shipmentGraph.Document.Current }));
adapter2.Menu = SOShipmentEntryActionsAttribute.Messages.ConfirmShipment;
adapter2.Arguments = new Dictionary<stringobject>
adapter2.Searches = new object[]{shipmentGraph.Document.Current.ShipmentNbr};
adapter2.SortColumns = new[] { "ShipmentNbr"};
TimeSpan timespan;
Exception ex;
while (PXLongOperation.GetStatus(shipmentGraph.UID, out timespanout ex) == PXLongRunStatus.InProcess)
{ }
//Here you'll have your shipment confirmed

And DummyView looks like this:

public class DummyView : PXView
        List<object> _Records;
        internal DummyView(PXGraph graphBqlCommand commandList<objectrecords)  : base(graphtruecommand)
            _Records = records;
        public override List<objectSelect(object[] currentsobject[] parametersobject[] searchesstring[] sortcolumns
bool[] descendingsPXFilterRow[] filtersref int startRowint maximumRowsref int totalRows)         {             return _Records;         }     }

If you wonder, why calling ConfirmShipment is not enough, answer is this: ConfirmShipment cal will confirm shipment, but it will not execute Automation Steps. Thats why all of mentioned steps are needed. Otherwise, you'll make long research on question, why something doesn't work in the same way, as it works in UI, but doesn't work from my code.