Latest Contributions by AaronKoelker

‎10-10-2025

We branded it with an image/logo that includes text, similar to your usage of DeskQuest @Zrobinson_SFPUC , and it serves as the app title. We used a .svg so it scales nice. If you just want title text and no logo you can still use that as a workaround—create an svg image of just your title text and upload it as a "Custom Logo" in the Indoors Viewer configuration options. Just make sure the image aspect ratio is wide and narrow with minimal empty space on the upper/lower margins, so that it maximize its space in the header.

‎10-10-2025

This would be nice. Perhaps as a workaround in the meantime, you can find an Instant app template or create an Experience Builder app that supports multidimensional sliders (unsure which, if any, do), and then embed the app into your StoryMap.

‎09-22-2025

@Robert_LeClair This was the solution, thank you. I added a copy of my input data to the same FGDB as my target data and the tool worked as expected. Hopefully this bug is eventually addressed so we can avoid the extra step, but this will work for now.

‎09-19-2025

Hi Robert @Robert_LeClair , thanks for the BUG link. That does sound like a similar issue, although in my case I'm only using one matching field, not "two or more". I did see the tool work as expected by publishing a copy of the data to a hosted feature service in ArcGIS Online, and then running the tool directly against that service as the Target Dataset. It was the same data I was using before—so the only difference was that instead of two local FGDBs, it was one local FGDB and one hosted feature service. Unsure why it would work that way but not with the local data... unless it is all just an extension of that same bug. I will try to put a copy of both datasets (input and target) into the same workspace and see if that serves as a workaround. Thanks.

‎09-19-2025

Our users have often brought up the orientation of maps displayed in Indoors. The default north orientation isn't always intuitive for indoor maps, as people often expect it to orient to the front of the building. Users can manually rotate maps after loading, but this isn't always ideal, especially for users who are unfamiliar with the building (ex. visitors using a kiosk) A potential solution: Add a field for "Rotation" (in degrees) to the Facilities feature class as a part of the default Indoors Information Model. Then, update the behavior of the Floor Filter (ArcGIS Pro, Online, Portal) to read the value in the "Rotation" field whenever the user selects a new Facility from the dropdown, and apply it to the map alongside the normal pan/zoom action that occurs. If there's no value in the Rotation field, it just defaults to the map's default orientation (likely north), ensuring the functionality remains optional. For routing directions and other multi-building actions, perhaps they could reapply a rotation action back to the map's default orientation. While this Idea is similar to this one, it would apply to more than just the Kiosk/Viewer App—benefitting Space Planner users, users working in ArcGIS Pro, and potentially those using custom apps created with Experience Builder that have floor-aware data.

‎09-19-2025

Hi @GauravJobanputra , yes I posted it to Questions by mistake, I can repost it to Ideas, thanks. For the routing and other multi-building actions, could it simply default back to whatever the web map's default rotation is set as? For example, when the user taps the Directions button to get a route, it already pans and zooms the map to highlight the full path. Instead it could pan, zoom, and apply a rotate based on the map default. I could also see how that may be disorienting in certain situations, though.

‎09-17-2025

Seeing a similar issue in 3.4.3 Append tool "Update (Upsert) Options" being ignore... - Esri Community

‎09-17-2025

In ArcGIS Pro 3.1, an "upsert" functionality was added to the Append GP tool, allowing you to designate updates to existing records in addition to adding new ones. This blog post outlines the functionality and says: Use the Matching Fields for Update parameter to update existing records in the target dataset based on matching records in the input dataset. In this example, each zoning polygon has a unique Zone_ID. Therefore, any records from the target with a Zone_ID that matches records in the input dataset will update with values from the input. Note: You can also match based on multiple matching fields. Using ArcGIS Pro 3.4.3, we're not seeing this perform as described. Instead, a duplicate of the matching record is added from the Input Dataset with the new attributes and geometry, while the original persists and remains unchanged. The schemas of the two datasets match (though they are in different FGDBs), and we're using a shared unique ID field to match the target and input fields. Afterward, I can do a Select By Attributes for that ID and both the original and appended feature will select, implying that the Unique ID does match. Have tried with and without the Update Geometry option checked, as well as the Enforce Domains option. Have also tried using a Selection vs a Where Query for the Input features. Basically, it's always just doing a normal append, despite configuring the tool's Update Options. Has anyone else encountered this or found a solution? We found another upsert-related bug addressed in 3.2, but this seems to be the opposite of the issue we're having.

‎09-17-2025

Somehow I managed to post this in the wrong place... If an admin would like to delete or move this topic, please do. Also, while this Idea is similar to this one, it would apply to more than just the Kiosk/Viewer App, benefitting Space Planner users, those working in ArcGIS Pro, and potentially those using custom apps created with Experience Builder that have floor-aware data.

‎09-17-2025

This was posted in the wrong location—it's been reposted to the Ideas section: Add a Rotation field to Facilities schema for auto... - Esri Community Our users have often brought up the orientation of maps displayed in Indoors. The default north orientation isn't always intuitive for indoor maps, as people often expect it to orient to the front of the building. Users can manually rotate maps after loading, but this isn't always ideal, especially for users who are unfamiliar with the building (ex. visitors using a kiosk) A potential solution: Add a field for "Rotation" (in degrees) to the Facilities feature class as a part of the default Indoors Information Model. Then, update the behavior of the Floor Filter (ArcGIS Pro, Online, Portal) to read the value in the "Rotation" field whenever the user selects a new Facility from the dropdown, and apply it to the map alongside the normal pan/zoom action that occurs. If there's no value in the Rotation field, it just defaults to the map's default orientation (likely north), ensuring the functionality remains optional.

‎08-20-2025

From what we've been told, the results in the Explore pane of the Viewer app or Mobile app will sort based on their proximity to the user (via GPS in the mobile app) or via whatever "Unit" feature has been set by the user as their default "Home" location. This requires a routing network and a "closet facility" layer to function, otherwise it seems to sort by default on OBJECTID, as you're seeing. Haven't gotten far enough in our own deployment to actually test this yet, though.

‎08-20-2025

We would have use for this as well! Right now our solution is to just have teams work it out themselves on what days they should/shouldn't book within a Workspace Area. It would be a great improvement if we could have the software enforce it to prevent mistakes. Basically expand the Workspace Area settings to allow for multiple groups of People to be added to be associated with an area, instead of just one, when the area is set to "Restricted", and then allow us to assign days/times for when those groups can book within the Workspace Area.

‎08-20-2025

In my experience, ArcGIS Pro's performance plummets if you are working with data over any sort of network. Web services, data on shared network drives, a Documents folder that is mapped through a One Drive account, etc., will all slow down even the simplest editing tasks to a crawl. Doesn't matter how beefy your PC specs are. Working over network drives is a common practice in a workplace environment, but for whatever reason Pro has always struggled with it. It's been an issue for so long that at this point I assume it is just an inherit limitation of however the software is structured. As a test, copy some data that you are experiencing performance issues with to a local drive, preferably the same physical storage device that ArcGIS Pro is installed to. Run the same editing tasks and see if there is an improvement. The difference is often night and day in my experience.

‎08-07-2025

I'll add that one limitation I found with this is that if you overwrite the hosted feature layer then those "Allow Attribute Editing" options all get reset back to the default. But if you set those fields to "Read Only" in ArcGIS Pro (right-click the layer in your Map and go to Data Design > Fields) before publishing and it will carry over to the service. So far I haven't noticed any impact on functionality and have been able to create and merge plans. Edit: If you try this with the Occupants layer, it causes the Update Occupants GP tool to fail when trying to run directly against the service 😞

‎08-06-2025

@nmanocha Nakul, Thanks again for the detailed response. I think your last point "We will have a documentation of what is supported in downloaded ones and what are the limitations?" would go a long way toward improving the authoring experience, whether it is just a document linked from the web builder or it is somehow incorporated directly into the authoring experience (for example, if you add an infographic block, maybe there's a pop-up or small banner in the builder that notes the limitations or availability in the app.) Having the web browser version and the online version of the native app be in sync through an embed as you proposed sounds like it could be beneficial as well and help cut down on unwanted surprises when presenting. However I think for our use cases, if we are ever using the native app it would be because we needed the offline mode. For everything else we'd likely use just use the browser version.

Online Status	Offline
Date Last Visited	Wednesday

My Ideas

Latest Contributions by AaronKoelker

Re: Indoors Viewer: allow customization of the header

Re: Add support for multidimensional raster slider in StoryMaps

Re: Append tool "Update (Upsert) Options" being ignored (3.4.3)

Re: Append tool "Update (Upsert) Options" being ignored (3.4.3)

Add a Rotation field to Facilities schema for automatic orientation with Floor Filter

Re: Add a Rotation field to Facilities schema for automatic orientation with Floor Filter

Re: Should Append tool perform Update and Add at the same time

Append tool "Update (Upsert) Options" being ignored (3.4.3)

Re: Add a Rotation field to Facilities schema for automatic orientation with Floor Filter

Add a Rotation field to Facilities schema for automatic orientation with Floor Filter

Re: Custom Sorting for Indoors Category Results - Is it Possible?

Re: Configure temporal hotels

Re: ArcPro Overall Performance.

Re: How to configure the Edit Form pop up in the Space Planner application?

Re: Briefings Preview Enhancements

Re: Small change to standard themes (Obsidian, Rid...

Re: Updating config.json results in text widget re...

Append tool "Update (Upsert) Options" being ignore...

Re: Should Append tool perform Update and Add at t...

Re: One Layer, several (mutually exclusive symbolo...