Do a PR but i'm not sure because an invoice, as a legal document, should have
a date (not depending of a timzezone) and it's numbering should be sequencial
(no gaps). Whereas a PO is a internal document that can have a timestamp and
holes in it's numbering.
On 07/09/2014 03:59 AM, Nhomar Hernández wrote:
2014-07-08 19:11 GMT-04:30 Antony Lesuisse <[email protected]
<mailto:[email protected]>>:
with a mixin to save those fields on crm.lead and sale.order. This is
required to track google adwords campains on lead generation and
e-commerce shopping carts.
- on purchase.order chaging the date into a datetime (not sure it's merged
yet).
If you put [email protected] datetime for electronic invoicing, I will
bless you all my life ;-)
We have 4 years dealing with a monkey patch + change 1 file for 3
localizations ;-)
I can make a PR+tests if you tell me you will approve this change.
FYI, merged or not, We must do that, than it can be better merged obviously.
[1]
http://bazaar.launchpad.net/~openerp-mexico-maintainer/openerp-mexico-localization/trunk/view/head:/l10n_mx_invoice_datetime/account_invoice_view.xml
[2]
http://bazaar.launchpad.net/~openerp-mexico-maintainer/openerp-mexico-localization/trunk/view/head:/l10n_mx_invoice_datetime/invoice.py
--
--------------------
Saludos Cordiales
Nhomar G. Hernandez M.
+58-414-4110269
Skype: nhomar00
Web-Blog: http://geronimo.com.ve <http://geronimo.com.ve/>
Servicios IT: http://vauxoo.com <http://vauxoo.com/>
Linux-Counter: 467724
Correos:
[email protected] <mailto:[email protected]>
[email protected] <mailto:[email protected]>
twitter @nhomar
_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to : [email protected]
Unsubscribe : https://launchpad.net/~openerp-community
More help : https://help.launchpad.net/ListHelp