I don't know if already reported but i just notized that there is a problem with the default print formats.
For example the 'Body: width: 8.3in;'-print property disturbs the default forms when they are attached as communication record.
I did sent an invoice as mail and when later i try to switch from print view to details view for this invoice the forms layout and design is influenced by the print formats.
Ii added a global classes and moved styles from body, html and etc to prevent from this.
Best regards, Sören
–
You received this message because you are subscribed to the Google Groups "ERPNext User's Forum" group.
Its a known issue - we should have not used global css styles for the print formats. Its on our list to re-write. Ideally print formats should be on the server side (because you may want to get them via an API). The architecture is already implemented, its only a matter of converting the existing formats. Should be done in a month or so.
I don't know if already reported but i just notized that there is a problem with the default print formats.
For example the 'Body: width: 8.3in;'-print property disturbs the default forms when they are attached as communication record.
I did sent an invoice as mail and when later i try to switch from print view to details view for this invoice the forms layout and design is influenced by the print formats.
Ii added a global classes and moved styles from body, html and etc to prevent from this.
Best regards, Sören
–
You received this message because you are subscribed to the Google Groups “ERPNext User’s Forum” group.
Sorry i may have over overlooked it in githubs issue list.
two other things that i have senn thins morning:
- yesterday yout introduced the new single notification Center: wouln'd it be usefull to have a notification symbol for calender module if there is a calender item today?
- #323 on the issues list is delivery note: but i think this is maybe no question of doctype. I have the case that i will need to implement recurring orders. They will be generated in draft state an include a common pool of items that will be ordern e.g. every day or week. this orders get customized with special items order special qty's and then be submitted to production.
So it maybe usefull if possible to have some abstract recurring/periodic function e.g. at the actions menu of any doctype before making lots of individual implementations like for sales invoice.
Best regards,
Sören
–
You received this message because you are subscribed to the Google Groups "ERPNext User's Forum" group.
- yesterday yout introduced the new single notification Center: wouln'd it be usefull to have a notification symbol for calender module if there is a calender item today?
Already there.
- #323 on the issues list is delivery note: but i think this is maybe no question of doctype. I have the case that i will need to implement recurring orders. They will be generated in draft state an include a common pool of items that will be ordern e.g. every day or week. this orders get customized with special items order special qty's and then be submitted to production.
You can write a small python script for this using the API (webnotes.client) and call it using the scheduler (cron) - it should not be too hard. You can write a small post on this too ;-)
So it maybe usefull if possible to have some abstract recurring/periodic function e.g. at the actions menu of any doctype before making lots of individual implementations like for sales invoice.
True can be done - but its non-trivial and there is a big list pending (like Print Formats!)
Best regards,
Sören
–
You received this message because you are subscribed to the Google Groups “ERPNext User’s Forum” group.
On Wednesday, June 19, 2013 8:26:28 AM UTC+2, Rushabh Mehta wrote:
two other things that i have senn thins morning:
- yesterday yout introduced the new single notification Center: wouln’d it be usefull to have a notification symbol for calender module if there is a calender item today?
Already there.
seems i came flatfooted.
- #323 on the issues list is delivery note: but i think this is maybe no question of doctype. I have the case that i will need to implement recurring orders. They will be generated in draft state an include a common pool of items that will be ordern e.g. every day or week. this orders get customized with special items order special qty’s and then be submitted to production.
You can write a small python script for this using the API (webnotes.client) and call it using the scheduler (cron) - it should not be too hard. You can write a small post on this too
Will do that.
So it maybe usefull if possible to have some abstract recurring/periodic function e.g. at the actions menu of any doctype before making lots of individual implementations like for sales invoice.
True can be done - but its non-trivial and there is a big list pending (like Print Formats!)
:-) should’nt be any request - simply wanted to know if theres something like that planned or already in progress.
Best regards,
Sören
–
You received this message because you are subscribed to the Google Groups “ERPNext User’s Forum” group.
