Latest Contributions by MelanieWawryk

That is much better, thank you! ... View more

Why should we have to create, maintain and train on two apps for every project? Staff love Field Maps, it should have been released for natively for Windows right away. We don't need an experience for editing, we just need to use the same great field editing app on a desktop. ... View more

That would work and it would mean we wouldn't have to make and maintain two apps for every task (one in field maps and one for in the office) We could just consume the original field map with the widget and be able to use it on any device including windows desktops. ... View more

I can answer that. We have two issues related to the subsystem. The first is our server are not compatible with Windows 11 so it will be a while before we can upgrade from Windows 10. At the same time, I asked about the subsystem and they said it was a security risk so they would not approve it. Perhaps both opinions and restrictions have changed by now. It would be helpful if there was a white paper explaining how it all works and why it is not a risk that we could take to our network and security teams to try and convince them. As far as why we need it. We have field staff that use Field maps in the field. When they come into the office or their supervisors are in the office, they use their computers to make updates. We also have support staff that are in the office that enter data as well. All three groups would like their app on the computer to look and feel like the one in the field. Instead, we need to try and replicate the app using web application builder or experience builder. It would be so much simpler to just have one field map that can be used in the field and in the office rather than having to create two apps to do the same thing. Additionally, some of our field staff use tablets. This is both for the screen real estate and so they can keep utilities drawings that are pulled up through hyperlinks in a local viewer from their laptops. There are thousands of drawings and tablets do not have enough storage space. They use a local copy of data and the plans for emergency use when there is no power or internet so can not switch to using a tablet. They would also like to have field maps on the laptops. Let me know if you have any additional questions. Thanks Melanie Melanie Wawryk MSc. GISP ... View more

Thanks that is a good suggestion. Ideally, it would be nice if there was a config file where you could specify codes you don't want to see in the manager log window. The admin filter works all right; you need to switch to the admin though and add in the dates.  Having an additional filter like the one in admin for codes when looking through the manager log would be a nice addition. Alternatively, Esri could move that error to verbose or fine since it doesn't impact the server in any meaningful way and you were already warned about it when publishing. ... View more

It is a huge security risk having "Use in ArcGIS Field Maps Mobile" enabled by default. This should be an easy fix to have it off by default. @HollyTorpey_LSA I agree much easier to remember to enable it because you are actively working on creating the app. A bit of an oversight that should be corrected ASAP 🙏 ... View more

Any chance you could get rid of the Type of Layer: 'Name of group' is 'Group Layer', which is not supported. It really clogs up the logs ... View more

We ended up using Kobo Toolbox https://www.kobotoolbox.org to create a survey for work permitting that required several documents to be uploaded. We then use FME to convert the survey into our enterprise geodatabase with fields with hyperlinks to each of the different types of documents downloaded with FME to our document server. There wasn't enough control over multiple uploaded documents within Survey123 mainly when the uploaded files are not all the same type of document.  ... View more

I completely appreciate your work on this. However, I think trying to create it as a subsystem app is the wrong direction to go. It should be a native windows app. It needs to be re-developed for windows,  not an android app in a container on windows. I understand that it would mean developing two similar but not identical apps which is way more development time on your end, but the way it is currently being developed leaves it out of reach for most customers. The important part is that the field map document on AGOL can be used by both the Windows desktop application and the android/iOS app. ... View more

I agree with @rsun_TQB; we need a native Windows app. I will test the beta at home, but adding an Android subsystem in a corporate environment will never pass the security sniff test. And then requiring Amazon accounts will never work. We also can't upgrade to Windows 11 because it isn't compatible with our network drives. The current solution is not an acceptable solution for a corporate setting. Please go back and create a windows app, your customers deserve it. ... View more

Please just develop it natively on Windows! We shouldn't have to add a subsystem and sideload things to enterprise systems to run a program. It's not like Windows in an obscure operating system, and we have invested in enterprise Corporate GIS. We are not some small shop that can just cobble a solution together. This sounds like something you would code in your basement. You are forcing us to move from Collector which had a Windows version to field maps which is a great improvement however making Field Maps available on Windows was just left out of your plans. Sorry, you really need to provide it, you can see that it is a requirement for many organizations. There is no way sideloading a subsystem will be approved on our corporate network. ... View more