Latest Contributions by AaronKoelker

https://developers.arcgis.com/python/latest/api-reference/arcgis.gis.toc.html#arcgis.gis.User.provisions Does anybody know what specific user permissions are needed to access the User.Provisions property (linked above) via the API? When I'm logged in with an admin account, I'm able to pull this property no problem. But we're trying to create a custom role for reporting purposes that can essentially only view all user information, not manage it, so that the script doesn't require a full admin account.  In the options for creating a custom role, the only permission I see related to licenses is under Admin -> Content -> Manage licenses, which is described as "Allow member to assign licenses to members of your portal." Enabling this lets me read the user.provisions property—but I'm wondering if there is another permission that would allow read-only? Separating out the ability to view and manage would be ideal.  Edit 4/3/2026—to add, while the permission mentioned above works for most things (even if it's not ideal because it also allows for assigning/revoking licenses), I do get an error when trying to read add-on license for admin accounts. Specifically in one ArcGIS Online org we have, but haven't seen the issue when running on Enterprise orgs. Have not been able to figure out which specific add-on or extension causes this, or whether it's some sort of license/extension inherent to admin accounts that non-admin accounts are not allowed to view in the API. I suspect it may be an organization extension like ArcGIS Velocity. The specific error is a 403: You do not have permissions to access this resource or perform this operation. Would really appreciate some clarification or insight here   ... View more

I've run into a potentially undocumented limitation with Joined Views and Experience Builder, and am wondering if anyone has run into this before or could replicate/enlighten. As a simplified example—say I have an ExB app with just a Filter widget and a Table widget. The Table widget has two Sheets in it, and both sheets point to different Joined Views which share a common join layer (an ArcGIS Online hosted feature layer (Layer A)) but use different target layers in their joins (two other ArcGIS Online hosted feature layers (Layer B and Layer C)). So one Joined View is Layer A + Layer B and the other is Layer A + Layer C. Layer B and Layer C both share a field that contains common data, let's say colors, as an example. The Color field in both Layer B and Layer C are string fields and do not use Domains, however the Values inside the field do match across both layers. So there is a "Red" in both fields of both layers, a "Green", etc. etc. The only difference between the fields is the name (example: one is "Color" and another is "Colour"). I set up my Filter widget to have a Group Filter set up to "Ask for Values" (Unique), using the Color/Colour fields from my Joined Views. When I go to test, I get a dropdown for Colors as expected and select my choice. In the Table widget, however, only one of the sheets gets filtered. Whichever Joined View in the Group SQL Expression that was used as the "Main field" gets filtered in the table, while the other does not. If I switch the "Main field" in the expression to use the other Joined View, then the other sheet gets filtered in the table, and not the first.  Unlike single data filters (non-Group Filters), I can't actually see what the underlying SQL looks like, so I'm unsure if the cause is just that the underlying field name is different across both views. I've never run into that issue using two hosted feature layers, rather than Joined Views. That seems to be the whole point of the Group SQL Expression builder, letting you map values to the filter across different fields.  I suspect it's a limitation of using Joined Views, but haven't seen that documented anywhere and I'm hoping that someone can confirm.  ... View more