Allow on Submit disabled for standard fields

ERPNext
1

Hi All,

I was looking for some input on my comment I posted to issue #956

I’ll repeat what I wrote on the closed ticket;

I recently upgraded my deployment, and I have been burned by this change. We use the PO no standard field on Sales Order’s. We often get the PO number a couple days after a order has been placed, so we need to update the SO after it is submitted.

Is the only solution to stop using the PO no standard field, and use a custom PO fields instead? I’m reluctant to add a custom field when a standard field already exists.

Thanks,

https://github.com/frappe/erpnext/issues/956

2

I would use a custom field. Or maybe the PO NO can be editable on submit in the standard document.

We stopped users from changing allow on submit, because was being misused and used to cause us headaches in trying to fix the issues.

1 Like