Bug
Running the arcgis.users.search function with a query returns a different output format than running the function without a query.
| Bug ID Number | BUG-000101730 |
|---|---|
| Submitted | December 27, 2016 |
| Last Modified | June 5, 2024 |
| Applies to | No Product Found |
| Version found | N/A |
| Operating System | Windows OS |
| Operating System Version | 10.0 64 Bit |
| Status | Will Not Be Addressed |
Additional Information
Although it appears that the properties available in the user object are different in the two cases, it's not actually true. In both cases, all properties are fetched on demand if they're not available. For example, print(user..storageUsage) will fetch the storageUnits if they aren't available with the user object initially. Because of performance reasons, we don't fetch all properties initially, but if the properties are queried, the 'user' object is hydrated and all properties are fetched and made available. It's only in the print function that this discrepancy shows up, but doesn't affect the behavior of the API.Steps to Reproduce
Bug ID: BUG-000101730
Software:
- No Product Found
Get notified when the status of a bug changes
Discover more on this topic
Search for related information
Find training related to this topic
Explore ideas and give feedback
Get help from ArcGIS experts
Download the Esri Support App