[NEWS] 09.01.24 usuniemy pola “scheduledAt” i “finishedAt” z odpowiedzi zasobów, dzięki którym możesz sprawdzić szczegółowy wynik wykonania zadania edycji wielu ofert / On 09.01.24 we will remove “scheduledAt” and “finishedAt” fields from the response in resources, in which you can check the detailed report of the task of editing multiple offers

**09.01.24** usuniemy pola “scheduledAt” i “finishedAt” z odpowiedzi zasobów, dzięki którym możesz sprawdzić szczegółowy wynik wykonania zadania edycji wielu ofert

**09.01.24** usuniemy pola, w których zwracamy datę dyspozycji modyfikacji oferty:

- **“tasks[].scheduledAt”** - rozpoczęta,
- **“tasks[].finishedAt”** - zakończona.

**Jakich zasobów dotyczy zmiana?**

Pola usuniemy w ramach metody GET na zasobach, dzięki którym możesz sprawdzić szczegółowy wynik wykonania masowej edycji:

- [/sale/offer-publication-commands/{commandId}/tasks](https://developer.allegro.pl/documentation#operation/getPublicationTasksUsingGET) - statusu publikacji,
- [/sale/offer-price-change-commands/{commandId}/tasks](https://developer.allegro.pl/documentation#operation/getPriceModificationCommandTasksStatusesUsingGET) - ceny,
- [/sale/offer-quantity-change-commands/{commandId}/tasks](https://developer.allegro.pl/documentation#operation/getQuantityModificationCommandTasksStatusesUsingGET) - liczby sztuk,
- [/sale/offer-price-automation-commands/{commandId}/tasks](https://developer.allegro.pl/documentation#operation/getofferPriceAutomationModificationCommandStatusUsingGET) - przypisania przelicznika cen do ofert,
- [/sale/offer-modification-commands/{commandId}/tasks](https://developer.allegro.pl/documentation#operation/getTasksUsingGET) - jednego z [określonych pól](https://developer.allegro.pl/documentation#tag/Batch-offer-modification) w ofercie,

W zamian, wprowadziliśmy dziś nowe pola:

- **“createdAt”** - data utworzenia zadania,
- **“completedAt”** - data realizacji zadania,

które zwracamy w odpowiedzi dla całego zlecenia, czyli w ramach poniższych metod na zasobach:

- [PUT /sale/offer-publication-commands/{commandId}](https://developer.allegro.pl/documentation#operation/changePublicationStatusUsingPUT)
- [GET /sale/offer-publication-commands/{commandId}](https://developer.allegro.pl/documentation#operation/getPublicationReportUsingGET),
- [PUT /sale/offer-price-change-commands/{commandId}](https://developer.allegro.pl/documentation#operation/priceModificationCommandUsingPUT),
- [GET /sale/offer-price-change-commands/{commandId}](https://developer.allegro.pl/documentation#operation/getPriceModificationCommandStatusUsingGET),
- [PUT /sale/offer-quantity-change-commands/{commandId}](https://developer.allegro.pl/documentation#operation/quantityModificationCommandUsingPUT),
- [GET /sale/offer-quantity-change-commands/{commandId}](https://developer.allegro.pl/documentation#operation/getQuantityModificationCommandStatusUsingGET),
- [POST /sale/offer-price-automation-commands/{commandId}](https://developer.allegro.pl/documentation#operation/offerPriceAutomationModificationCommandUsingPOST),
- [GET /sale/offer-price-automation-commands/{commandId}](https://developer.allegro.pl/documentation#operation/getofferPriceAutomationModificationCommandStatusUsingGET),
- [PUT /sale/offer-modification-commands/{commandId}](https://developer.allegro.pl/documentation#operation/modificationCommandUsingPUT),
- [GET /sale/offer-modification-commands/{commandId}](https://developer.allegro.pl/documentation#operation/getGeneralReportUsingGET).

W przypadku metod PUT i POST, ze względu na asynchroniczne działanie zasobów, w polu “completedAt” zawsze zwróćimy wartość null.

**Dlaczego wprowadziliśmy zmianę?**

Chcemy usunąć pola, które aktualnie zwracamy w nadmiarowej liczbie i zoptymalizować wewnętrzne procesy związane z przetwarzaniem zadań w zasobach do edycji wielu ofert jednocześnie.

Więcej na temat modyfikacji wielu ofert przeczytasz w [naszym poradniku](https://developer.allegro.pl/tutorials/jak-zarzadzac-ofertami-7GzB2L37ase#edycja-wielu-ofert-jednoczesnie).

-----

**On 09.01.24** we will remove fields, in which we return the date when the offer modification:

- **“tasks[].scheduledAt”** - has begun,
- **“tasks[].finishedAt”** - has ended.

**Which resources will be affected by the change?**

We will remove fields within the GET method on resources, in which you can check the detailed result of performing the task of editing offers in bulk:

- [/sale/offer-publication-commands/{commandId}/tasks](https://developer.allegro.pl/documentation#operation/getPublicationTasksUsingGET) - publication status,
- [/sale/offer-price-change-commands/{commandId}/tasks](https://developer.allegro.pl/documentation#operation/getPriceModificationCommandTasksStatusesUsingGET) - price,
- [/sale/offer-quantity-change-commands/{commandId}/tasks](https://developer.allegro.pl/documentation#operation/getQuantityModificationCommandTasksStatusesUsingGET) - quantity,
- [/sale/offer-price-automation-commands/{commandId}/tasks](https://developer.allegro.pl/documentation#operation/getofferPriceAutomationModificationCommandStatusUsingGET) - price automation rule,
- [/sale/offer-modification-commands/{commandId}/tasks](https://developer.allegro.pl/documentation#operation/getTasksUsingGET) - [one of the specified field](https://developer.allegro.pl/documentation#tag/Batch-offer-modification)s in the offer.

Instead, we introduced new fields today:

- **"createdAt"** - the date when the task was created,
- **"completedAt"** - the date when the task was completed,

which we will return in the response for the entire task, that is, within the following methods on resources:

- [PUT /sale/offer-publication-commands/{commandId}](https://developer.allegro.pl/documentation#operation/changePublicationStatusUsingPUT)
- [GET /sale/offer-publication-commands/{commandId}](https://developer.allegro.pl/documentation#operation/getPublicationReportUsingGET),
- [PUT /sale/offer-price-change-commands/{commandId}](https://developer.allegro.pl/documentation#operation/priceModificationCommandUsingPUT),
- [GET /sale/offer-price-change-commands/{commandId}](https://developer.allegro.pl/documentation#operation/getPriceModificationCommandStatusUsingGET),
- [PUT /sale/offer-quantity-change-commands/{commandId}](https://developer.allegro.pl/documentation#operation/quantityModificationCommandUsingPUT),
- [GET /sale/offer-quantity-change-commands/{commandId}](https://developer.allegro.pl/documentation#operation/getQuantityModificationCommandStatusUsingGET),
- [POST /sale/offer-price-automation-commands/{commandId}](https://developer.allegro.pl/documentation#operation/offerPriceAutomationModificationCommandUsingPOST),
- [GET /sale/offer-price-automation-commands/{commandId}](https://developer.allegro.pl/documentation#operation/getofferPriceAutomationModificationCommandStatusUsingGET),
- [PUT /sale/offer-modification-commands/{commandId}](https://developer.allegro.pl/documentation#operation/modificationCommandUsingPUT),
- [GET /sale/offer-modification-commands/{commandId}](https://developer.allegro.pl/documentation#operation/getGeneralReportUsingGET).

Due to the asynchronous operation of resources, the "completedAt" field will always return null in case of PUT and POST methods.

**Why did we make the change?**

We want to remove fields that currently are returned redundantly and optimize our internal processes associated with performing tasks in editing offers in bulk resources.

You can find more information about editing offers in bulk in [our guide.](https://developer.allegro.pl/tutorials/how-to-process-list-of-offers-m09BKA5v8H3#editing-many-offers)