BlackBerry Web Services known issues

If your organization’s environment supports a large number of users (for example, 5000), the BWS.getUsers method might take longer than expected to return results, and might use a larger amount of heap memory than expected.

If an application uses the BWS.getUsers method with the sortBy parameter set to user name and the sortAscending parameter set to false (descending order), and the username field is empty for some users, the results are not returned as expected. Users with non-empty user names are repeated across multiple pages. (DT 6722942)

Workaround: In BWS.getUsers, set the pageSize parameter to 0 (return all users on a single page) or to a value that exceeds the number of users in the MDM domain.

If your organization’s environment hosts a large number of users (for example, 5000) and an API calls the BWS.getUsers method with the pageSize parameter set to 0 (return all users on a single page), the operation can use a large amount of memory. (DT 6709745)

If an application uses the BWS.getUsers method with the sortBy parameter set to last contact date, and the lastcontactdate field is set to null for all users, the results are not returned as expected. (DT 6705456)

Workaround: In BWS.getUsers, set the pageSize parameter to 0 (return all users on a single page) or to a value that exceeds the number of users in the MDM domain.

The BWS.getUsers method does not currently support sorting results by device attributes. Results are sorted using the USER_UID attribute. (DT 6698756)

Parameters that are not supported in a BlackBerry Device Service domain might return an INVALID_PARAMETER error code instead of a NOT_SUPPORTED error code. (DT 6608253)



Was this information helpful? Send us your comments.