Differentiating Live vs. Batch product request syntax

Hello,

There is no concrete distinction in the format of the Live product request that differentiates it from a Batch product request.

Live:

<GetEcomData ExternalUserId="123" AccessUserCustomerNumber="123" VatCountryCode="US" VatPostingGroup="">

<tables>

<Products type="filter">

Batch:

<GetEcomData ... CustomIdentifier="ABC">

<tables>

<Products type="all">

We should not differentiate using "Products type" since that's in both requests.

The live request includes an AccessUserExternalId and AccessUserCustomerNumber, and the presence of these helps infer that this is the live request, but we don't trust that it will stay this way and have seen unexpected field name changes in the past.

Is there a plan to include an intentional and reliable identifier to distinguish the two types of Product requests?

Thank you,

Skylar Kennedy

Hi Skylar,
there are no plans to change any parameters in those requests. We are not allowed to make significant changes in order to support the already released applications for the D365BC and AX/FO. The live request always checks for the "AccessUserCustomerNumber" parameter so it will not work without it. The live integation always use the customer related information for the lowest possible product prices for that customer while the regular batch product request gets general available information. Batch request can include several items in the request so you can get Products/ProductGroups/Users/ProductPrices in the one request. You can find out more about those requests here:
batch and live.

BR, Dmitrij

Developer forum

Differentiating Live vs. Batch product request syntax

Replies