I want to set a restriction that won't allow users to set the resolution_date in Customer Issue to a date back in time. Is there a client script I can follow to do this?
The logic would be upon saving:
If resolution_date is not empty then if resolution_date is < today do not save, else save, else save
–
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.
msgprint("Sales Order Date cannot be a past date"); // or any other message you want..
}
}
}
The doc.transaction_date is the name of the field in which you want to add the restriction. Now the problem with client script is that it would check the date of the Client's computer with the date selected and not the actual date on the server, but still I think this works well.
I hope you are able to understand the code, if you have any questions do let me know.
On Sat, Nov 23, 2013 at 3:29 PM, lxnow <la…@union.ph> wrote:
I want to set a restriction that won't allow users to set the resolution_date in Customer Issue to a date back in time. Is there a client script I can follow to do this?
The logic would be upon saving:
If resolution_date is not empty then if resolution_date is < today do not save, else save, else save
–
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.
msgprint("Sales Order Date cannot be a past date"); // or any other message you want..
}
}
}
The doc.transaction_date is the name of the field in which you want to add the restriction. Now the problem with client script is that it would check the date of the Client’s computer with the date selected and not the actual date on the server, but still I think this works well.
I hope you are able to understand the code, if you have any questions do let me know.
On Sat, Nov 23, 2013 at 3:29 PM, lxnow <la…@union.ph> wrote:
I want to set a restriction that won't allow users to set the resolution_date in Customer Issue to a date back in time. Is there a client script I can follow to do this?
The logic would be upon saving:
If resolution_date is not empty then if resolution_date is < today do not save, else save, else save
–
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.
msgprint("Sales Order Date cannot be a past date"); // or any other message you want..
}
}
}
The doc.transaction_date is the name of the field in which you want to add the restriction. Now the problem with client script is that it would check the date of the Client's computer with the date selected and not the actual date on the server, but still I think this works well.
I hope you are able to understand the code, if you have any questions do let me know.
On Sat, Nov 23, 2013 at 3:29 PM, lxnow <la…@union.ph> wrote:
I want to set a restriction that won't allow users to set the resolution_date in Customer Issue to a date back in time. Is there a client script I can follow to do this?
The logic would be upon saving:
If resolution_date is not empty then if resolution_date is < today do not save, else save, else save
–
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.
To unsubscribe from this group and stop receiving emails from it, send an email to erpnext-developer-forum+un...@googlegroups.com.
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.
msgprint("Sales Order Date cannot be a past date"); // or any other message you want..
}
}
}
The doc.transaction_date is the name of the field in which you want to add the restriction. Now the problem with client script is that it would check the date of the Client’s computer with the date selected and not the actual date on the server, but still I think this works well.
I hope you are able to understand the code, if you have any questions do let me know.
On Sat, Nov 23, 2013 at 3:29 PM, lxnow <la…@union.ph> wrote:
I want to set a restriction that won't allow users to set the resolution_date in Customer Issue to a date back in time. Is there a client script I can follow to do this?
The logic would be upon saving:
If resolution_date is not empty then if resolution_date is < today do not save, else save, else save
–
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.
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.
The script below works on the resolution_date field for an existing Customer Issue, but it seems to be needing something else to allow for saving the issue if it resolution_date is blank (i.e. the issue has not yet been resolved).
msgprint("Sales Order Date cannot be a past date"); // or any other message you want..
}
}
}
The doc.transaction_date is the name of the field in which you want to add the restriction. Now the problem with client script is that it would check the date of the Client’s computer with the date selected and not the actual date on the server, but still I think this works well.
I hope you are able to understand the code, if you have any questions do let me know.
On Sat, Nov 23, 2013 at 3:29 PM, lxnow <la…@union.ph> wrote:
I want to set a restriction that won't allow users to set the resolution_date in Customer Issue to a date back in time. Is there a client script I can follow to do this?
The logic would be upon saving:
If resolution_date is not empty then if resolution_date is < today do not save, else save, else save
–
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.
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.
if (doc.resolution_date && wn.datetime.get_day_diff(new Date(), wn.datetime.str_to_obj(doc.resolution_date)) > 0) {
validated = false;
msgprint("Resolution Date cannot be a past date"); // or any other message you want..
}
The script below works on the resolution_date field for an existing Customer Issue, but it seems to be needing something else to allow for saving the issue if it resolution_date is blank (i.e. the issue has not yet been resolved).
msgprint("Sales Order Date cannot be a past date"); // or any other message you want..
}
}
}
The doc.transaction_date is the name of the field in which you want to add the restriction. Now the problem with client script is that it would check the date of the Client's computer with the date selected and not the actual date on the server, but still I think this works well.
I hope you are able to understand the code, if you have any questions do let me know.
On Sat, Nov 23, 2013 at 3:29 PM, lxnow <la…@union.ph> wrote:
I want to set a restriction that won't allow users to set the resolution_date in Customer Issue to a date back in time. Is there a client script I can follow to do this?
The logic would be upon saving:
If resolution_date is not empty then if resolution_date is < today do not save, else save, else save
–
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.
To unsubscribe from this group and stop receiving emails from it, send an email to erpnext-developer-forum+unsubscr...@googlegroups.com.
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.
To unsubscribe from this group and stop receiving emails from it, send an email to erpnext-developer-forum+un...@googlegroups.com.
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.
Thanks Max! I think I got the logic... both values
1. resolution_date
2. get_day_diff (subtracts current date and doc.resolution_date)
must be more than 0 for the error to appear. Otherwise, it lets the form save.
On Saturday, November 23, 2013 10:40:01 PM UTC+8, Maxwell wrote:
Try it
if (doc.resolution_date && wn.datetime.get_day_diff(new Date(), wn.datetime.str_to_obj(doc.resolution_date)) > 0) {
validated = false;
msgprint("Resolution Date cannot be a past date"); // or any other message you want..
}
The script below works on the resolution_date field for an existing Customer Issue, but it seems to be needing something else to allow for saving the issue if it resolution_date is blank (i.e. the issue has not yet been resolved).
msgprint("Sales Order Date cannot be a past date"); // or any other message you want..
}
}
}
The doc.transaction_date is the name of the field in which you want to add the restriction. Now the problem with client script is that it would check the date of the Client’s computer with the date selected and not the actual date on the server, but still I think this works well.
I hope you are able to understand the code, if you have any questions do let me know.
On Sat, Nov 23, 2013 at 3:29 PM, lxnow <la…@union.ph> wrote:
I want to set a restriction that won't allow users to set the resolution_date in Customer Issue to a date back in time. Is there a client script I can follow to do this?
The logic would be upon saving:
If resolution_date is not empty then if resolution_date is < today do not save, else save, else save
–
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.
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.
I’m just checking if there is some value, yes, the next condition must be performed, for this I use the AND &&, you can also use the OR operator || if you need at any time.
Thanks Max! I think I got the logic... both values
1. resolution_date
2. get_day_diff (subtracts current date and doc.resolution_date)
must be more than 0 for the error to appear. Otherwise, it lets the form save.
On Saturday, November 23, 2013 10:40:01 PM UTC+8, Maxwell wrote:
Try it
if (doc.resolution_date && wn.datetime.get_day_diff(new Date(), wn.datetime.str_to_obj(doc.resolution_date)) > 0) {
validated = false;
msgprint("Resolution Date cannot be a past date"); // or any other message you want..
}
The script below works on the resolution_date field for an existing Customer Issue, but it seems to be needing something else to allow for saving the issue if it resolution_date is blank (i.e. the issue has not yet been resolved).
msgprint("Sales Order Date cannot be a past date"); // or any other message you want..
}
}
}
The doc.transaction_date is the name of the field in which you want to add the restriction. Now the problem with client script is that it would check the date of the Client's computer with the date selected and not the actual date on the server, but still I think this works well.
I hope you are able to understand the code, if you have any questions do let me know.
On Sat, Nov 23, 2013 at 3:29 PM, lxnow <la…@union.ph> wrote:
I want to set a restriction that won't allow users to set the resolution_date in Customer Issue to a date back in time. Is there a client script I can follow to do this?
The logic would be upon saving:
If resolution_date is not empty then if resolution_date is < today do not save, else save, else save
–
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.
To unsubscribe from this group and stop receiving emails from it, send an email to erpnext-developer-forum+unsubscr...@googlegroups.com.
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.
To unsubscribe from this group and stop receiving emails from it, send an email to erpnext-developer-forum+unsubscr...@googlegroups.com.
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.
To unsubscribe from this group and stop receiving emails from it, send an email to erpnext-developer-forum+un...@googlegroups.com.
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.
I found a workflow problem with this set up in that I realize we have a status called "For Customer Pick-Up" before a Customer Issue is actually "Closed". So when a Customer Issue is changed status from "For Customer Pick-Up" to "Closed", the back-dating condition should not apply. If any one has ideas, it would be appreciated. Thanks.
On Saturday, November 23, 2013 11:13:58 PM UTC+8, Maxwell wrote:
Yes, but when I do see
doc.resolution_date
I’m just checking if there is some value, yes, the next condition must be performed, for this I use the AND &&, you can also use the OR operator || if you need at any time.
Thanks Max! I think I got the logic... both values
1. resolution_date
2. get_day_diff (subtracts current date and doc.resolution_date)
must be more than 0 for the error to appear. Otherwise, it lets the form save.
On Saturday, November 23, 2013 10:40:01 PM UTC+8, Maxwell wrote:
Try it
if (doc.resolution_date && wn.datetime.get_day_diff(new Date(), wn.datetime.str_to_obj(doc.resolution_date)) > 0) {
validated = false;
msgprint("Resolution Date cannot be a past date"); // or any other message you want..
}
The script below works on the resolution_date field for an existing Customer Issue, but it seems to be needing something else to allow for saving the issue if it resolution_date is blank (i.e. the issue has not yet been resolved).
msgprint("Sales Order Date cannot be a past date"); // or any other message you want..
}
}
}
The doc.transaction_date is the name of the field in which you want to add the restriction. Now the problem with client script is that it would check the date of the Client’s computer with the date selected and not the actual date on the server, but still I think this works well.
I hope you are able to understand the code, if you have any questions do let me know.
On Sat, Nov 23, 2013 at 3:29 PM, lxnow <la…@union.ph> wrote:
I want to set a restriction that won't allow users to set the resolution_date in Customer Issue to a date back in time. Is there a client script I can follow to do this?
The logic would be upon saving:
If resolution_date is not empty then if resolution_date is < today do not save, else save, else save
–
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.
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.
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.
Yes, When you change from “Closed” to “For Customer Pick-up”, the doc.resolution_date already have a value then you should the value to null, with a custom event on status see below
I found a workflow problem with this set up in that I realize we have a status called "For Customer Pick-Up" before a Customer Issue is actually "Closed". So when a Customer Issue is changed status from "For Customer Pick-Up" to "Closed", the back-dating condition should not apply. If any one has ideas, it would be appreciated. Thanks.
On Saturday, November 23, 2013 11:13:58 PM UTC+8, Maxwell wrote:
Yes, but when I do see
doc.resolution_date
I’m just checking if there is some value, yes, the next condition must be performed, for this I use the AND &&, you can also use the OR operator || if you need at any time.
Thanks Max! I think I got the logic... both values
1. resolution_date
2. get_day_diff (subtracts current date and doc.resolution_date)
must be more than 0 for the error to appear. Otherwise, it lets the form save.
On Saturday, November 23, 2013 10:40:01 PM UTC+8, Maxwell wrote:
Try it
if (doc.resolution_date && wn.datetime.get_day_diff(new Date(), wn.datetime.str_to_obj(doc.resolution_date)) > 0) {
validated = false;
msgprint("Resolution Date cannot be a past date"); // or any other message you want..
}
The script below works on the resolution_date field for an existing Customer Issue, but it seems to be needing something else to allow for saving the issue if it resolution_date is blank (i.e. the issue has not yet been resolved).
msgprint("Sales Order Date cannot be a past date"); // or any other message you want..
}
}
}
The doc.transaction_date is the name of the field in which you want to add the restriction. Now the problem with client script is that it would check the date of the Client's computer with the date selected and not the actual date on the server, but still I think this works well.
I hope you are able to understand the code, if you have any questions do let me know.
On Sat, Nov 23, 2013 at 3:29 PM, lxnow <la…@union.ph> wrote:
I want to set a restriction that won't allow users to set the resolution_date in Customer Issue to a date back in time. Is there a client script I can follow to do this?
The logic would be upon saving:
If resolution_date is not empty then if resolution_date is < today do not save, else save, else save
–
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.
To unsubscribe from this group and stop receiving emails from it, send an email to erpnext-developer-forum+unsubscr...@googlegroups.com.
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.
To unsubscribe from this group and stop receiving emails from it, send an email to erpnext-developer-forum+unsubscr...@googlegroups.com.
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.
To unsubscribe from this group and stop receiving emails from it, send an email to erpnext-developer-forum+unsubscr...@googlegroups.com.
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.
To unsubscribe from this group and stop receiving emails from it, send an email to erpnext-developer-forum+un...@googlegroups.com.
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.
