Latest Contributions by CalebAnderson2

Someone asked a similar question here with no replies so I'll ask it again in a different way. Is it possible to auto-populate a field (in addition to the unique ID) from a parent feature service to a related record? I currently have my unique ID auto-populating when creating new related records but I would like other fields to transfer to my related record as well. For example, I would like the manhole # and the serial # of the monitor to transfer from the original point feature service to the related table (maintenance records). Auto-populating fields would save the field-guys from typing this info over and over. I've experimented with a few varieties of relationship classes without success. Any ideas would be great. Thanks Message was edited by: Caleb Anderson Contacted ESRI and was told by support that this is not possible Message was edited by: Caleb Anderson The best I could come up with for a workaround (after deep-diving into some other forums) is to move the data from the cloud to our local SDE. Our main brain GIS people will make the data available for collector and field collection work-flows will continue as usual. With the data stored locally, I can automate the following tool to "auto-populate" specified fields (field personnel leave the field blank and the tool runs nightly and replaced null values with data from a parent feature class field): The "Calculate Field" in the above model builder tool has the following script: I tried it out locally and it works but I haven't tried it through our SDE yet. There will have to be some coordination to make this happen but I don't see why it wouldn't work. ... View more

I have a web map with the same feature layer shown twice in the table of contents. Once to show type and once to show maintenance status. The problem with this is when clicking on the feature, the pop-up shows "two records". These are actually the same record and it's confusing to some. In order to make it more simple, I removed the pop-up for the maintenance layer. This isn't a problem when using an Android device. Trying to edit a feature with an iOS device in this scenario provides a message that states "Select a feature to view details". ... View more

I've been struggling with the best way to symbolize both the type and status of an asset in Collector. I'm working with several types of waste water flow monitors that are either operational or in need of maintenance. We're trying to work it so the field crew, in part, get's their task list by looking at the web map to identify monitors in need of maintenance and planning their route and schedule accordingly. All maintenance needs and maintenance performed are stored in related and nested tables. Attempt #1 (Fail) Created two fields for the monitors feature class (type and status) Made a copy of the feature class in the table of contents using ArcMap and symbolized each copy by either type or status (skull and crossbones at the request of the monitor repair techs) Upload (share) as ArcGIS service, add to web map, use with collector, etc. The problem here is that "adding data" to related tables either crashes collector (Android) or just wouldn't show up (iOS) . Attempt #2 (Mostly Success) Upload the data without a duplicated copy of the feature class (just the monitors) Create a copy using ArcGIS Online and change the symbology This works great other than I'm limited on the symbology (Web Map vs. ArcMap); pretty trivial but the techs won't get their skull and crossbones. How are other people symbolizing type and status. Is there a better way? ... View more

I am having problems with related and nested tables using Collector on iOS. I tried uploaded my own data which gave me a couple issues so I uploaded the map package provided with this blog (hydrants). I am still experiencing the same problems… Problem #1 1. Select hydrant 2. Add new hydrant inspection 3. View hydrant inspections (related table). This screen is blank. When viewing this screen before there are any related records it says “no records” and after adding a record, it’s just blank. The records are there when viewing the maintenance related table on the web map; just not in Collector. Problem #2 1. Select hydrant 2. Add new hydrant inspection 3. Scroll to the bottom and there’s no nested table. According to the blog tutorial, there should be a “Violations” nested table here. The blog comments suggest it worked for some but I’m not sure of their mobile operating system. I’d test this on an android device if I had one. *** Update *** I have since tested this map using an iphone 5 and some kind of Android Verizon phone. Both of which worked just fine! Apparently Collector (10.3) related / nested tables doesn't work on my antiquated iphone 4. Has anyone else experienced this? ... View more