Latest Contributions by JanetSilb_Spike

I would also like to know if this is possible. Thanks @RandyMcGregor3 for posting the question.  ... View more

That's a a good idea, thanks @rzufelt . However we are already into the 3rd year & I'm not sure I want to change the structure for the sets of fields, but good to think about for future applications. ... View more

Thanks @AustinCanty1 . It is because of the different api versions between Map Viewer & WAB. However, we put a significant amount of work into configuring the current WAB last year & it's being used. I had found a solution to making the image attachments visible in the WAB pop-ups, I think by adding an expression. But I can't find that solution now & need to use it again. Any help?   ... View more

An additional note: I thought about adding a "Description" field but that would only allow for 1 description for each record/feature. However each feature has 12 photos so the descriptors have to be tied to the attachments, rather than to the feature.        ... View more

Hi @JoshConrad1, I worked with Tech Support to arrive at this solution: Adjust our Arcade Expression to not hide Groups with values: Each season, add the following line to the Arcade Expression for Conditional Visibility for the previous seasons' Groups (replacing "Season_Completed_FieldName" with the field name for the previous seasons' Completed field) ....|| $feature["Season_Completed_FieldName"] == "Yes" || $feature["Season_Completed_FieldName"] == "No" Example for Spring 22, Fall 22, Winter 22: $feature["Completed"] == "Yes" || $feature["Completed"] == "No" ||$feature["Completed_Aug22"] == "Yes" ||$feature["Completed_Aug22"] == "No"| |$feature["Completed_Nov22"] == "Yes" ||$feature["Completed_Nov22"] == "No" I also put in this enhancement request, which I guess is underway for future release of Field Maps: Enhancement request: ENH-000145702: Conditional visibility in the Field Maps erases attribute values when editing existing features. Please allow user to choose what attributes to keep instead of erasing all the related attributes. ... View more

Thanks for this solution. Can you tell me where you changed the organizational URL? Was it in a settings menu within Dashboards? ... View more

Actually @Anonymous User , it is not straightforward because not all data cleared, nor does it clear if I edit the fields now. Would you be willing to do a brief screen share call with me?  --Janet ... View more

Hello @JoshConrad1 & @Anonymous User .  I think I have run into a similar challenge. My client is using Field Maps to monitor the condition of trees on a restored site every spring & fall for 5 years through a contract with the city. So far they have used the form I configured this past spring (May) and fall (Aug) 2022. However we just noticed that the Spring22 Condition field is now empty and the Completed field set back to "No" for those features monitored in Aug.  I did set up the form to have fields grouped by season/year (e.g. Spring 2022), and then set conditional visibility for the group so that if the autopopulated Monitoring Date falls outside of the designated season date range, then that group is not visible.   Fortunately I have the Spring 22 collected data backed up so I can repopulate the fields. Can you please advise me on how to create the more complex Arcade expression to preserve each season's data going forward? ... View more

I learned at the UC Field Maps technical session that this functionality is not yet available.  ... View more