Hi guys,
we’re currently working with the IdentityAPI of the Java MS SDK and found an inconsistency between the API Spec Cumulocity - OpenAPI and the implementation in the SDK.
The API Spec for “Retrieve all external IDs of a specific managed object” states that it simply returns an array of elements - so I’d assume that I’d get all existing externalIds of that ManagedObject.
The SDK however returns an ExternalIDCollection which is paginated - so I’d expect all aspects of that (pageSize, currentPage) need to be applied.
Can someone clarify which approach is correct? Especially: how can we make sure to really get all (even more than 2000?) externalIds of a ManagedObject.
Thanks a lot,
Michael
I would guess the SDK implemenation is wrong assuming that the API supports paging which doesn’t seem to be the case here.
Also checked the API and there are no paging information available nor are url parameters page or pageSize recognized…
The SDK just assumes that but always returns non-paged results wrapped in a paged collection class which would assume that you can use paging there which not have any effect.
I would also assume that a MO with 2000 Ext IDs is definitely an edge case 
After some more discussions, we agreed that this is indeed a defect in the SDK and will be fixed in a future version.
I confirmed that even >2000 externalIds of a ManagedObject are returned by the REST API as well as with the SDK, so it is not a critical problem.
1 Like
