[19.0][MIG] delivery_gls_asm: Migration to 19.0#4685
[19.0][MIG] delivery_gls_asm: Migration to 19.0#4685RicardCForgeFlow wants to merge 47 commits intoOCA:19.0from
Conversation
|
/ocabot migration delivery_gls_asm A revisar CI. |
a2d86a3 to
e3cc89c
Compare
342b823 to
f6a8224
Compare
f6a8224 to
65b4c50
Compare
| # make the expedition. Try to fallback to the commercial entity one | ||
| "destinatario_telefono": consignee.phone or consignee_entity.phone or "", | ||
| "destinatario_movil": consignee.mobile or consignee_entity.mobile or "", | ||
| "destinatario_movil": "", |
There was a problem hiding this comment.
Pienso que este cambio no es correcto realizando la prueba, hay veces que salta error que el móvil del destinatario es un campo obligatorio.
There was a problem hiding this comment.
Vaya 😞 ! Ponemos el campo phone entonces?
En Odoo 19 han borrado el campo mobile (bastantes quejas por lo que veo):
odoo/odoo@6b820eb
odoo/odoo#189739
There was a problem hiding this comment.
[UPD] Update delivery_gls_asm.pot Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: l10n-spain-12.0/l10n-spain-12.0-delivery_gls_asm Translate-URL: https://translation.odoo-community.org/projects/l10n-spain-12-0/l10n-spain-12-0-delivery_gls_asm/ Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: l10n-spain-12.0/l10n-spain-12.0-delivery_gls_asm Translate-URL: https://translation.odoo-community.org/projects/l10n-spain-12-0/l10n-spain-12-0-delivery_gls_asm/
Non implemented methods should raise informative exceptions if used [UPD] Update delivery_gls_asm.pot delivery_gls_asm 12.0.1.0.1 Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: l10n-spain-12.0/l10n-spain-12.0-delivery_gls_asm Translate-URL: https://translation.odoo-community.org/projects/l10n-spain-12-0/l10n-spain-12-0-delivery_gls_asm/
delivery_gls_asm 12.0.1.0.2
The `cliente` key corresponds to the company not to the customer, wich is `nombre_dst` delivery_gls_asm 12.0.1.0.3
Alhough it will raise another exception, at least it will show the proper message and not a traceback.
Ensure that the values sent to the xml soap request are properly escaped. A partner name like "Johnson & Johnson" would fail otherwise.
[UPD] Update delivery_gls_asm.pot [UPD] README.rst
- Fix tests to declare packages explicitly - Fix wrong keyword literals on errors TT45144
New shipping times and renaming of some of them by GLS TT48760
Check the actual value that is being sent to GLS, since it doesn't make sense to error for 15 characters when the value you would send doesn't actually exceed that limit My use case is that we have some clients that deliver a whole stock.picking.batch instead of stock.picking individually, therefore the reference we use is the batch's name (overwritten through _prepare_gls_asm_shipping). This started erroring when the picking reference reached 16 characters while the batch reference is still only 10
Main github account has been renamed, the previous one now only exists as a redirect. Changing to receive notifications correctly
… code instead of phone_code
65b4c50 to
9b1219f
Compare
6dcb2e5 to
dbf7edd
Compare
pedrobaeza
left a comment
There was a problem hiding this comment.
Por favor, no lo hagáis depender de partner_mobile. Eso me parece un despropósito y forzar a la gente a instalar un módulo que a lo mejor no quiere. Utilizad phone, o como mucho, si queréis detectar dinámicamente si existe el campo mobile, utilizar ése (if "mobile" in self.partner_id).
…a PickUp Service Also raise UserError if trying to send pickup with a non PickUp Service
dbf7edd to
319cc3b
Compare
Okay! He añadido el |
Se ha añadido tests. En el modo de pruebas, la cancelación de pickup devuelve el Error Desconocido -204. (Método
_cancel_pickup) Esto no sé si es debido a estar en modo prueba o también ocurre en entornos de producción.@ForgeFlow