Latest Contributions by AaronKoelker

Hello there. On the Allocation tab of the Space Planner, you can add a new Organization Area based on pre-existing values in the ORG_LEVEL_1 field. When these areas are created, any Units with a matching Occupant based on ORG_LEVEL_1 are automatically allocated to that new Org Area. This is great and makes sense, as obviously the Unit is being used by that specific group if somebody from the group is assigned there. However, if you were to move the initial occupant out of that Unit and then assign a new Occupant from a different group that desk is not automatically allocated to the new Occupant's group. Since Space Planner users have to move Occupants on one tab and then go to another tab to manually re-allocate the Unit in this scenario, we've found that over time the second step is sometimes forgotten and the Allocation information can become increasingly out of sync with what Occupants are sitting where. To correct this, you'd have to go around one by one and verify that each Unit is still allocated to the matching group of the assigned Occupant. Another scenario is if you are doing a large rearrangement of Occupants (perhaps moving departments between floors) it can be complicated to re-allocate each Unit to match (especially if teams aren't fully lumped together in ways that make it easy to draw a box around all of them to re-allocate). And lastly, sometimes the Allocation tab is simply more useful to see where teams are, rather than restricting where they are allowed to be.  To ease these scenarios, it would be great if there was a "recalculate" button or similar that could manually trigger that initial auto-allocation function again based on the Occupant assignments. Perhaps both an option to recalculate all areas at once (for orgs with many departments/teams) and another option to recalculate just for one specific organization area. Options to only "upsert" (add or update allocations) versus a full overwrite (add, update, & remove allocations) based on Occupant changes would be helpful too. ... View more

With the List Widget, you can filter the list data based on the current map extent (ex. Dynamically filter data in a List widget based on the map view).  It would be great if an option or trigger was added so that the List Widget could filter based on the layer's scale visibility, too. For example, if I have a scale limit (a.k.a. visibility range) set up for a layer in my web map to turn off beyond 1:1,500,000 scale, those features would also disappear from my List Widget once I've zoomed out beyond 1:1,500,000. Currently, the features remain on the list widget regardless of their visibility on the map, which can be a confusing disconnect for users. Additionally, when the user is zoomed out to smaller scales, this might also (I assume) bring an unnecessary performance hit to the List Widget as it tries to load a bunch of features that are otherwise hidden from the map.  Adding this option could help authors both control the length of longer lists connected to big datasets when the user zooms out to smaller scales (hopefully leading to performance gains), and could also provide a more intuitive relationship between what features are appearing on the map vs what is appearing in the List.  Thanks for your consideration ... View more

When 360 photos (via Oriented Imagery dataset) are added to the Indoors Viewer app (browser), a button to "Show 360 Photo Locations" becomes available. By default, the symbols for these photo points are hidden from the map until this button is clicked.  When the button is clicked, the map is greyed out and the 360 photo point symbols appear. However, these symbols are greyed out along with the rest of the map. I imagine the intention might've been to grey out the map and have the photo points remain at their normal brightness so that the user can find them easier, but it doesn't appear to be working correctly if so.  It would be great if the grey mask applied only to the map beneath the 360 photo points, so that the points could stick out visually. (As a sort-of workaround in the meantime, I've applied an animation to the symbols to make them pulse and have them stick out more)     ... View more

Hello, I'm working on a script to report add-on license assignments across multiple portals (both AGO and Enterprise) and am having issues with add-on extensions for ArcGIS Pro (e.g. Spatial Analyst). I'm also trying to avoid using a full admin account if possible, instead using a custom role.  The issue is that I can create a custom role that has the "Manage Licenses" admin privilege and be able to view and assign these kinds of add-on licenses via the website just fine. But in the API, this info appears to only be stored in the gis.admin.license class, which requires an admin account to access.  Can anyone provide insight on this discrepancy? Is there another way to view the assigned add-on extensions for a user that is not through gis.admin.license? The User class has a provision property I can access, but that only seems to return add-on apps (e.g. ArcGIS Pro), and not the add-on extensions. The apps are returned as a license object but looking at the properties there's no additional extensions/entitlements associated in there, either.  Any ideas or guidance?  ... View more