Auto Discovery Mechanism Of Acumatica Extensibility Framework

Hello everybody,

another interesting notice today. 

Imagine following situation.

1. You have base class. Let it is called GraphX. 

2. In your library you created extentions of this grap: GraphXExt1, GraphXExt2 at the same level. For example like this:

public class GraphXExt1 : PXGraphExtension<GraphX>
{
   protected virtual void ARTran_USRProjectID_FieldDefaulting(PXCache sender, 
                 PXFieldDefaultingEventArgs e)
   { 

   }
}

public class GraphXExt2 : PXGraphExtension<GraphX>
{
   protected virtual void ARTran_USRProjectID_FieldDefaulting(PXCache sender, PXFieldDefaultingEventArgs e)
   { 

   }

}

3. Then question, if page will be loaded, which ARTran_USRProjectID_FieldDefaulting will be executed? From GraphXExt1 or from GraphXExt2?

The answer is the last loaded ( !!!!! ). If last loaded by framework will be GraphXExt2 then GraphXExt2 will be the winner. If last loaded will be GraphXExt1 then page will execute ARTran_USRProjectID_FieldDefaulting of GraphXExt1. Acumatica doesn't have any way to configure loading sequence of graphs. It means that it is crazy idea to make changes of the same member in two different graphs.

Ready to take your Acumatica development to the next level? If you’ve ever faced challenges like managing graph extensions or customizing workflows, we’re here to help! Whether it’s resolving loading sequence complexities or tailoring Acumatica to fit your unique business needs, our team specializes in creating seamless customizations that work for you.

Leave a customization request today and let us handle the technical intricacies while you focus on growing your business. Don’t let development hurdles slow you down—reach out now and let’s build the solution you need!