Multiple dimensions: is the same data expected even if the dimension order changes?

[SaraRands]

In order to help our customers use the 2.0 APIs for multiple dimensions, I've written a connector that recursively generates the report body for multiple dimensions, following the pattern documented at:
https://www.adobe.io/apis/experiencecloud/analytics/docs.html#!AdobeDocs/analytics-2.0-apis/master/reporting-multiple-breakdowns.md

I've noticed that sometimes the data is different depending on what order the dimensions are pulled in.

For example, if we pull dimension1, dimension2, dimension3, we get 179 rows of data. (That is, if the first request specifies dimension1 as a dimension; children requests specify dimension1 as metricFilters and dimension2 as the dimension; and grandchildren requests with the final level of data specify dimension1 and dimension2 as metricFilters and dimension3 as the dimension.)

But if we change the order to dimension3, dimension2, dimension1 we get 229 rows of data.

Is this an expected outcome? Do our customers need to specify the dimension ordering when they configure their report?

If this isn't expected, could your support team reach out to me so we can determine the cause of the data discrepancy?

[parrish488]

@SaraRands I believe this is working as intended, the ordering of the dimensions would be very important when doing breakdowns. If you can provide the specific reporting request JSON bodies, I could easily verify.

I realize this issue is pretty old, so let me know if you still need help.