Views
Replies
Total Likes
I don't believe so...
So going back in the history of the APIs... the older versions (1.4, 1.3, etc) allowed for complex breakdowns... but they were slow.. so this meant that you would have to do a call to "create the report" which would spit back a report id... then you would have to keep querying the queue to check for that report to be ready... once it was done, you could then make a call to grab the report.
Depending on how many APIs were being used by all the different Adobe clients, this could be relatively quick... maybe all done within a minute... or it might take a lot longer... There was also times when the queue would get stuck, and nothing would work... Client Care had to clear the queue and reset things to get it working again.
Now, with version 2.0, Adobe has thrown away the queue model... opting for a fast experience by returning the data when called... but this comes with it's own challenges... as in, you can no longer do bulk breakdowns, you have to run a query for each breakdown you need....
So depending on how deep your breakdowns, and how many rows in each, those all need to run separately... unfortunately.
I am really sad that API 1.4 is being sunset.... for quick and easy data, API 2.0 is superior, since it's fast and returns data immediately... but for complex breakdowns, having to make all those requests is painful... (The older version was much friendlier...)
Views
Replies
Total Likes
I don't believe so...
So going back in the history of the APIs... the older versions (1.4, 1.3, etc) allowed for complex breakdowns... but they were slow.. so this meant that you would have to do a call to "create the report" which would spit back a report id... then you would have to keep querying the queue to check for that report to be ready... once it was done, you could then make a call to grab the report.
Depending on how many APIs were being used by all the different Adobe clients, this could be relatively quick... maybe all done within a minute... or it might take a lot longer... There was also times when the queue would get stuck, and nothing would work... Client Care had to clear the queue and reset things to get it working again.
Now, with version 2.0, Adobe has thrown away the queue model... opting for a fast experience by returning the data when called... but this comes with it's own challenges... as in, you can no longer do bulk breakdowns, you have to run a query for each breakdown you need....
So depending on how deep your breakdowns, and how many rows in each, those all need to run separately... unfortunately.
I am really sad that API 1.4 is being sunset.... for quick and easy data, API 2.0 is superior, since it's fast and returns data immediately... but for complex breakdowns, having to make all those requests is painful... (The older version was much friendlier...)
Views
Replies
Total Likes
Views
Likes
Replies