Skip to main content
Solved

Making the header level field as editable irrespective of the statuses

  • September 3, 2024
  • 3 replies
  • 33 views

Forum|alt.badge.img
  • Semi-Pro II
  • 247 replies

Hello all,

I have been trying to make a field remain as editable irrespective of the statuses of the document.

I added this custom field → overridden the workflow
 

I am figuring out the code that would be required to be added in order to make this field as editable.

Best answer by aiwan

Hi @Harry 

 

This is more of the coding route rather than Low Code/No Code but here is an example:

protected virtual void _(Events.RowSelected<YourDac> e, PXRowSelectedArgs b)
{
YourDac row = e.Row;  //Get current record from Cache
if(row == null) return; 

b?.Invoke(e.Cache, e.Args); //Invoke base handler if there is one.

PXUIField.SetEnabled<YourDac.yourField>(e.Cache, e.Row, true); //Set the field enabled, regardless of any conditions.

}

Hope this helps, be careful as this will leave the field open to edit at all times.

Aleks

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

3 replies

Forum|alt.badge.img+8
  • Captain II
  • 366 replies
  • Answer
  • September 3, 2024

Hi @Harry 

 

This is more of the coding route rather than Low Code/No Code but here is an example:

protected virtual void _(Events.RowSelected<YourDac> e, PXRowSelectedArgs b)
{
YourDac row = e.Row;  //Get current record from Cache
if(row == null) return; 

b?.Invoke(e.Cache, e.Args); //Invoke base handler if there is one.

PXUIField.SetEnabled<YourDac.yourField>(e.Cache, e.Row, true); //Set the field enabled, regardless of any conditions.

}

Hope this helps, be careful as this will leave the field open to edit at all times.

Aleks


Forum|alt.badge.img+8
  • Captain II
  • 366 replies
  • September 3, 2024

@Harry 

 

Forgot to mention, this will need to be inserted in a graph extension of the graph that controls your screen.


Naveen Boga
Captain II
Forum|alt.badge.img+19
  • Captain II
  • 3407 replies
  • September 3, 2024

@Harry  I wrote the article below a while ago, and with this change, modifications will be required in both the Workflows and the code (specifically the RowSelected event). This article should help with your requirements. Please feel free to reach out if you need any assistance.

 

https://asiablog.acumatica.com/2021/10/enable-customization-fields-when-document-is-completed.html


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