Latest Contributions by MiltonSolano

Hey @JustinReynolds , Thank you for your effort to help me on this. Your idea might work but unfortunately my project needs changing fields (adding, deleting, updating others) so, having scripts to store the state of my field seems overkill in this stage. I up-voted the idea to keep values when hiding things on FieldMaps. Maybe they can developed a "Switch" to allow to keep values or set them blank. Saludos, Milton ... View more

To rub more salt into the wound, Scenario 1: I have a smart form to census trees each year. We need to have last year measurements to compare and avoid mistakes. If the tree condition is dead, the all measurements are hidden, including last year measurements. When hiding the measurements, all last year measurements are lost forever! Those measurements should stay there even if the tree is dead. Scenario 2: I have codes to identify tree conditions (dead, laying down, vines, etc.) These codes have default values ("-","D") to use the switch input type. If the tree is Dead, then the remaining switch codes are hidden. But if by mistake, someone switchs ON Dead and the switch off Dead, all defaults are replaced by Null, rendering the switches to listboxes because there's no default value anymore. On my case, using conditional visibility and switch input is useless if the fields are set to null. ... View more

Hey @JustinReynolds , Thank you for sharing this piece of code. It might work with those fields where I can set a default value but then, there are other fields with old measurements that are lost forever. For example, tree height last year is lost  when hiding the field and so other fields. It doesn't matter if the field is marked read only. So the switch input type and conditional visibility is useless when there is read-only data for reference, because it will be lost if you make those field hidden. Milton ... View more

Thanks @JustinReynolds , My form is already loaded with so many calculated fields (tree censuses are really complex), so the idea of adding additional constraints it's a no-go for me. Thank you anyway for trying to help me. I wonder if the guys at FieldMaps are thinking about a solution to this behavior. That could be setting the field values to the declared default for the field but not Null! Milton ... View more

Definitely a necessary functionality for published layers. I tried the REST Admin endpoint workaround and doesn't work. ArcGIS Pro already have this tool: Assign Default to Field but it doesn't work with hosted feature layers. It's incredible the amount of work one have to do to fix this behavior: 1. Arcade is showing the default value on records with null value 2. We have to create another field, do a field calculation, delete the previous field. 3. Reorder the new field on the popup window and FieldMaps form. Create calculated field from the new added field. 4. Edit labels on the map to show the new created field. All of this for one single wrong default value. Please, implement this on the next AGOL release. ... View more

Folks, Tested on Android and the problem is there: if the calculated fields have names with a common root (in my case COD) then the calculations are ignored. I was breaking my head wondering why my arcade code wasn't working until I found this post and changed the field name to BAND_CODES instead of CODES_BAND to change the common root with other fields (CODES_TREES, CODES_DENDO). Wao, I was going crazy trying to figure out what was happening. I hope the folks at FieldMaps fix this inconvenient bug. Milton ... View more

@RhettZufelt, My man! I owe you a couple of beers. I couldn't figured it out by myself in a million years. Lessons learned through your help: 1. Never publish a Feature class with Labels defined from ArcGIS Pro. It's a headache. 2. JSON Lint. Thank you for sharing this tool. 3. A real world example to use Notebooks. I used AGOL Notebooks to make these changes instead of ArcGIS Pro. 4. I executed the Python code against the Feature Layer (the original layer) and the 3 Views created from there. Although, the original layer changed the definition, the views kept the original one. After running the notebook, I checked the REST endpoints and the Drawing Info was changed. Now the labels are showing just fine on FieldMaps online and offline. Sometimes I feel a little bit dismayed by the amount of tools we need to know in order to have everything running top notch (ArcGIS Pro, Cartography, Coordinate systems, Symbology, AGOL, FieldMaps, JSON, Python, REST manipulation, Ecology, maths, logic, etc. Thanks God there's people like you, available to help other people.   ... View more

I'm really interested in learning how to clear the default labeling issue rather than having to recreate everything. Can you show me how to use the Python API to clear the labeling issue? I'll really appreciate this. Milton ... View more

Hi @RhettZufelt , Thank you for looking into this issue. It seems like a bug and you basically can't fix it without deleting and re-publishing the layers. It happened once with a domain for a field: I wasn't able to delete the domain and had to delete de FC and re-create everything again. I edited the JSON definition directly for the FC and Views with no luck. After updating the FC JSON definition, I created another view (to inherit the new definition) and the labels problem persist. I think is more than just editing the FC JSON definition. Your findings were correct and I tried that way. The solution then is to re-publish the FC, recreate the views, maps, smart forms, etc. Thank you for your time! ... View more

Yes, I sent you an invitation to join a group on AGOL. Join the group and check the content there  @RhettZufelt when you have access to the group, try the following: open the map in FieldMaps, notice the labels. Then, take the map offline and open it again. Check the labels  Milton ... View more

  Added. The map name is "ForestGeo Censo 2022 - Piloto Supervisores". Important... use the  Map Viewer Classic to open the map, please. Milton ... View more

Hi @RhettZufelt , Thanks for taking the time to see this and sorry for the late answer; I was working on other improvements on the form. Some fields are empty because those trees are not finished yet (not all fields are capturedt), hence the empty labels. I'm using a view to display these trees. The thing is: labels are showing just fine on FieldMaps when online. BUT, if you take the map offline and open the map in FieldMaps, the labels are shown incorrectly. I might share with you the Feature View and the map, so you can test it out. What is your AGOL user? Or is there another way for you to have access to the view and the map and test the label issue? Best, Milton   ... View more

Rhett, My bad at attaching images not quite the same on the question. I reattached the images at the same extent and data. The supervisors need to see more info on the label string the quickly **bleep** the census status, whereas the field crew just need 3 fields concatenated. Each field worker has the option to take the map offline on a "as needed" basis. So the map is taken offline on the spot, no pre-created offline areas. The problem is when you see the map Online, the labels are shown correctly. But once you take the map offline, the labels are changed to the original labels defined on the View. When I created the view, I defined the label as part of the view. Now it seems, when taking the map offline, is using this label as a default, ignoring the labels at the map level. Any ideas? Milton ... View more