Project Pro forma Custom fields enabled when status is closed

Hi @lbarker ,

We can enable the fields using workflow. 

Please refer to the below link
2021 R1 Enable Locked Fields | Community (acumatica.com)

That did not work, hence why I did code for this screen.  

This blog post has slightly different code than you have (aside from running on a different graph). Naveen is setting Base.Document.Cache.AllowUpdate to true along with Base.Transactions.Cache. But he is not calling SetEnabled on the whole row, just the required fields.

He also mentioned needing to do changes in the workflow as well.

Hopefully that helps!

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

Thanks so much but it also does not work, as if I don’t enable the row first, it leaves the custom fields disabled so something is different with this screen, so this was the only solution.   

Hoping someone worked out how to do this on this screen.

Hi @lbarker 

Have you tried:

if(row.Status != “C”)

{

PXUIFieldAttribute.SetEnabled(cache, row, true);

       PXUIFieldAttribute.SetEnabled<PMProformaLineExt.usrMAnoteID>(cache, row, true);

        PXUIFieldAttribute.SetEnabled<PMProformaLineExt.usrMAflag>(cache, row, true);

}

Also, if this is not a custom screen, you should override the event handler e.g., _(Events.RowSelected<PMProformaTransactLine> e, PXRowSelected b)

Hope this helps!

Aleks

Hi @lbarker 

You will also need to add the following line into your code to get the DAC extension.

PMProformaTransactLine rowExt = PXCache<PMProformaTransactLine>.GetExtension<PMProformaTransactLineExt>(row);

Aleks

Hi @lbarker were you able to find a solution? Thank you!

Would like a solution to this as well.

You most likely should not be setting the whole row as enabled. Have you gone into the workflow and made a custom workflow extension and added your custom fields for the states that you want them to be enabled in? That should accomplish what you are looking for, you often need to make the change in the workflow.

​@Josiah Lisle is right.

In having to enable the custom field in closed state, I suppose all the fields have been enabled in the closed state. In this case, individual field states should be set through the extended workflow.

For example, here on the extended defaultv1 workflow, on closed status, the invoice date field is disabled. Similarly, other fields can be disabled.
 

Hi

Yes I did try this, but its as though the workflow does not apply at all.  I tried also to enable the line in code too and then in the workflow to disable the other fields, and also does not work.

I would recommend to unpublish all customizations, restart your instance, and verify that the behavior has returned to the system default.

Then I would recommend creating an entirely new customization package, extending the workflow, go into the extended workflow and add the specific field you want to enable in that status, as ​@varthinibhaskaran18 suggested. Then make sure you set this workflow extension as active, and publish this customization.