Allow on Submit: use cases

[lxnow]

Just curious how this field option "Allow on Submit" can be useful to others.  I find it useful in correcting payments matching once a payment has been recorded and submitted. However, we keep this unticked by default because we do not want users to just change payment records at anytime.

[Nabin Hait]

Don't use "Allow on Submit" feature for payment matching. It will only update against voucher in Journal Voucher, but not update corresponding GL Entry and outstanding amount in the related invoice. So, even if you updated "Against" field after submission, that will not reflect in Sales/Purchase Register report.

On 07-Oct-2013, at 8:07 AM, lxnow wrote:

Just curious how this field option "Allow on Submit" can be useful to others.  I find it useful in correcting payments matching once a payment has been recorded and submitted. However, we keep this unticked by default because we do not want users to just change payment records at anytime.

--
You received this message because you are subscribed to the Google Groups "ERPNext User's Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to erpnext-user-fo...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[lxnow]

Ah... HAve to roll-back the changes we made then. Thanks for informing.

To unsubscribe from this group and stop receiving emails from it, send an email to erpnext-user-forum+unsub...@googlegroups.com.

[lxnow]

Also noticed that posting date also isn't updated when it is modified after submit (for purchase invoices).

So what is the use case for this option?

[lxnow]

Just to be clear, when I said "posting date also isn't update", I am actually referring to the AGING value found in the A/P main report, which does not update. So the proper way to correct an incorrectly dated PI is to cancel and reinvoice (which makes sense)... still I'm wondering why there's this option in the first place.

[Nabin Hait]

Posting Date also can not be set as "Allow on Submit". We will remove the option of "Allow on Submit" for standard fields through Customize Form.

We have created an github issue for this (https://github.com/webnotes/erpnext/issues/956)

To unsubscribe from this group and stop receiving emails from it, send an email to erpnext-user-fo...@googlegroups.com.

[lxnow]

Thanks for clarifying. Say we set a field with "Allow on Submit", what kind of permission does a user need to have in order to edit the field after submission? I am looking at use cases where a field becomes read-only upon submission, while having a sub-set of users with higher privileges be able to change when needed (e.g. correcting typographical errors).