-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CodigoOperacion vs IdOrdenRetiro #31
Comments
Hello Hugo, did you find any solution? |
I just generate the labels myself. As long as they have the same info as the "real" ones and the barcode with the tracking number they don't seem to care. I've seen many others do the same (including large warehouses). Apparently OCA's API is incomplete and there's no way to complete the whole process. |
I think we're talking in english but both are from argentina. jaja. Ya encontré el circuito completo. obtengo el id de orden retiro y con eso después puedo cancelar, visualizar etiqueta y demás. |
De donde sacás el id de retiro? 🥺 |
jaja, me volví loco, pero lo saqué y nada.. magia.. te devuelve un vector resumen, y una matriz detalle_ingresos la buscas igual q resumen pero agregándole la línea.. [0] |
echo " Orden Retiro".$abc['detalleIngresos'][0]['OrdenRetiro'].""; |
si o si debería estar en true el confirmarpedido,... |
When creating a new pickup order (eg: via
create_pickup_order
), the WS returns aCodigoOperacion
.However, fetching the PDF labels requires sending an
IdOrdenRetiro
. Checking via the web UI, I can tell thatCodigoOperacion
andIdOrdenRetiro
don't have the same value (nor does there seem any way to infer one from the other).Have you guys found a way to obtain the
IdOrdenRetiro
? If not, how are you handling fetching the PDF labels for packages?The text was updated successfully, but these errors were encountered: