TTN np logistics is not created for targeted delivery due to duplication in the fields.
In order No. 1157, such data [file]5057[/file] when trying to create a TTN np logistics on the status "Awaiting shipment" gives an error [file]5058[/file] going into the logs, we see [file]5059[/file] that the "city" field is filled with the full address, but it shouldn't be.
Please correct.
TTN np logistics is not created for targeted delivery due to duplication in the fields. In order No. 1157, such data when trying to create a TTN np logistics on the status "Awaiting shipment" gives an error going into the logs, we see that the "city" field is filled with the full address, but it shouldn't be. Please correct.
Good afternoon, Still not working. 1. If I'm not mistaken, in NP this is a required field for targeted delivery, but it is not recorded. 2. When we try to create a TTN and click on the status "Awaiting sending" it will glow gray and will not let it go further Waiting for an answer!
Good afternoon,
Still not working.
1. If I'm not mistaken, in NP this [file]5098[/file] is a required field for targeted delivery, but it is not recorded.
2. When we try to create a TTN and click on the status "Awaiting sending" it will glow gray and will not let it go further [file]5099[/file]
Waiting for an answer!
1. New mail does not give a damn about regions, districts and other territorial-administrative units all its life. They accept a purely unique city and street/department id. What you see in the new logistics mail is purely someone who wanted to receive more fields, instead of the normal receipt of the city id from the new mail directory. 2. We pass City+Region+Street+House+Flat to npl. District - unfortunately we don't know the name of the district and we can't know, that's why it is not transferred to API. With this combination, it is very easy to understand what kind of city it is and where to send the parcel using a purely directory from the new mail. We have several solutions: a) You manually fill in the area after the area in each order, we fix the action parser to isolate the name of the area from the address and add it to the action transfer b) you write to npl with a request to remove this field from the mandatory ones, since even without it you can understand exactly where you need to send the parcel
1. New mail does not give a damn about regions, districts and other territorial-administrative units all its life. They accept a purely unique city and street/department id. What you see in the new logistics mail is purely someone who wanted to receive more fields, instead of the normal receipt of the city id from the new mail directory.
2. We pass City+Region+Street+House+Flat to npl. District - unfortunately we don't know the name of the district and we can't know, that's why it is not transferred to API. With this combination, it is very easy to understand what kind of city it is and where to send the parcel using a purely directory from the new mail. We have several solutions:
a) You manually fill in the area after the area in each order, we fix the action parser to isolate the name of the area from the address and add it to the action transfer
b) you write to npl with a request to remove this field from the mandatory ones, since even without it you can understand exactly where you need to send the parcel
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
Donate
You don't have enough funds in your account Top up