There's this useful behavior wherein when a sales order is entered, ERPNext checks if the field po_no (customer Purchase Order) is already entered in the system, then it pops up a warning message for the user to double-check.
Is this behavior possible to replicate via custom client script (on hosted version) for a custom field?
If so, any tips on where to start looking for scripts would be helpful. Thanks!
–
Note:
If you are posting an issue,
We should be able to replicate it at our end. So please give us as much information as you can. Please see it from the point of view of the person receiving the communication.
For sending images, use http://imgur.com or other similar services. Do not send images as attachments. Links are good. Same goes for any file you are going to send.
End of Note
—
You received this message because you are subscribed to the Google Groups "ERPNext Developer Forum" group.
When inserting new Custom Field, system checks if there is custom/standard field already existing in with the same name. If field with the same name is found, system raises validation message.
On Thu, Dec 5, 2013 at 9:23 AM, lxnow <la...@union.ph> wrote:
There's this useful behavior wherein when a sales order is entered, ERPNext checks if the field po_no (customer Purchase Order) is already entered in the system, then it pops up a warning message for the user to double-check.
Is this behavior possible to replicate via custom client script (on hosted version) for a custom field?
If so, any tips on where to start looking for scripts would be helpful. Thanks!
–
Note:
If you are posting an issue,
We should be able to replicate it at our end. So please give us as much information as you can. Please see it from the point of view of the person receiving the communication.
For sending images, use http://imgur.com or other similar services. Do not send images as attachments. Links are good. Same goes for any file you are going to send.
End of Note
—
You received this message because you are subscribed to the Google Groups "ERPNext Developer Forum" group.
We should be able to replicate it at our end. So please give us as much information as you can. Please see it from the point of view of the person receiving the communication.
For sending images, use http://imgur.com or other similar services. Do not send images as attachments. Links are good. Same goes for any file you are going to send.
End of Note
—
You received this message because you are subscribed to the Google Groups "ERPNext Developer Forum" group.
Sorry for the wrong response. Please disregard my last message. You can expect to hear from our technical expert for help on this.
On Thu, Dec 5, 2013 at 9:23 AM, lxnow <la...@union.ph> wrote:
There's this useful behavior wherein when a sales order is entered, ERPNext checks if the field po_no (customer Purchase Order) is already entered in the system, then it pops up a warning message for the user to double-check.
Is this behavior possible to replicate via custom client script (on hosted version) for a custom field?
If so, any tips on where to start looking for scripts would be helpful. Thanks!
–
Note:
If you are posting an issue,
We should be able to replicate it at our end. So please give us as much information as you can. Please see it from the point of view of the person receiving the communication.
For sending images, use http://imgur.com or other similar services. Do not send images as attachments. Links are good. Same goes for any file you are going to send.
End of Note
—
You received this message because you are subscribed to the Google Groups "ERPNext Developer Forum" group.
We should be able to replicate it at our end. So please give us as much information as you can. Please see it from the point of view of the person receiving the communication.
For sending images, use http://imgur.com or other similar services. Do not send images as attachments. Links are good. Same goes for any file you are going to send.
End of Note
—
You received this message because you are subscribed to the Google Groups "ERPNext Developer Forum" group.