Latest Contributions by RyanUthoff

It's all good. I appreciate your response and I am glad I was able to find a workaround. Unfortunately, Field Maps has the same "bug" that the new Collector (not the Collector Classic version) and Explorer apps (after v.18.1.0) has that makes the app essentially unusable. All three apps have a variation of the same error message. This is when we sign in to the app with our Portal logins and does not apply to AGOL. In Field Maps, if I open up the layer list for a map, under each layer name, it says "Token Required" and it can't load any of the data. In Explorer, it used to say "User cancelled the authentication challenge", but with the latest version of the app, it just keeps on taking me to the Portal sign in page when I open a map. No matter how many times I enter my credentials, it just keeps on asking me for them over and over again. Eventually, if I click the X button to close the sign page enough times, it gives me an error message for each layer saying "super.handleChallenge(challenge) must not be null." I made a Geonet post when I originally reported the problem (Explorer for ArcGIS Error - User Cancelled Authentication Challenge). I also opened a case with Esri support. I was told back awhile back from Esri that it should be fixed around now. I was really hoping that Field Maps would include this fix, but it does not. So we're still stuck with sideloading an old version of Explorer and Collector Classic until it gets fixed. Since this is with Field Maps, I can open up another support ticket with Esri, but I don't want to be that guy who continuously submits bug reports for the same issue. ... View more

I actually found a workaround. Once you get to step 9, go to your Portal home page and find the newly added ArcGIS Field Maps Application in your content. Click on it and go to settings.  Click "Register" and enter the two Redirect URIs. After you click "Register", copy the app ID and follow steps 12-15 like normal. After doing this, I was able to use Field Maps. ... View more

I will add that I received the error message with two different Enterprise deployments.  ... View more

Glad it isn't just me. I commented on the blog post with my issue and Jeff said to reach out to support. It's near the end of the day for me, but I'll reach out to support tomorrow. If I have any solutions, I will post them here. And if you have a solution before me, I'd appreciate it if you post it here! ... View more

I had problems with steps 9/10. I receive an error message saying unable to register app. Error 500. 'redirect_uris' invalid. I'll be reaching out to Esri tech support to see what is going on with it. ... View more

I saw that Jeff replied to my comment on his blog post about registering Field Maps with Portal. Here are the instructions. 1. Open the ArcGIS Portal Directory and login as a member with administrative privileges. The URL format is: https://webadaptorhost.domain.com/webadaptorname/sharing/rest 2. Navigate to the administrative user’s content. http://webadaptorhost.domain.com/webadaptorname/sharing/rest/content/users/ 3. Under Supported Operations choose Add Item. 4. In the Add Item form, enter: Title: ArcGIS Field Maps Type: Application Type Keywords: Application Tags: ArcGIS Field Maps 5. Click Add Item. 6. On the User Item page, under Supported Operations, click Share Item. 7. On the Share Item page, set Share with Everyone to True, click Share Item. 8. On the User Item page, select and copy the ID value. 9. Under Related Operations, click Register App. On the Register App page, enter: Item ID: This is the ID copied in step 9. App Type: Select multiple from the dropdown Redirect URIs: Enter [“urn:ietf:wg:oauth:2.0:oob”, “arcgis-fieldmaps://auth/”,”arcgis-fieldmaps-beta://auth/”] – This value allows the successful authentication response to be sent to the portal URL. 10. Click Register App. The Registered App page displays the App ID. 11. On the Registered App page, copy the App ID value. 12. Open the ArcGIS Portal Administrator Directory and login as a member with administrative privileges. The URL format is: https://webadaptorhost.domain.com/webadaptorname/portaladmin 13. Navigate to Home > Security> OAuth> Change App ID. 14. On the Change App ID page, enter: Current App ID: This is the App ID copied in step 11. New App ID: Enter “fieldmaps” 15. Click Change App ID. ... View more

No, unfortunately Esri never gave me a bug number for this. They acknowledged that it was something they were aware of (I guess before I contacted Esri support), but they did not tell me the bug number. To my knowledge, it still has not been fixed. We are now within the 3-4 month time frame of when Esri said they anticipate it would be fixed......and it has still not been fixed. I downloaded the latest Explorer update released this week and I am still experiencing the same issues. ... View more

Oh my goodness, that is exactly what it is! Once I change it to Geodesic in ArcMap, the measurements between ArcMap/Pro and the web map match up. I've been trying to figure out why the measurements didn't match for awhile now, and it was just a little setting in the measurement tool. Thank you for your help! ... View more

Hi Rachel, Thank you for replying back. I understand that reprojecting data can cause accuracy loss. However, in this case, I can replicate this among multiple datasets, even datasets I create in Web Mercator. So even in cases where the original dataset that I create is in Web Mercator, I am still seeing a significant size difference between what ArcMap is displaying vs. what the web maps are displaying. I would expect this if the server was reprojecting the data into another coordinate system, but in this case, the data is already in Web Mercator so I'm not sure why there is such a large difference in size. ... View more

As an alternative to exporting to Excel, you might be able to use the FME AGOL Feature Service Reader to read your feature service from AGOL. This would eliminate having to manually export to Excel and relying on field names to be in the correct order. Esri ArcGIS Online (AGOL) Feature Service Reader/Writer  ... View more

I think this would be a very useful feature, but I can see how it might be hard to implement, or might give misleading results. Typically, it is up to the user who is publishing the data to be aware of feature service best practices. Of course there are several Esri documentation articles and videos regarding this. The reason why I think that it might be hard to implement is because feature service behavior is dynamic. It can depend on the data. For example (assuming this is a traditional feature service and not hosted), you publish a feature service with only 5 records, but then add one million records in the EGDB. That has the potential to negatively affect the performance, but the feature service has already been published (with no need to republish) so the analyze would not be useful in this case. Also, the server environment is dynamic. Feature service performance can vary if the server is under high load or if many people are using the feature service you published which the analyze functionality wouldn't be able to replicate. In your case, your server is having issues drawing features with 250,000+ vertices, but it's possible that other servers may not have issues. Maybe it would be nice to have a "stress test" functionality within ArcGIS Pro that would test the feature service under different scenarios, but that would require the feature service to already be published. I could also see how the "stress test" functionality could be a little dangerous, especially in a production environment. At the end of the day, I think it would be great to have this feature in ArcGIS Pro. But it would still be up to the user to determine if it is truly a "problem" or not for them because as I said, every server environment is different. ... View more

Thank you for your reply Andrew. This helps me understand how AEC project delivery works a little better. I understand that our end users would require two forms of authentication: the AGOL account along with our internal Portal account. Is it possible to do any sort of pass through authentication so that the AGOL account can authenticate with the Portal account without the end user needing to authenticate with Portal? For example, when adding a server feature service to AGOL as an item, I have the option to store the Portal credentials with the feature service so that way the end user in AGOL does not have to sign in to Portal to view the feature service. Is that an option with distributed collaboration and AEC project delivery? Thank you for your help, I really appreciate it. I'd be happy to talk to you about this, especially if there is going to be a complicated solution (if there is any) to my question above. Plus, we might have more questions in the future about AEC project delivery and it would be helpful to have someone to reach out to. Thank you! ... View more