Latest Contributions by ThomasHamill

@LittleMissEsri, I think this effort and the Esri Community would benefit greatly from Esri Survey123 team support or an Esri solutions engineer to make this into an official Survey123 Template (or official app like what's been done with Field Maps, QuickCapture, etc.).   If you scan back and read through this thread from the beginning, you'll see how the Esri user community has contributed substantial efforts towards prototyping this XLSForm (most of the "heavy lifting") throughout the past six years, and since there is consistent demand and renewed interest for this product at the beginning of the vernal pool/wetland season every year, the next logical step seems to be to formalize the XLSForm prototype as a template in Survey123 and make it into an official Esri solution like what Wildnote (wildnoteapp.com) and Ecobot (ecobot.com) have done.  FWIW, these Esri competitors are still capturing a bunch of the potential customers/end-users/market share for a product like this since they've been ahead of Esri on a field mobile data collection USACE Wetland Determination Form solution for at least a few years now...   This effort to produce and refine a reliable USACE Wetland Determination Form (free of bugs/glitches) has benefitted from numerous Esri Community contributors (most recently from @ByronTsang, but also from @ClaireInbody1, @CurtKleist, and myself back in 2021, 2022, and 2023).  At one point I even reached out to the Survey123 for help to QA/QC and publish (an earlier incarnation of) the form as an official template in the Survey123 app (correspondence attached).  I'm a little surprised this hasn't received more interest from the Esri solutions teams given the continued interest for six years and longstanding gap in the Esri solutions offerings.   I think the next most logical step is to do this process again i.e., have the Survey123 Team take @ByronTsang's latest form—the one with the multi-region functionality—QA/QC and refine it, then publish it as an official S123 template (or standalone app like Field Maps or QuickCapture).   There was also a related/parallel effort to generate a working Survey123 Feature Report template to go along with the XLSForm.  More of that is detailed in separate thread here: USACE Wetland Determination Form (and Feature Report).  ... View more

Thank you @ZhifangWang, that workaround in your first bullet point with the suggestion to add HTML <p> tags around the read-only calculation appears to have worked and resolved the "Error: Initializing form... Error: not a object" pop-up with at least two other users also having tested and confirmed success. ... View more

This doesn't seem solved yet, as some users have reported being unable to make the "version=3.21" solution work. Any way the team can disable/revert the Solved! Go to Solution indicator until a consistently reliable solution has been found? ... View more

Given this issue, for active surveys would it help to change the appearance visibility to hidden (on those calculations/note questions that might be causing the error)? ... View more

Also, I'm seeing that while this is a solution for the attribute pop-up in the Map Viewer, the field order of the edit menu/dialog in the Map Viewer remains unchanged and would still unfortunately show the default attribute order of the layer's schema; I don't believe the field order in the edit menu can be customized. Hopefully Esri can ensure the field order changes are propagated down to the attribute edit menu as well. ... View more

Here's how to reset the layer pop-up to the default attribute order of its schema in the Map Viewer (i.e. reverse the automatic alphabetical sort on fields in the pop-up that seems to be the default when a new layer is added to a web map): 1) In the Map Viewer (not Map Viewer Classic), select the layer of choice from the Layers Pane table of contents (left sidebar) 2) Select the Pop-ups button from the layer settings (right sidebar) 3) Select the existing Fields list button with the fields currently in alphabetical order 4) Click the Select fields button (which will change to Deselect all) 5) Click the Deselect all button (which will change back to Select all) to turn off all fields 6) Click Select all once more—notice the order reset in the "dimmed" Fields list menu that appears behind the active Select fields menu 7) Click Done at the bottom of the Select fields menu 😎 To save these changes, don't forget to click Save from the Save and open menu (left sidebar) Related question: New Map Viewer Popup Field Ordering ... View more

@WNelson761, unfortunately, no, and I'm in a different role now, but this wouldn't be too much of a lift for Esri and the user community to develop since most of the heavy lifting is already complete with the AGCP PDF having been transposed as a Survey123 XLSForm—this AGCP version would just need to be used as a template/starting point, adapted and adjusted to include either the National Wetland Plant List species (to make more of a universal "all-region" WDDF) or just the subset of species that are specific to the Eastern Mountains and Piedmont Region (to make one for just that region).  The External Choice Lists are where I stored these species for the AGCP XLSForm. Esri should really consider taking on this as a formal product or at least as a formal template within Survey123 Connect because at least two competitors (ecobot and Wildnote) have taken the market share on the mobile data collection for these USACE Wetland Determinations. @LittleMissEsri@GinaO_Neil @Jennie @FinnSwann @Ismael @IsmaelChivite  ... View more

Thanks for the response, @RhettZufelt!  I will give this a try! ... View more

Hi @AyanPalit, thank you for your response.  This batch solution doesn't quite do what I'm looking for, I'm afraid. Ideally, Calculate Geometry would run differently for subsets of features in a single feature layer conditionally, based on an attribute that stores the local CRS (with a WKID) of the feature.  For example, the tool would calculate the area unit (acres, square meters, square km, etc.) using State Plane Arizona West for features with '6409' in their WKID attribute, calculate the area using State Plane Colorado South for features with '6432' the WKID attribute, and so on... It would be akin to having the Coordinate System parameter in the Calculate Geometry tool change or be data driven based on the WKID attribute in the feature class.  Does this make sense? ... View more

I'm seeing neither the Popup Config nor the Form Config buttons when I go into the Visualization menu of the feature layer properties.  Did this feature get rolled back? I'm trying to modify the layer configuration to set a permanent field ordering for the editing pop-up in Field Maps (and prevent the fields from resorting alphabetically when a user clicks to edit a feature).  Can I do this through the Visualization menu of the feature layer properties or does it need to be configured elsewhere?     ... View more

@icf_Eric_Link, have you had any luck completing a draft of the Feature Report template? ... View more

Has a solution been found for this scenario? ... View more