Latest Contributions by alex_friant

Hi Kelly, Thanks for the advice. I just filed a support request. ... View more

Today I discovered what appears to be a bug with (at least) the Zone Lookup template. If you are using a custom geocoder (say from your enterprise), everything works fine. However, if you enable Map Navigation constraints, that geocoder functionality breaks. Even if you turn off Map Navigation, that geocoder continues to no longer function properly (results always come back negative). You need to delete the geocoder and re-add it (with Map Navigation OFF) and then it works again. Seems like a bug, imo. ... View more

@CathyAppleton - Totally agree with everything you said. I want a minimize button, too. I wanted to share a tip with you (in the meantime) that if you hold down the Ctrl key and double-click the layer, the attribute table will open up. I use that shortcut a lot and thought I'd share. 🤓 ... View more

I like this idea. Currently the only option is to slide adjust the table view (or which ever view that needs minimizing) using the border between it and the map view, which would be super convenient.  And really, a Minimize button would just be a kind of shortcut to quickly do that for the user (effectively shrinking the view down, just like sliding border bar), so implementation would just be a UI interface to quickly toggle between two values (current & 0). Seems like an easy win!   ... View more

There is a built-in set of Geoprocessing Tools that do this in ArcGIS Pro: Data Management Tools Workspace Generate Schema Report Convert Schema Report Import XML Workspace Document Your workflow would be something like this:  Design your Geodatabase "template" feature class (fields, settings, domains, sub-types, etc.) Run the Generate Schema Report -- choose export option to XLSX You can make little tweaks in that spreadsheet in Excel if you need to Run the Convert Schema Report -- choose export option to XML Run the Import XML Workspace Document -- you'll need a Geodatabase as your target to deploy the schema to ✅ Done.  ... View more

Sounds like a reason to stay away from 3.6 until they patch it. ... View more

@wayfaringrob - That's good point. That login screen is dark! Let's give a shout out to the login screen team! 🏆 Maybe the main site team could borrow and apply that css? 😆 ... View more

Add me to the queue. 2026 is almost here and we still don't have a dark mode for the main AGOL site. Place your bets... will be get dark mode by 2030? $10 says... no. ... View more

I think the temporary work around is to make sure your layer isn't being projected on the fly - make sure your map's coordinate system matches that of the data layer you are editing. ... View more

@JasonFitzsimmons - If I understand your desired workflow correctly, I think I know how you can do one small addition to the workflow to change just the data sources for the new map, not the original one also. After you have the "Data Sources" tab opened for the project, open the "Maps" folder under the Catalog View, to the left of where all the data sources are listed for the project. Select the new map you duplicated. Only the data sources for that particular map will be listed to the right. You can change those sources, and it will not affect the original map's data sources. Give it a try, it works for me in Pro 3.4.4. ... View more

@SebastienPelletier - Thanks for sharing that Bug report. I think I kind of figured out why Experience Builder (XB) is screwing things up with Scroll zooming after black boxing this issue. First, I created a global "Level of Detail" (LOD) layer (shared publicly so you can try) so I could see what standard Level of Detail (0-23) you are between while at any particular arbitrary scale. Second, if you use that layer in a Map Viewer map, you can see clearly that Map Viewer respects each "Scroll" event as a single LOD step. Third, if you use that same layer in a map consumed by XB, you can see that XB is doing something different, but what? To figure that out, I changed my Windows 11 Mouse settings under Scrolling to change the number of "lines" a scroll event would scroll a document from the default of "3" to "1" line. Back in XB, you can see instantly, while scrolling now, that the LOD has some arbitrary scale steps configured that are much "narrower" than the standard LOD scales. There appears to be about 4 scale steps between each LOD cut off. To be precise, there are exactly 94 scale levels utilized by XB. If you're using Windows 11 or 10's default Mouse Scroll "3 line" setting, you'll usually end up (depending on where you start) with about 1 or 2 scrolls to change from one standard LOD to the next in XB. But this is not true in Map Viewer! Map Viewer doesn't care what your OS Mouse Scroll Settings are set to - it only looks at whether or not your mouse scrolled once. The bug, it appears, is twofold: XB has 94 scale steps, not the standard 24 XB isn't respecting mouse scrolling events as single LOD step changes like Map Viewer does, rather XB is receiving its scrolling events from the "# of lines" setting in the OS (or mouse driver). (The following is speculation) This difference between Map Viewer behavior and XB behavior is probably due to Map Viewer JavaScript listening to 'scroll' events, and XB is listening to 'wheel' events and having the setting "event.deltaMode === 1", which has the app listen to the OS settings. ... View more

😢 okay ... View more

The colon ':' just after #data_s=id needs to be encoded to %3A so it looks like this: #data_s=id%3A instead of this: #data_s=id: Conversely, the %3A just after the 'search_status' parameter needs to be a colon ':' so it looks like this: search_status: instead of this: search_status%3A The final URL should look like this: https://myportal.org/portal/apps/experiencebuilder/experience/?id=4224xxxxxxxxxxxxx982#data_s=id%3AdataSource_1-18fc5181f68-layer-16-0&widget_2=search_status:%7B%22searchText%22%3A%221234%20Executive%20Park%20Blvd%22%7D This is a breakdown of why some colons are encoded or not:   ... View more

We'd love to see Esri's photo-enabled applications (QuickCapture, FieldMaps, Survey123, etc.) include built-in watermarking capabilities that would let the form and map designers easily add timestamps and custom text (i.e. coordinates, name of app & user ingesting) to photos. This could work beautifully as headers, footers, or overlays, giving teams the flexibility they need for documentation and branding. Even better, imagine if organizations could create standardized watermark templates at the enterprise level - similar to how organization themes work now. Designers could then simply select from these pre-approved templates, ensuring consistency across projects while saving time on setup. This would streamline workflows and give organizations better control over their visual standards during data collection. ... View more

Background: I was gratefully advised by Pro-West Associates that they have seen this issue before, and it appears to be related to if the user account experiencing the RuntimeError has signed into ArcGIS Pro before. The issue is tied to the Windows Registry, and while I can confirm that's the case with our user experiencing issues, it's not always the case, only that the fix lies in the registry. I had two other User accounts on the same server that had also opened ArcGIS Pro, but import arcpy worked just fine for them when using the ArcGIS Server Python 3 environment. So, replicating the issue is difficult. These are the steps taken to solve the RuntimeError for that one user we needed to be able to use arcpy in the ArcGIS Server Python 3 environment: Make sure ArcGIS Pro is uninstalled (I also had ArcGIS Desktop 10.8 uninstalled as well, so if you still have that installed, you may want to take that into consideration at step 5 below) Sign in as user that was experiencing the issue of RuntimeError during import arcpy Open the Windows Registry Editor  Danger! Only do these steps in an environment you can recover catastrophic failures with, as Windows Registry is a core component of the Windows OS and can cause instability or corrupt the Windows OS. Proceed at own risk and if you know what you are doing! Note the settings for [Computer\HKEY_CURRENT_USER\Software\ESRI\ArcGISPro] are:                       Make those > ArcGISPro settings look like so:                                     Close Registry Editor Sign out the user from Windows, Sign the user back in  Test using Server’s Python 3 command prompt:                                                                          Reinstalling ArcGIS Pro after this point still results in a success as above. We will not have that user sign in to ArcGIS Pro out of concern that it might cause issues again (we've burned too much time on this issue at this point and must march forward.) I hope this solution works for others - it was hard to discover! ... View more