Rename column at screen in Acumatica

Hello everybody,

today I want to share answer at simple question how to change the caption at some screen. 

For example you want to change caption at screen AR202000 for Inventory ID to caption INVENTORY ID.

For this purpose we need to understand which DAC is responsible for Grid. For this puprose we can open page AR202000.

There we can see the following line:

<px:PXDataSource ID="ds" runat="server" Visible="True" Width="100%" PrimaryView="Filter" TypeName="PX.Objects.AR.ARSalesPriceMaint">

So it means that for Graph or controller we will check ARSalesPriceMaint.

For field inventory id responsible code 

<px:PXSegmentMask ID="edInventoryID" runat="server" DataField="InventoryID" AllowEdit="True">

and view which we need is named 

 <px:PXGridLevel DataMember="Records">

Lets navigate to class PX.Objects.AR.ARSalesPriceMaint with help of reflector ( one of my favorite tools ).

Find there member Records which is declared in the following way:

public SalesPriceProcessing<ARSalesPrice, InnerJoin<InventoryItem, On<InventoryItem.inventoryID, Equal<ARSalesPrice.inventoryID>>, LeftJoin<INItemCost, On<INItemCost.inventoryID, Equal<InventoryItem.inventoryID>>>>, Where<ARSalesPrice.custPriceClassID, Equal<Current<ARSalesPriceFilter.custPriceClassID>>, And2<Where<Current<ARSalesPriceFilter.curyID>, IsNull, Or<ARSalesPrice.curyID, Equal<Current<ARSalesPriceFilter.curyID>>>>, And<ARSalesPrice.isPromotionalPrice, Equal<Current<ARSalesPriceFilter.promotionalPrice>>, And<InventoryItem.itemStatus, NotEqual<INItemStatus.inactive>, And<InventoryItem.itemStatus, NotEqual<INItemStatus.toDelete>, And<Where2<Where<Current<ARSalesPriceFilter.itemClassID>, IsNull, Or<Current<ARSalesPriceFilter.itemClassID>, Equal<InventoryItem.itemClassID>>>, And2<Where<Current<ARSalesPriceFilter.inventoryPriceClassID>, IsNull, Or<Current<ARSalesPriceFilter.inventoryPriceClassID>, Equal<InventoryItem.priceClassID>>>, And2<Where<Current<ARSalesPriceFilter.ownerID>, IsNull, Or<Current<ARSalesPriceFilter.ownerID>, Equal<InventoryItem.priceManagerID>>>, And2<Where<Current<ARSalesPriceFilter.myWorkGroup>, Equal<boolFalse>, Or<InventoryItem.priceWorkgroupID, InMember<CurrentValue<ARSalesPriceFilter.currentOwnerID>>>>, And<Where<Current<ARSalesPriceFilter.workGroupID>, IsNull, Or<Current<ARSalesPriceFilter.workGroupID>, Equal<InventoryItem.priceWorkgroupID>>>>>>>>>>>>>>, OrderBy<Asc<ARSalesPrice.inventoryID, Asc<ARSalesPrice.uOM, Asc<ARSalesPrice.lastDate>>>>> Records;

Looks scarry, huh? For me in the begining of my way also. But lets continue. 

DataField="InventoryID" means that this field is declared in class ARSalesPrice.

Just for example lets say that DataField looked in the following way:

DataField="InventoryItem__InventoryID". That mean that we need to search for class InventoryItem.

Lets navigate with reflector to class ARSalesPrice and find there field InventoryID.

It's declared in the following way:

        [Inventory(DisplayName="Inventory ID"), PXDefault, PXParent(typeof(Select<InventoryItem, Where<InventoryItem.inventoryID, Equal<Current<inventoryID>>>>))]
        public virtual int? InventoryID
        {
            get
            {
                return this._InventoryID;
            }
            set
            {
                this._InventoryID = value;
            }
        }

Then do the following:

1. create class ARSalesPriceExt like this:

 public class  ARSalesPriceExt : PXCacheExtension< ARSalesPrice>
    {

2. In the class declare the following member:

        [Inventory(DisplayName="INVENTORY ID"), PXDefault, PXParent(typeof(Select<InventoryItem, Where<InventoryItem.inventoryID, Equal<Current<inventoryID>>>>))]
        public virtual int? InventoryID
        {
            get
            {
                return this._InventoryID;
            }
            set
            {
                this._InventoryID = value;
            }
        }

3. Build class library and reference it in your Acumatica web site and congratulations, you have changed caption in grid

 

FieldUpdated behaviour

Hello everybody,

today  I want to share one interesting feature of Acumatica. 

I revelaed that after inserting of new row executes FieldUpdated even if field wasn't updated. After reading documentation I found that it is gotcha and inteded to be so.

Acumatica and ObjectsEqual lack of parameters

Hello everybody,

today I want to share how I deal with ObjectsEqual limitation. In one of my tasks I had requirement to check for equality more then eight parameters and found that ObjectsEqual takes only 8 parameters. But I needed more. 

In order to fix it I decided to use extension classes of C# which allows inject into existing class new functionality.

Here is the way how I did it:

public static class PXCacheExtensions
    {
        public static bool ObjectsEqualExt(this PXCache cache, object a, object b, params IBqlField[] values)
        {
            var result = true;
            foreach (var bqlField in values)
            {
                result = result && object.Equals(cache.GetValue<IBqlField>(a), cache.GetValue<IBqlField>(b));
            }

            return result;
        }

        public static bool ObjectsEqual<Field1, Field2, Field3, Field4, Field5, Field6, Field7, Field8, Field9>(this PXCache cache, object a, object b)
            where Field1 : IBqlField
            where Field2 : IBqlField
            where Field3 : IBqlField
            where Field4 : IBqlField
            where Field5 : IBqlField
            where Field6 : IBqlField
            where Field7 : IBqlField
            where Field8 : IBqlField
            where Field9 : IBqlField
        {
            return (cache.ObjectsEqual<Field9>(a, b) && cache.ObjectsEqual<Field1, Field2, Field3, Field4, Field5, Field6, Field7, Field8>(a, b));
        }

        public static bool ObjectsEqual<Field1, Field2, Field3, Field4, Field5, Field6, Field7, Field8, Field9, Field10>(this PXCache cache, object a, object b)
            where Field1 : IBqlField
            where Field2 : IBqlField
            where Field3 : IBqlField
            where Field4 : IBqlField
            where Field5 : IBqlField
            where Field6 : IBqlField
            where Field7 : IBqlField
            where Field8 : IBqlField
            where Field9 : IBqlField
            where Field10 : IBqlField
        {
            return (cache.ObjectsEqual<Field10>(a, b) && cache.ObjectsEqual<Field1, Field2, Field3, Field4, Field5, Field6, Field7, Field8, Field9>(a, b));
        }

        public static bool ObjectsEqual<Field1, Field2, Field3, Field4, Field5, Field6, Field7, Field8, Field9, Field10, Field11>(this PXCache cache, object a, object b)
            where Field1 : IBqlField
            where Field2 : IBqlField
            where Field3 : IBqlField
            where Field4 : IBqlField
            where Field5 : IBqlField
            where Field6 : IBqlField
            where Field7 : IBqlField
            where Field8 : IBqlField
            where Field9 : IBqlField
            where Field10 : IBqlField
            where Field11 : IBqlField
        {
            return (cache.ObjectsEqual<Field11>(a, b) && cache.ObjectsEqual<Field1, Field2, Field3, Field4, Field5, Field6, Field7, Field8, Field9, Field10>(a, b));
        }

        public static bool ObjectsEqual<Field1, Field2, Field3, Field4, Field5, Field6, Field7, Field8, Field9, Field10, Field11, Field12>(this PXCache cache, object a, object b)
            where Field1 : IBqlField
            where Field2 : IBqlField
            where Field3 : IBqlField
            where Field4 : IBqlField
            where Field5 : IBqlField
            where Field6 : IBqlField
            where Field7 : IBqlField
            where Field8 : IBqlField
            where Field9 : IBqlField
            where Field10 : IBqlField
            where Field11 : IBqlField
            where Field12 : IBqlField
        {
            return (cache.ObjectsEqual<Field12>(a, b) && cache.ObjectsEqual<Field1, Field2, Field3, Field4, Field5, Field6, Field7, Field8, Field9, Field10, Field11>(a, b));
        }


    }

After those modifications my cache accepts twelve parameters for comparing

Enums and strings

Hello everybody,

I want to share some pieces of code how to work with enums. 

Some time it is needed to have list of string constants in your code, which can feet to some strings with spaces. 

enum EarningType
    {
        [Description("Virginina")]
        VL,
        [Description("Salt and Lasso")]
        SL,
        [Description("TO")]
        TO,
        [Description("RG")]
        RG
    }

One of easy ways to use description is usage of extension methods like this:

 public static class EnumsProcessor
    {
        public static string GetEnumDescription(this Enum value)
        {
            var fi = value.GetType().GetField(value.ToString());

            var attributes =
                (DescriptionAttribute[])fi.GetCustomAttributes(typeof(DescriptionAttribute), false);

            if (attributes.Length > 0)
                return attributes[0].Description;
            return value.ToString();
        }
}

and then in code you can write something like this:

EarningType.VL.GetEnumDescription() which will return you description from description field.

Execute stored procedure in Acumatica

Hello everybody.

I want to share if you need to execute stored procedure in Acumatica how to achieve it. 

It's simple.

1. Create Stored procedure in db.

2. Use in your code PXDatabase.Execute.

For example let's say you created stored procedure which has name DeletePrTranByPrPayrollAndPayrollDetailsId and takes as parameters @prPayrollRefNbr and @prPayrollDetailsID which are of type nvarchar.

Then you can call stored procedure in the following way:

var pars = new List<PXSPParameter>();

PXSPParameter p1 = new PXSPInParameter("@prPayrollRefNbr", PXDbType.NChar, details.PayrollRefNbr);

PXSPParameter p2 = new PXSPInParameter("@prPayrollDetailsID", PXDbType.NChar, details.PRPayrollDetailID);

pars.Add(p1);

pars.Add(p2);

PXDatabase.Execute("DeletePrTranByPrPayrollAndPayrollDetailsId", pars.ToArray());

PXSelect vs PXSelectReadonly

Hello everybody,

today I want to share with you important difference between PXSelect  and PXSelectReadonly.

In my project I had the following situation. PXSelect of table name didn't give me what actually was in db. After a long research I found PXSelectReadonly and key difference is that PXSelectReadonly reads directly from db without usage of Acumatica Cache. 

RowPersisting declaration in Acumatica

Just small search result.

Row persiting event declares as following:

protected virtual void YourDACClasss_RowPersisting(PXCache cache, PXRowPersistingEventArgs e)

   {

 

   }

Create new instance of graph in Acumatica

Hello,

today I want to note how to create new instance of Graph. Lets say you need to create instance of graph PRPaySlipManager.

In that case you can get instance of that graph in the following way:

PRPaySlipManager manager = PXGraph.CreateInstance<PRPaySlipManager>();

What is tstamp

Hello everybody,

I want to share what is purpose of field TStamp in database for tables in Acumatica. In reality you can make projects without it, but. If you add it, you'll help Acumatica with concurency management