Latest Contributions by AaronKoelker

‎10-24-2025

@Robert_LeClair Weird. So I did a clean install of 3.5.0, ran it again and still got the same error. Then I created a new polygon feature class within the same file geodatabase, did a mockup similar to yours, and got the same error again. I'm working with "Indoors" data which has a bunch of validation rules and such, so to rule that out, I created an entirely new file geodatabase, made another dummy layer, ran the same calculation and I still get that error. I suppose I could try going back to 3.4 to test...

‎10-24-2025

Hi @Robert_LeClair I did not uninstall 3.4.3 first—I used the built-in upgrade function found within Pro on the About tab. I did just try the soft reset option you shared via editing the App Data folder and registry, but no luck. I also tried clearing the local cache. Something perhaps noteworthy, in my case I have a text field with some room numbers like 1-1, 1-2, etc. I'm trying to simply add a letter P in front of them, so my field calculation looks something like NAME = 'P' + !NAME! . The message I get show it trying to add two letter P's; here's an example of the message for just one feature, but it's similar on all. WARNING 001156: Failed on input OID 1534, could not write value 'PP1-2' to output field NAME I'm also seeing this same behavior trying to calculate on a hosted feature service, in addition to a polygon feature class within in a file geodatabase. It's copies of the same data, just in two different locations. I can try rolling back to 3.5.0 and see if that works, thanks. I tried the Powershell method above (WinGet uninstall --name ArcGIS Pro 3.5 Patch 4 (3.5.4)) but I get an error that the argument only works for single packages, and I don't really know enough about Powershell to go further. I can try a full uninstall and then reinstall 3.5.0 from My Esri

‎10-24-2025

I'm also seeing this error (001156) since updating to 3.5.3 from 3.4.3 doing very basic field calculations with a polygon feature class in a file geodatabase, using an editing session. Simply calculating a text field by joining two other text fields, such as "!FIELD1! + !FIELD2!" etc. I've tried unchecking 'Enforce Domains' (even though my fields do not use domains). Feels like a critical issue, will try updating to 3.5.4 to see if that resolves but I don't see anything in the patch notes related to it. Update: After getting the error, I went to manually type my values into that field and when the text becomes selected it suddenly changes to what it *should* have looked like had my field calculation succeeded. But then when I click out again, it reverts back to the previous value. I then updated Pro to 3.5.4 and restarted, and when I opened the application again my expected values from the failed Field Calculation then appeared correctly. Very bizarre. If I wasn't also getting an actual error code I would've written it off as a visual bug.

‎10-10-2025

I'm using the Chart widget, and am trying to limit the number of categories that will display in a bar chart using the "Maximum Categories" option under the widget's Content pane; Data settings group. It is a stacked bar chart using the "Split by Field" option. However, the app/widget continues to show many more categories over the limit I've set. If I disable the "Split by Field" option, it works as intended. In the Experience Builder documentation, it only says that you must use the "By Group" category type to have this option (which I am). I did notice that if I lower the Maximum Categories number, (for example to 5) it will show less categories in the chart, but still many more than what I set the maximum number to. In the case of lowering it to 5, it instead shows 14 in the chart (out of 40) The settings I'm using are in the table below. Can anyone else reproduce this issue? Is there another undocumented requirement for this setting related to the Split by Field? Category Type By Group Category Field Text Field 1 Statistics Count Split by Field Text Field 2 Sort by Value / Descending Maximum Categories 25

‎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.

Online Status	Offline
Date Last Visited	yesterday

My Ideas

Latest Contributions by AaronKoelker

Re: errors 001156 & 000595 when using Calculate field Tool

Re: errors 001156 & 000595 when using Calculate field Tool

Re: errors 001156 & 000595 when using Calculate field Tool

"Maximum Categories" setting for Bar Chart widget has unexpected results using "Split by Field" option

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: 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...

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