Latest Contributions by LindsayRaabe_FPCWA

I find many apps now allow you to let your mobile device remember your login details and instead use your biometric infomation (fingerprint/facial recognition/iris scan). This would be a useful feature for logging into Field Maps instead of having to retype your username and password everytime.  ... View more

When logging into your ArcOnline account (and I assume Enterprise accounts have the same problem), a lot of users struggle to enter their Password correctly the first (second and third) time as it only shows the most recent leter you've pressed. Many login functions have a check-box to "Show Password" so you can review it in full before hitting submit. Whilst on a PC or larger device, typing is relatively easy, mobile devices can be more difficult, especially for less tech savvy users with "fat finger syndrome".  ... View more

Background: After using Collector Classic, Collector and now Field Maps for quite a while, of all the technical support requests we get in the GIS team from our Field Staff who are working with offline areas, the majority tend to be solved by removing an offline area that they have had on their device for an extended period of time and downloading a new offline area. Over time, small changes and tweaks to maps and feature services (and sometimes ever where no discernable changes have occured) can result in long-held offline areas no-longer matching the online environment 100%. Unfortunately, users don't become aware of this until they try and save a feature and instead get an "Unable to save" type error. This may occur in one layer, but not another layer. Despite myself and my colleagues telling people they need to regularly remove offline areas and start "fresh" with a new copy, especially if they haven't used an offline area in a while, it falls on deaf ears or just isn't thought about.  My proposal: Include the option at an organisational level to include an expiry timeframe for offline areas. For example, I set in the org settings an offline time limit of 90 days. Any offline area taken will automatically expire and be removed after 90 days. Warnings could be "pushed" to users devices or email address (automatically) annoucing when an offline area is X days from expiring. Offline areas with features yet-to-be syncronised could be set (org level) to either sync automatically prior to expiry, prompt user to sync/discard and then the offline area expires, or discarded automatically upon expiry.  Bonus Functionality: An org setting that enables the automatic background renewal of offline areas upon expiry (remove it and redownload using the same settings in the background) with the option to occur only when connected to Wi-Fi or Cellular data (are data caps really an issue anymore?).  Upvote away people 😉 ... View more

Hi Brains Trust. I'm working on a model and starting to delve deeper into parts I've not really used a lot before - especially not in combination. Here's the scenario.  I have a feature class that contains a field called DateS which contains date stamps formatted like this: 2020-11-16T00:02:58.096Z I want to be able to iterate through all the different dates in that column (easy enough using Iterate Field Values), extract the Year and Month (I assume that will be Get Value) and then run a formula to calulate the Australian Financial Year (July - June) that the date range falls in. Example of some output values; Input from DateS       -      Output as Financial Year (YEAR-Y1) 2020-11-16T00:02:58.096Z       -      2020-21 2020-06-16T00:02:58.096Z       -      2019-20 2019-10-16T00:02:58.096Z       -      2019-20 2019-03-16T00:02:58.096Z       -      2018-19   ... View more