Latest Contributions by RyanUthoff

‎10-29-2025

Ahh, gotcha. And after thinking about it, the documentation I provided probably wouldn't work for you anyway because I believe it would be created as a read-only feature layer view (which is confusing because you can create editable hosted feature layer views). The duplicate layer shouldn't cause it to lose sync, because it's still pointing to the original underlying source data. But like I said, it would be read only since it's based off a referenced feature layer. Unfortunately, that's the only ideas I have. Maybe someone else here will have some other ideas!

‎10-29-2025

Honestly, I think your best bet is to work with your third-party company to provide you with feature services that meets your needs. It might be difficult to implement a solution for services that you do not have any control over. With that being said, are the feature services the third-party is providing hosted feature services? You said "third-party hosted feature services", but I'm not sure if you meant feature services hosted by the third-party, or if they're actually hosted feature services. If they are hosted feature services, then you'd be able to create a view layer from it which I believe would accomplish what you're needing. If they are referenced feature services, this documentation might help. However, you mentioned that you do not have server admin access. If that also includes not being able to publish feature services, then I don't believe this solution would work either.

‎10-29-2025

Unfortunately, I don't believe it is possible as of 11.5. This doesn't directly address FGDBs, but here is some 11.5 documentation regarding preparing data to publish a feature service. It lists relational databases, cloud data warehouses, and enterprise geodatabases. It does not mention file geodatabases.

‎10-17-2025

I reached out to Esri support and learned there was already an enhancement submitted for this. ENH-000163207 It was submitted in November of 2023, and last updated in June of 2024. Considering it's been over a year since it's been updated, I can only assume that this is very low on the priority list for Esri and that everyone who uses Microsoft as their email platform is going to need to have contingency plans in place for when Microsoft officially deprecates legacy authentication. I created an ArcGIS Idea to hopefully get some more visibility to this issue. But realistically, I'm expecting anything MS related to break within Portal once MS fully shuts down legacy authentication. https://community.esri.com/t5/arcgis-enterprise-ideas/portal-email-support-microsoft-modern/idi-p/1658743

‎10-17-2025

Currently, Portal does not support Microsoft Modern Authentication when configuring email settings within Portal. Portal only supports basic/legacy authentication. This presents multiple problems because Microsoft is deprecating legacy authentication in April of 2026. Without Modern Authentication support, it will be impossible for organizations to configure Portal Email Settings which also means it will be impossible for organizations to implement MFA for their built-in Portal accounts (because even configuring MFA requires the Portal emailer to be configured). So at minimum, once legacy authentication is deprecated (for those who use Microsoft email), Portal's emailer will be broken. And even worse, MFA will not be able to be configured because it requires the Portal Emailer to be configured first (although maybe Portal doesn't care if the emailer actually works for MFA to function, I'm not sure). Not being able to configure MFA goes directly against Esri's hardening guide for ArcGIS Enterprise. So ideally, we'd like Esri to support Microsoft Modern Authentication so we can implement the security best practices that Esri recommends. Note that changing email providers or using non-built-in accounts might not be an acceptable solution for everyone.

‎10-16-2025

Does Portal support Microsoft Modern Authentication for email notifications and MFA? I can't find any documentation stating that it does, and when reviewing the configuration for setting up the emailer in Portal, it doesn't appear to be compliant with modern authentication. With Microsoft (eventually) ending support for legacy authentication, we're going to need Portal to support Microsoft Modern Authentication in order for Portal emails and MFA to continue to function.

‎10-15-2025

Sorry, I said Portal because that's what I use, but that also applies to AGOL as well. You'd need to create a built-in AGOL account.

‎10-15-2025

It's not possible to store credentials with services using SSO accounts. You can only do it using built-in accounts (like yours). What we have to do is create a built-in Portal "service account" that is used specifically for sharing services where we want to store the credentials with the service.

‎10-10-2025

I think you're on the right track with that being the issue. It sounds like the DB is at a version too high for the currently installed ODBC drivers to be able to support. So the correct solution would be to review what version of SQL Server the client is using, then install the corresponding/supported ODBC drivers. At minimum, the client would need to check the version of SQL Server and the version of the ODBC driver installed on the ArcGIS Server machine to determine if there is any incompatibility. If there is an incompatibility, then installing a compatible ODBC driver should fix the issue. Otherwise, there might be another issue going on. But the first step would be to confirm the SQL Server and ODBC driver version.

‎09-22-2025

I've used this solution with good success. https://community.esri.com/t5/arcgis-online-questions/possible-to-find-out-where-feature-layers-are/td-p/1142174

‎09-22-2025

If you already have a workflow for separating the years (like using a TestFilter), then you can just use the Counter transformer for each year and each Counter will start at 0 (or whatever number you like). I'm sure there is a more elegant way of doing it, but that's the first way I thought of right off.

‎09-15-2025

Hmm, at this point, I think that's all the ideas I have. That's definitely some strange behavior and I'm not sure what would be causing that.

‎09-15-2025

Darn, I was hoping it would give more useful information than that......At least something a little more specific. It might be worth seeing if the data stores registered with the server validate in ArcGIS Server Manager. I'm not sure if there are any dependencies regarding that. Like Portal verifying the data store validates before it can change ownership or something like that. I'm doubting that's the case though, but might be worth checking.

‎09-15-2025

I haven't heard of this issue before. But one thing that might give you more information is watching the internet traffic when you get this error. Like opening up dev tools in your browser and seeing if it provides any additional information when you make the request to change ownership.

‎09-03-2025

Are the tables in the EGDB registered as versioned? Or is it non-versioned, but with archiving enabled? If the answer is yes, then you must edit the data the "Esri approved" way when editing directly in SQL. I'll include a couple links below that tell you how you can edit either versioned or non-versioned with archiving enabled data the "Esri approved" way when editing directly in SQL. The only time where you don't really need to do anything special is when the table is non-versioned with no archiving. While I haven't directly experienced your issue in a distributed collaboration, I have experienced this issue where we update the data in SQL, but then Esri doesn't recognize it. The solution is to follow the correct editing procedures in the documentation below. https://desktop.arcgis.com/en/arcmap/latest/manage-data/using-sql-with-gdbs/editing-nonversioned-geodatabase-data-in-sql-server-using-sql.htm https://desktop.arcgis.com/en/arcmap/latest/manage-data/using-sql-with-gdbs/edit-versioned-data-using-sql-sqlserver.htm

Online Status	Offline
Date Last Visited	a week ago

My Ideas

Latest Contributions by RyanUthoff

Re: Controlling User Editing Access On Feature Services

Re: Controlling User Editing Access On Feature Services

Re: Referenced Feature Services from a File Geodatabase.

Re: Portal Email/MFA Settings and Microsoft Modern Authentication

Portal Email Support Microsoft Modern Authentication

Portal Email/MFA Settings and Microsoft Modern Authentication

Re: How to secure services with SSO login?

Re: How to secure services with SSO login?

Re: Error with creating Data Store item

Re: How to find where feature services are being used in ArcGIS Online

Re: How can I restart a row counter in FME at the beginning of each year?

Re: Cannot change ownership of Data Store items

Re: Cannot change ownership of Data Store items

Re: Cannot change ownership of Data Store items

Re: Enterprise geodatabase replication to AGOL doesn't work when data is updated with SQL

Re: Order of Operations for Enterprise Upgrade

Re: No "Copy sent data to a new survey" option in ...

Re: ArcGIS Data Store upgrade 11.5 to 12.1 fails

Re: Limit the size of the ArcGIS Data Store

Re: Why Still Require a Security Question After In...