Skip to main content
Solved

Customizing an Existing Enquiry Screen ( Project Transaction Details)

  • May 15, 2023
  • 1 reply
  • 274 views

Hello 

I am working on customization screen ( Project Transaction Details) 



I want to add new selector field to the exisintg Enquiry screen. The problem I am facing is 

1)  The  exsiting acumatica DAC Filter values, they are hidden  and in same graph(TransactionInquiry)
2) When I try to extend this filter and add new filter (i.e a new selector), it is not showing in my customization screen.
3) I feel, as existing fields are all unbound and its hidden, my newly added  extended dac filter selector is not exposed and does not recognize the TranFilter DAC. 



        [PXHidden]
        [Serializable]
        [System.Diagnostics.CodeAnalysis.ExcludeFromCodeCoverage]
        public class TranFilter : IBqlTable
        {
            #region ProjectID
            public abstract class projectID : PX.Data.BQL.BqlInt.Field<projectID> { }
            protected Int32? _ProjectID;
            [Project(typeof(Where<PMProject.baseType, Equal<CT.CTPRType.project>,              And<PMProject.nonProject, Equal<False>>>), WarnIfCompleted = false)]

            #endregion

            #region AccountGroupID
    ……………………..
            #endregion
            #region ProjectTaskID
    ……………………..
            #endregion
            #region CostCode
    ……………………..
            #endregion

   ……………………...
       }

 

Could anyone please help me and suggest the best practice ,
1) Add new field value( a selector dac) via extending this TranFilter DAC, and I want my new selector to behave just like projectID field.
2) have it in use via extenidng the  graph via delegate
 

 

Best answer by aaghaei

DACs that we use in PXFilter ALL are hidden and this is NOT an exception. I assume this is what you have done:

  1. you have added a DAC Extension to “TranFilter”
  2. you have added a custom field to this DAC Ext and have set its properties including PXSelector property.
  3. You have revised the associated query to account for the newly added filter field. 
  4. You have added this new field to the header of the Project Transaction Details Inquiry screen and set its commit change to True to force refresh the screen when its value changes.

So please provide your customization code and package that includes the above items so that we can have a look.

View original
Did this topic help you find an answer to your question?

1 reply

aaghaei
Captain II
Forum|alt.badge.img+10
  • Captain II
  • 1202 replies
  • Answer
  • May 15, 2023

DACs that we use in PXFilter ALL are hidden and this is NOT an exception. I assume this is what you have done:

  1. you have added a DAC Extension to “TranFilter”
  2. you have added a custom field to this DAC Ext and have set its properties including PXSelector property.
  3. You have revised the associated query to account for the newly added filter field. 
  4. You have added this new field to the header of the Project Transaction Details Inquiry screen and set its commit change to True to force refresh the screen when its value changes.

So please provide your customization code and package that includes the above items so that we can have a look.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings