Hello,
We have to merge this branch as soon as possible because the modules here are
no longer present in the extra-addons branch.
I am going to remove the product_gs1_128 module from the branch because it is
now clear that it will be in lp:stock-logistic-barcode thanks to Numérigraphe.
By the
Que tal comunidad
Les dejo un video de la localizacion mexicana para la nomina en la version 7
del openerp
http://youtu.be/Tihem1YGXio
Programing Solution
Nuestra pasion
Ustedes la conocen como programacion
evi...@hotmail.com
Eduardo Vizcaino Granados
Dios nos dio el 0 y el 1
para que prog
Another remark that I'm surprised nobody raised is that you have a checkbox
"Customer" in the "Sales & Purchases" tab of the contact form. If you have a
warehouse, it is not a customer so this checkbox should be unchecked. Hence, it
will not be possible to select it in the customer m2o field in
Hello,
It's quite easy to add a relationship between contacts to simulate the
features of base_contact on v7. Or to allow several level of parents
instead of only one. (as the structure is already a real tree structure)
We already promised such a module to some OpenERP Enterprise customers
using
Hello,
Both approaches have their advantages and disadvantages. We have adjusted
our addons in preparation for 7.0 and in the beginning there was some
doubt about it, but now we like it. The possibility to make sales to
consumers is a plus. In our examples however, we miss the possibility to
conne
The proposal to merge lp:~openerp-chinese-team/openobject-doc/Chinese-init into
lp:~openerp-community/openobject-doc/6.1 has been updated.
Status: Needs review => Merged
For more details, see:
https://code.launchpad.net/~openerp-chinese-team/openobject-doc/Chinese-init/+merge/137749
--
http
Review: Approve
On 12/04/2012 01:54 PM, Joshua Jan(SHINEIT) wrote:
> We want use the "zh_CN" because there is three language(zh_CN, zh_TW, zh_HK)
> in Chinese. They are different.
Alright, I can see how it might confuse people if we simply used "zh", even
though there may only be one Chinese tr
Hi Olivier,
Thanks for your reply. :)
We want use the "zh_CN" because there is three language(zh_CN, zh_TW, zh_HK)
in Chinese. They are different.
Yes actually plan to translate and maintain the OpenERP documentation in
Chinese. We have a branch in github to translate the
document.(
i am not sure about the entry. potentially you have several locations for
Chinese. i would tend to follow Joshua s advice.
Eric
"Olivier Dony (OpenERP)" wrote:
>Review: Needs Information
>
>Hi Joshua,
>
>Thanks for contributing to the OpenERP documentation/translation!
>
>Would you mind if we
Review: Needs Information
Hi Joshua,
Thanks for contributing to the OpenERP documentation/translation!
Would you mind if we renamed the "zh_CN" subdirectory to just "zh" in order to
be consistent with the naming of the other translations? (can be done when
merging your proposal)
Bonus questio
Hello,
This reminds my of my craints when i got to know that base_contact was
removed from 6.2 branch. Anybody else concerned with the base_contact
approach for 7.0?
On 24.08.12 I sent to the list the following Email text:
> The location in 6.1 was a good approach as the address remained the
> o
Hello,
This is a big deal of troubles... No answer yet, but we/they need to find a
way. Same mess with invoice reconciliation... Make a SO, choose a partner A
(company checked) as SO's partner, partner B as an invoice address, then you
cannot reconcile both. Payment will have to be made by par
Hi Nhomar,
I will say it's better to create a new project for such a topic, add it as part
of Openobject LP project and put an entry in the doc.openerp.com.
Sounds good to you ?
Regards,
Joël
Le 30 nov. 2012 à 16:18, Nhomar Hernández a écrit :
> Hello everyone.
>
> We will prepare a dem
Hello,
I definitely agree. Now maybe 7.0 has a model that works for B2C but B2B is
warped back to the stone age.
I doubt the community was in favor of this turnaround seen the effort we all
have to put in migrating our customer's partner information.
Normalization was introduced for a reason
14 matches
Mail list logo
