Latest Contributions by RyanUthoff

There are a couple ways you can track changes to your data. The first way would be to create an automated process to copy your data from AGOL into a local GDB of some sort. If you ever needed to revert back to an old record, you'd have all of the historical data. The second way would be to take advantage of the Extract Changes functionality. The support articles I listed below are referring to ArcGIS Enterprise, but you can also enable Extract Changes on an AGOL feature service as well. https://developers.arcgis.com/rest/services-reference/enterprise/extract-changes-feature-service/ https://support.esri.com/en-us/knowledge-base/how-to-enable-extract-changes-on-hosted-referenced-feat-000036676 https://support.esri.com/en-us/knowledge-base/how-to-recover-deleted-feature-from-a-hosted-feature-la-000037178 https://community.esri.com/t5/arcgis-online-questions/hosted-feature-layer-change-log-access/td-p/1156946 I've never needed to use Extract Changes before, but I just tried it on an AGOL hosted feature service and the functionality seems to work for me.

I was curious about this so I tried to replicate your scenario in ExB. I was able to replicate it, and I can provide some insight on the query that ExB is actually using. First of all, you can validate this yourself by opening your ExB app and opening the query widget. Then, open up your browser's dev options to view the internet traffic. From there, you will be able to see the requests that ExB is sending to the server, which includes the query from the query widget. You might have to click a few of the requests to find the one you're looking for, but you will be able to see the query that ExB is sending. In your case, it appears that ExB is sending a query you're not expecting. This is the query: (County IN ('Lincoln')) AND (Era LIKE '%19th Century%') OR (Era LIKE '%20th Century%') Notice that if you select multiple eras, it is treating them separately (putting them in separate parenthesis) vs. the query that you are expecting it to be. So that is the root of the problem and why you're not getting the expected results. I don't know if this is by design or not. Honestly, I would have expected the same behavior you are expecting if I were to configure the SQL Expression Builder the same way you did. In my mind, if a person selects multiple eras, it should put that in one big parenthesis block instead of a parenthesis for each era. Edit: It looks like someone beat me to the solution lol. And bonus points for them for actually knowing why the problem is happening lol.

Does your workflow require you to create a version for each downloaded map, even if it is for the same user? Or, would creating a single version per user (regardless of the number of times they download it) be an acceptable alternative? See here: https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/prepare-feature-layer-data-for-offline.htm Regardless, based on the documentation I'm reading, it appears that you do need to delete the replica versions manually. Esri will automatically delete the feature service replicas, but not the actual version replicas that are associated with the feature service replicas. In fact, you won't be able to delete the version replica until the feature service replica has been deleted. Some helpful documentation: https://enterprise.arcgis.com/en/server/latest/publish-services/windows/offline-maps-and-versioned-data.htm https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/replica-versions-in-offline-workflows.htm

When publishing a S123 form to Portal using S123 Connect, it creates a folder on your content page where it places the survey and the content associated with it. By default, Esri prefixes the folder name with "Survey-" (ex: Survey-Inspection Survey) When you delete a survey through S123 Connect, it will delete the associated survey folder. However, there is a specific scenario where S123 Connect will delete a different folder and not the associated survey folder. For some organizations, it is a common workflow to change ownership of S123 forms so other people can make changes and republish them. In this scenario, a user might change ownership of a survey and insert it into a different folder in their content. Note that this folder is NOT the original survey folder that was created when initially publishing the S123 form. After changing ownership, the person then downloads the form through S123 Connect so they can make changes and republish. However, in the event that the end user needs to delete the survey through S123 Connect, it will delete the folder the survey is currently located in and not the original "survey" folder that was created when the form was originally published. While S123 Connect gives you a warning that it will delete the survey and the survey folder (along with all of its contents), the wording is misleading as it indicates that it is going to delete the survey folder, which in my opinion, indicates the original survey folder that was created when originally publishing the survey. Here is the warning S123 Connect gives: An end user might place the survey in their own folder with other content in it. At this point, I would not consider this the "survey" folder. It's just a regular folder with content in it. And when you go to delete the survey through S123 Connect, it will delete everything in that folder, including non-S123 related content that you do not want to be deleted. This is incredibly dangerous. My idea is that Esri needs to clarify the wording S123 Connect provides when deleting a survey to indicate that it will delete the folder (and all of its content) that the survey is currently located in and not the "survey" folder which is a little vague and misleading.

I don't think 12.0 was necessarily a re-architecture of anything where you'd absolutely have to be on Pro 3.6. The 12.0 release signifies more of a removal of features and functionality, like the classic map viewer, Web AppBuilder, etc. But generally, 3.6 and 11.5 should work pretty well together. Like I said, there could be new functionality released with 3.6 that isn't compatible with 11.5, but I'm not sure what that would be right off. One example that happened to me in the past was when Esri released high-precision date fields. We upgraded Pro but not Enterprise, and we couldn't publish feature services with high-precision date fields enabled. We could work around that by not using them, but that's just an example of a compatibility issue.

Using the same version of Pro/Enterprise is best practice and is what is recommended, but generally, you should be okay if you use Pro 3.6 with Enterprise 11.5. The biggest concern would be any functionality released in 3.6 that isn't compatible with 11.5. From Esri's documentation: Although earlier and later versions of ArcGIS Pro and ArcGIS Enterprise work together for most functionality, pairing companion versions is recommended. When that isn't possible, staying within a range of two companion versions is recommended. The table below lists the companion versions. https://pro.arcgis.com/en/pro-app/latest/get-started/release-notes.htm

I'm not sure if this would be an acceptable solution for you, but you might be able to do that through AGOL Notebooks. You'd be able to define your own SQL expression to calculate the Unique ID in the format you are needing. The downside is that the calculation wouldn't be immediate. The AGOL Notebook would run either on demand or on a schedule. https://community.esri.com/t5/arcgis-online-questions/auto-calculate-unique-id-in-hosted-feature-service/td-p/1153764 Attribute rules would be a good solution, but that only works on ArcGIS Enterprise and not AGOL unfortunately.

If I entered an invalid value (according to the attribute rule) in the Editor widget form, would the attribute rule send an error message to the Experience Builder form? Yes, Editor widget form will give you an error message. What would the error message look like in the form? Is it a generic ExB error message, an attribute-rule-generated message, or a user-defined error message? Regardless of the error number/description you provide in ArcGIS Pro, the Editor widget form will only give you a generic error. See screenshot below. When would the error be thrown? When the value is entered into the field, or when the feature is saved? The error will be thrown when you click the "Update" button in the ExB form. It would be great if Esri would display the attribute constraint error you define in ArcGIS Pro in the map viewer (including ExB, etc.). I actually created an ArcGIS Idea about this last year. https://community.esri.com/t5/arcgis-enterprise-ideas/portal-map-viewer-should-display-attribute/idi-p/1629217

Do the maps render within Esri applications coming from the web adaptor? If you're able to test that, then you can isolate it to being a problem with Esri vs. the third party applications.

It depends on how you have defined your split model settings in ArcGIS Pro. By default, it uses the Update/Insert model. In the case of the Update/Insert model, the biggest polygon retains the original ObjectID, while the smaller polygon gets the new ObjectID. Documentation: https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/defining-feature-class-properties.htm#ESRI_SECTION1_C4DE6D7BC03247B2A10F4DC9BFCD768D

@DavidColey That's a good point for the Web Adaptor. It would be nice for that to be included in the "About" section as well, although I'm not sure how feasible it is since all it does is integrate with an existing web server. With that being said, I actually created an ArcGIS Idea 2.5 years ago to include Web Adaptor patches in the ArcGIS Enterprise patch utility. It's supposedly "in product plan", but after 2.5 years, it's either been forgotten about or pretty low on the priority list. https://community.esri.com/t5/arcgis-enterprise-ideas/include-web-adaptor-updates-in-arcgis-enterprise/idi-p/1313727

@DavidColey Ahh, I see that is a new feature added in 12.0. I'm just one version behind, so it looks like I barely missed out on that feature for now. Regardless, seeing the Available Patches needing to be installed would also be a good feature to have, so I'll leave my idea up.

Currently in ArcGIS Enterprise, the only way to see the patches currently installed (and/or needing to be installed) is to open the ArcGIS Enterprise patch utility directly on the servers itself. This complicates things as you have to RDP into each machine in your deployment, check the patch status, etc. My idea is to centralize all of that information in the "About" section of Portal (Organization > Settings > About). The "About" page already includes information for all the machines in the Enterprise deployment such as Portal version, Server version, etc., so why not expand the information on that page to include the patches currently installed per machine? And not only that, but also include the ability to check for new patches from the "About" page as well. I'm not necessarily saying we should have the ability to install patches from the "About" page, but just listing the patches currently installed as well as the patches needing to be installed would be a HUGE improvement over the current process we have now as we won't have to RDP into each machine to get the current patch status. So to sum it up, my idea is to include the currently installed patches, as well as patches needing to be installed, on the "About" page in Portal for all machines in the ArcGIS Enterprise deployment. Edit: It has come to my attention that installed patch information is available in the "About" section starting in ArcGIS Enterprise 12.0. However, it would still be nice to include patches that need to be installed in the "About" section as well. We still have to go to each machine to get that information and it would nice for that to be centralized in the "About" section.

‎04-15-2026

Also, I missed the part about the versioned data. Versioned (traditional) data is also not supported (unless you use S123 Classic v2.9). Your data will need to be un-versioned in order to enable supportsApplyEditsWithGlobalID. From the blog post, it must meet these requirements: So just adding GlobalIDs won't be enough. You'll also need to un-version it, but be very careful about doing that. Un-versioning can potentially result in data loss if you don't fully compress the DB first, not to mention any dependencies on versioned data that might break. I'm not sure if it will work with branch versioning or not.

‎04-15-2026

Have you tried following the steps in this blog post so "supportsApplyEditsWithGlobalID" can be set to true? https://community.esri.com/t5/arcgis-survey123-blog/how-to-enable-supportsapplyeditswithglobalids-on/ba-p/893977 You said that you do not have GlobalIDs. GlobalIDs are required in order to enable supportsApplyEditsWithGlobalID.

Online Status	Online
Date Last Visited	11 hours ago

My Ideas

Latest Contributions by RyanUthoff

Re: Tracking/Auditing/Safeguarding original GNSS points in AGOL

Re: Experience Builder Query Widget SQL Expression Builder AND with 'contains' not working

Re: What is the intended way to clean up after utilizing offline maps?

Clarify S123 Connect Wording when Deleting a Survey to Indicate it Deletes the Folder the Survey it is Currently in and not the Actual Survey Folder

Re: Upgrading to Enterprise 11.5 and need to use Pro 3.6 due to a Bug in 3.5.x Is this OK?

Re: Upgrading to Enterprise 11.5 and need to use Pro 3.6 due to a Bug in 3.5.x Is this OK?

Re: Use database sequence function from AGOL layer/table to generate unique integer IDs?

Re: Would a Portal/EGDB constraint attribute rule error message be passed to the ExB Editor widget?

Re: ARCgis page does not render Version 11.3

Re: How does Pro determine which part keeps the original Object ID when splitting a polygon?

Re: Include ArcGIS Enterprise Patches Needing to be Installed in About Section of Portal

Re: Include ArcGIS Enterprise Patch Status in About Section of Portal

Include ArcGIS Enterprise Patches Needing to be Installed in About Section of Portal

Re: Existing Feature Service (Layer) Does Not Have GlobalID So Cannot Create New S123 (also versioned so cannot sync)

Re: Existing Feature Service (Layer) Does Not Have GlobalID So Cannot Create New S123 (also versioned so cannot sync)

How to access ArcGIS Data Store Full Vacuum Comman...

Re: Tracking/Auditing/Safeguarding original GNSS p...

Re: Experience Builder Query Widget SQL Expression...

Re: What is the intended way to clean up after uti...

Re: Upgrading to Enterprise 11.5 and need to use P...