Running the arcgis.users.search function with a query returns a different output format than running the function without a query.
上次发布: February 7, 2017No Product Found
漏洞 ID 编号
BUG-000101730
已提交
December 27, 2016
上次修改时间
June 5, 2024
适用范围
No Product Found
找到的版本
N/A
操作系统
Windows OS
操作系统版本
10.0 64 Bit
状态
Will Not Be Addressed
开发团队已考虑过该问题或请求,并决定不会解决该问题。 问题的“其他信息”部分可能包含进一步说明。
附加信息
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.