Hi, @ray20  Yes, we can do this from the Automation steps from customization packages.

We can add conditions to enable/disable the fields at automation steps in the Customization package. Please find the screenshot for reference.

Hi @ray20 

We can add the condition like below on the SOLine_Rowselected event or we can use the Automation steps.

            PXUIFieldAttribute.SetEnabled<SOLine.curyUnitPrice>(cache, soLine, soLineExt.CWI == true);
            PXUIFieldAttribute.SetEnabled<SOLineExt.usrPricePerLB>(cache, soLine, soLineExt.CWI == true);

You can conditionally enable / disable fields with the PXUIEnabled attribute. You can either add the attribute via the CacheAttached event, or for custom fields, right in the field definition. Since you’re working with one of each, I’d suggest you use the CacheAttached event.

public class SOOrderEntry_Extension : PXGraphExtension<SOOrderEntry>
{
    #region Event Handlers

    /PXUIEnabled(typeof(Where<SOLineExt.cWI.IsEqual<False>>))]
    protected virtual void _(Events.CacheAttached<PX.Objects.SO.SOLine.curyUnitPrice> e)
    { }

    /PXUIEnabled(typeof(Where<SOLineExt.cWI.IsEqual<True>>))]
    protected virtual void _(Events.CacheAttached<PX.Objects.SO.SOLineExt.usrPricePerLB> e)
    { }

    #endregion
}

Hello @Naveen Boga @darylbowman @jinin 
Thank you all, nice to have your help.
Since I am not good at coding, I will try Naveen’s method first. Still, really appreciated. Thank you.

@Naveen Boga @jinin 
Hello, the “conditions” in the automation steps, firstly , it can not be on a line level? 
And secondly, it seems it can not support Customized field?

Hi @ray20   Yes, that is correct.

If you are going with the custom fields, better go with the code-level customization. Make sure like if you are going with RowSelected event then only Enable/Disable code should be present. 

Or also, you can do with  PXUIEnabled attribute → CacheAttached event.

@Naveen Boga 
Thank you buddy. 
1,   Do you know which is having higher/faster performance?
In Rowselected event or in CacheAttached event?
If user is planning to key in more than 30 solines on SO entry screen.

2,  I am not good at coding, so please help
for 
protected virtual void _(Events.CacheAttached<PX.Objects.SO.SOLine.curyUnitPrice> e) { }
 

it seems to me ,should be

protected virtual void _(Events.CacheAttached<PX.Objects.SO.SOLine.curyUnitPrice> e)

{

}

Or I shall put another codes in the {} body?

@ray20  Both events are the same according to me. 

When any changes happen both events will be triggered and run the code. You can go with any of those approaches.

This code is already above by dary and you can use this.

public class SOOrderEntry_Extension : PXGraphExtension<SOOrderEntry>
{
    #region Event Handlers

     PXUIEnabled(typeof(Where<SOLineExt.cWI.IsEqual<False>>))]
    protected virtual void _(Events.CacheAttached<PX.Objects.SO.SOLine.curyUnitPrice> e)
    { }

     PXUIEnabled(typeof(Where<SOLineExt.cWI.IsEqual<True>>))]
    protected virtual void _(Events.CacheAttached<PX.Objects.SO.SOLineExt.usrPricePerLB> e)
    { }

    #endregion
}

@Naveen Boga  Yes, I saw the codes. So that’s why I am a poor coder.

Why the event body {} is empty.  Shall we just leave it empty?
 

@ray20  Yes please, leave it empty.

@darylbowman @Naveen Boga 
Hello Coding Pros,
Thank you for your help. Let me update
1, Dary’s code is working. However, since IF both rowselected and cacheattahced events having same performance, I fininally choose to still keep codes in rowselected.
Because it has been tested and run for years without function issues.
And besides making disable or enable, we have still to make a equation that
UnitPrice =  PricebyLB * avgweight,    
so, I decided to do it in rowselected.

2, Upgarding the CPU solved our performance issue.

Still , thank you for your guidance.  Really appreciated to have you guys around.