1b.app
Link copied -

Problem with uploading data from Rozeta

Good afternoon.
Today, after lunch, we began to observe that orders from Rozetka began to arrive in a different format, not like it was before.
The field for new mail is unloaded without separation. Or the branch is at the end of the line, the system does not send parcels.
Please sort out this problem. Work stopped!!!
Original question is available on version: ru

Answers:

Good afternoon. For this order, the rosette api gives the following response:
[delivery] => Array
(
[delivery_service_id] => 5
[delivery_service_name] => Nova Poshta
[place_id] => 724136
[place_street] => street Kotlyarevsky
[place_number] => 10
[place_house] => 7
[place_flat] =>
[cost] =>
[city] => Array
(
[id] => 31419
[name] => Chernivtsi
[name_ua] => Chernivtsi
[name_en] => Chernivtsi
[region_title] => Chernivtsi region.
[title] => Chernivtsi
[status] => 1
)
[delivery_method_id] => 1
[ref_id] => e71fe717-4b33-11e4-ab6d-005056801329_10
[name_logo] => nova mail
[email] =>
[street_directory_id] =>
)
Previously, if we had a ref_id field, we looked up the branch by the given ref_id (this is the identifier of the new mail branch). But now such a department number does not exist (I just re-uploaded the NP reference book and double-checked it specially for the api). Those. socket transmits wrong branch ref. They also add _10 at the end of ref for some reason. Why did they change the format and how to decrypt it now, please check with Rozetka support. From our side, nothing has changed in the integration.
ps correct ref 10 branch in Chernivtsi 336de187-e1c2-11e3-8c4a-0050568002cf according to new mail api response.
01.12.2020, 18:47
Original comment available on version: ru

Maybe it will be easier to take a new field [place_number] from this api?
Replace ref_id with place_number
01.12.2020, 18:54
Original comment available on version: ru

1. We need not 10 but 336de187-e1c2-11e3-8c4a-0050568002cf
2. It's better to find out what causes such changes in the issuance of api and then see what to do. Now, in fact, the socket, changing its api, has broken your work - we just silently have to write a few crutches to resume it ???
01.12.2020, 18:59
Original comment available on version: ru

How to solve this problem?
As I understand it, she worries everyone who sells through Rozetka
02.12.2020, 11:33
Original comment available on version: ru

I'm negotiating with Rozetka. But for now, it's quiet.

Grabovsky Alexander
Client wrote:
How to solve this problem?
As I understand it, she worries everyone who sells through Rozetka
02.12.2020, 11:34
Original comment available on version: ru


Krasnobrizhev Alexander Viktorovich
Client wrote:
I'm negotiating with Rozetka. But for now, it's quiet.

Let's cooperate. Give contacts where to write or call. So that the outlet can see that this is not one person's problem.
02.12.2020, 11:37
Original comment available on version: ru

In the office on Rozetka, there is a connection with support, write there.
02.12.2020, 11:41
Original comment available on version: ru


Krasnobrizhev Alexander Viktorovich
Client wrote:
In the office on Rozetka, there is a connection with support, write there.


Thank you!
Anyone who has encountered a problem, write to Rosette about it. This will speed up the problem solving process.
02.12.2020, 11:49
Original comment available on version: ru

Куприян Владислав Валерьевич
Baza.cn.ua / Integrator (FOP Kupriyan)
I sent a task to TP yesterday
Your request #2311444 was successfully registered
While silence waiting for an answer
02.12.2020, 13:22
Original comment available on version: ru

yes, I have this problem too.
you need to plug in the outlet.
but crutches will probably have to be made by ourselves as usual
02.12.2020, 14:08
Original comment available on version: ru

Куприян Владислав Валерьевич
Baza.cn.ua / Integrator (FOP Kupriyan)
They answered me:
Good afternoon!
Let's look at the problem.
Rozetka Marketplace Technical Support Service
02.12.2020, 14:15
Original comment available on version: ru

Commentary is available in ru and not yet translated to the current language.
02.12.2020, 15:18

The socket has already fixed everything. Thanks to all.
04.12.2020, 11:00
Original comment available on version: ru

Please join the conversation. If you have something to say - please write a comment. You will need a mobile phone and an SMS code for identification to enter. Log in and comment