Latest Contributions by CraigCrowe

I have the Auto-populate of Lats and Longs working, but it only populates in Decimal Degree, is there any way of showing the results in the fields in Degree, decimal minutes? ... View more

Just an update. I spoke to the WMS service provider and found out that our server address had to be added to their Whitelist to enable access to the WMS. That was done, but in the process found another piece of information which has put the brakes on us accessing the WMS. ESRI in their infinite wisdom has disabled the ability to access HTTP addresses ("Allow access to the portal through HTTPS Only" button in Security settings is now not an option to turn off), so we can't access the WMS until the WMS provider creates an HTTPS version of the WMS. Thanks ESRI! ... View more

Hi Pete, You may have a point. We are accessing Online through a secure URL. I will have to see if I can get a secure WMS created, to see if that fixes the problem. Thanks for the reply. ... View more

After testing in the Collector app again, we have now discovered it is the actual app that has the Username issue. I downloaded an area and went "offline", captured a couple of points and saved. Before I went back online I reviewed the captured data and the CREATED_USER and LAST_EDITED_USER fields were auto-populated with my managers name. I am definitely logged in under my name. This is quite concerning as we won't be able to track who captured the data for further reference! Is there a chance that when my manager created my login that I was created as an "alias" and therefore when I capture data it is saving as his username? UPDATE - We discovered the CREATED_USER and LAST_EDITED_USER fields are being populated in the name of the "Owner" of the Feature layer, not the person who captured the data. Again this is not going to work for us as the person who owns the data is not going to be the one capturing the data. We may have over 20 people capturing data in the field but we can't track this work as it always populates with the GIS person sitting in the office. ... View more

My manager and I have found that the problem doesn't actually lie with populating the current user, but the fact that when the features sync to the sde, then the "Initial visit by" ('CREATED_USER' field) and "Last updated by" ('LAST_EDITED_USER' field) attribute fields get filled in as my manager's username, not my username even though I collected the data and he didn't edit it. Any ideas on this problem? ... View more