The Migration Center endpoint to get counts "migrations/v3/report/status/count" does not take a groupID parameter as a filter, - it only takes a start date and end date filter.
Conversely, and unintuitively, the Migration Center endpoint to get summary migrations/v3/report/summary does take a groupId parameter, but not dates.
https://docs.arcxp.com/alc?id=kb_article_view&sysparm_article=KB0010621
This makes the use of both endpoints extremely awkward.
For example, I would like to first request the count endpoint to get a list of all "interesting" states, for example, "FailPhoto", "FailVideo" and "ValidationFailed", and then go to summary to filter by that state to see detials on each error.
If you try this exercise, you will find that you cannot also reliably fiter by the migration "Chunk". GroupId is a very good solution for this, likely much more efficient on the backend (date comparisons are more expensive than string comparisons) but it's not implemented on the count endpoint.
This simply makes life hard on the developer, as the only soution to the user is to create a mapping of groupId to date-range and enforce it.
Additionally, this reduces usability because the date range, IIRC, is limited to day resolution. you cannot query count for a migration submission is a specific hour, for example, between start=2023-06-01T01:00:00 and end=2023-06-01T02:00:00 However, you can tag a migration submission with the group id "06-01-1pm" and use that in summary requests.
TL;DR:
filter parameters on migration summary and migration count endpoints to target a specific migration batch upload should be similar. They are not.
Guest
