Skip to content

[18.0][IMP] delivery_ups_oca: Save the tracking response#1109

Open
carlos-lopez-tecnativa wants to merge 2 commits intoOCA:18.0from
Tecnativa:18.0-delivery_ups_oca-tracking
Open

[18.0][IMP] delivery_ups_oca: Save the tracking response#1109
carlos-lopez-tecnativa wants to merge 2 commits intoOCA:18.0from
Tecnativa:18.0-delivery_ups_oca-tracking

Conversation

@carlos-lopez-tecnativa
Copy link
Contributor

@carlos-lopez-tecnativa carlos-lopez-tecnativa commented Feb 5, 2026

@pedrobaeza pedrobaeza added this to the 18.0 milestone Feb 5, 2026
Copy link
Member

@pedrobaeza pedrobaeza left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should the whole response be stored? What are the extra data that are not decoded on the later code?

@carlos-lopez-tecnativa carlos-lopez-tecnativa force-pushed the 18.0-delivery_ups_oca-tracking branch from 4e92ae1 to 8d22984 Compare February 17, 2026 14:44
@carlos-lopez-tecnativa
Copy link
Contributor Author

Should the whole response be stored? What are the extra data that are not decoded on the later code?

I do not know exactly which JSON key contains the tracking information because UPS does not generate a POD, so I think it is better to store the entire response so that we can later generate a report or something based on this field. The current tracking information is only saved in a text field and cannot be manipulated.

@pedrobaeza
Copy link
Member

Yeah, but if the tracking information is enough, the rest is not needed, just junk, but well, as you prefer.

@carlos-lopez-tecnativa carlos-lopez-tecnativa force-pushed the 18.0-delivery_ups_oca-tracking branch from 8d22984 to ecf8ec7 Compare February 25, 2026 14:23
@carlos-lopez-tecnativa carlos-lopez-tecnativa force-pushed the 18.0-delivery_ups_oca-tracking branch from ecf8ec7 to 2f74178 Compare February 25, 2026 14:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants