Latest Contributions by RyanUthoff

You are correct. Embedding/storing credentials on the Portal service (technically, the AGOL service that you are adding as an item on Portal) has to be with a built-in account. The built-in account would need to be on the AGOL side in your scenario. I'd recommend a built-in "service" account on AGOL that you can use when storing the credentials on Portal. It would be used solely for storing credentials on services on Portal. ... View more

Hey @CodyPatterson  I did find an Esri video where they did a demo that confirms that setting the portal URL within an MDM automatically opens the sign-in page when opening Field Maps. You can see how it works by starting at 24:00. I guess maybe that doesn't work for everyone like in your case though. https://www.youtube.com/watch?v=3UIIRvdWGcM&t=1440s ... View more

Hmm, that's odd. I'm not able to (easily) test the MDM myself, just going off what the technical paper said. Esri is claiming you can bypass the default screen, but also, I wouldn't be surprised if that is not correct or if the wording is misleading though. At least it provides a pre-set URL, which I suppose is better than nothing. But I also agree that it would be nice to bypass the default page completely. ... View more

I believe a solution for this already exists. When managing the app through an MDM, you can pre-configure the Portal URL which will bypass the default screen where you select AGOL or Enterprise.   More information can be found in this technical paper: https://support.esri.com/en-us/technical-paper/arcgis-mobile-apps-and-mobile-device-management-mdm-sup-3619 Edit: Some people have had mixed results with this method with it still showing the default screen, but allowing you to pre-select the Portal URL when logging in. I'm just going off what Esri is claiming how it works in the technical paper. Edit: See this youtube video for a demo on how it works: https://www.youtube.com/watch?v=3UIIRvdWGcM&t=1440s ... View more

The problem is that we can't force replicate the issue. It just happens randomly so that made it hard to troubleshoot. The problem magically went away, and then it suddenly came back within the past 2 or 3 weeks. But nothing has changed, so we don't know what happened. I don't remember them recommending one type of versioning, but it's ONLY happening on our tables that are registered as versioned (traditional). Non-versioned tables are fine, and we don't use branch versioning. Branch versioning is Esri's next generation of versioning, so I think that's what Esri would recommend. ... View more

Nope. Esri support couldn't figure it out either. Still happens to us from time to time and we have no idea why. ... View more

I think this question is going to be best answered by your Esri customer service representative. With that being said, where/how are you determining that the Viewer User Type does not have a Named User License? Here is what Esri's Master Agreement says: By those definitions, a Viewer User Type is a named user because it is an account assigned to a person (which is a named user) used to access AGOL (which is a specific Esri offering). And then if we look at the definition of a Named User, we see that Esri refers to it as a single person. I'm just curious on where you're reading that Viewer User Types are not Named User Licenses like other AGOL licenses? ... View more

I'm assuming you're wanting an out of the box tool, but the Esri Python API can certainly accomplish what you're wanting. ... View more

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! ... View more

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. ... View more

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.  ... View more

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   ... View more