Changes i Sale API?
Hi!
Is there any changes implemeted in the API for Sales on 2/7?
Dataloads look diffent and the field 'associateDbId' is missing.
We are also receiving 2 files instead of one, please see below.
Alle Antworten (11)
Hi Sara,
We do not see your images because they seems to be linked to your PC:
I am now aware of any API changes, but need to know more what your images show to determine what's what.
Best regards.
Hi Sara!
Yes, great, now we see some images. Can you share what archive provider you are using to get the data? There are several to chose from, but I guess it's one of the three?
I have invited a collegue from our BI team to join the conversation. She will join as soon as she is available.
Hi!
My collegue can't reply in this thread. Is there something she or I can do?
Hi Sara,
The last release (online) was 26/6. The Sale provider associate reference hasn't changed in 4 years, and has always exposed the associate ID as one of the following:
- associateId
- associate/associateDbId
The associateDbId is a field on the AssociateExtenderBase class, and is used as an extender on many other providers. However, when used by other providers as a relational field, the naming convension generally uses the "associate" prefix.
There is an associateDbId field on other providers, i.e. AllUsers, but that is because the group of user providers is towards the associate table, and not a relational reference.
Best regards.
Hi!
OK, but then why would we get the data in the files as above? We have not changed anything on our side, but the dataload is different.
Do you have any explanation for that?
BR
/Sara
Hi!
our BI team has identified the problem on our side. On 2/7 the data volume became large enough to become more than one page, and we did not handle that on our side.
Thank you for your help!
BR
/Sara