Latest Contributions by BrendanMadden

‎03-14-2024

In Map Viewer, the ability to enable/disable editing is available in the Properties for feature layers that are editable. It would be great to have the same option for tables as well - this is possible in Map Viewer Classic. In my particular use-case, I have two tables in a map with a related feature layer, and need one to be editable and one to be read-only. I can do this through Map Viewer Classic for now, but it seems like it should be doable in Map Viewer too.

‎12-23-2020

Hi @KevinBurke, Thanks for that suggestion! I had to tweak it slightly to get it to work, because using "IsEmpty(null)" was making all the fields show all the time. Here's what I did to make it work: $feature["FIELD_PTZ_QUANTITY"] > 0 || IsEmpty($feature["FIELD_PTZ_QUANTITY"]) I also modified my camera 2 fields a bit to be >= 2 rather than just == 2. Even though the domain range on the field is 0 - 2, if someone did enter a number greater than 2 it would have erased camera 2's field values. This way, the fields will still display in that scenario. Thanks so much for your help with this! It has gotten me to think more about how to properly build the Arcade expressions for conditional visibility, and the workaround you suggested should work just fine.

‎12-18-2020

Hi @Anonymous User, - Yes, when changing the value from 1 to 2, all six fields are visible and blank. - Correct - I would expect all six fields to be visible, but not that Camera 1's fields would be blank (assuming they had already been populated, which they generally are). - The quantity refers to the total number of PTZ cameras at a location (0, 1, or 2 max). Cameras 1 and 2 could have the same or different makes/models/types. Thanks a lot for that explanation, that makes sense. I definitely appreciate there are situations where clearing the fields when they are hidden makes sense. In my opinion though, I do think having some way to enable/disable that behavior would be really helpful. I could see situations where a user accidentally changes a field that is tied to conditional visibility and then loses data that they did not intend to. Canceling the update and restarting would be an option, but in my case this is a pretty long form and the user may end up having to spend a lot of time re-entering data unnecessarily. With the current behavior, I think my best option is to not use conditional visibility on those fields for now. It's not a deal-breaker, just a bit longer of a form. I think the behavior as it is now makes a lot of sense when creating new features. My workflow in this case is modifying existing features, and that's where I see the current behavior being potentially problematic. Thanks for working through this with me, I appreciate it!

‎12-18-2020

Hi @Anonymous User, - Camera 1 and Camera 2 have their own make/model/type fields (6 total). - That's correct, each Camera 1 field has the Camera 1 expression applied, and each Camera 2 field has the Camera 2 expression applied.

‎12-17-2020

Hi Kevin, Yes, that's exactly right. When the fields are hidden by deleting the 1 and then entering 2, the values that had previously been filled in camera 1's fields are deleted. Here are the expressions I am using on the camera 1 and 2 fields ("FIELD_PTZ_QUANTITY" is the field with 0, 1, or 2): Camera 1 make/model/type: $feature["FIELD_PTZ_QUANTITY"] > 0 Camera 2 make/model/type: $feature["FIELD_PTZ_QUANTITY"] == 2

‎12-17-2020

Hello, I'm trying to use conditional visibility in a form on a map that will be used only to modify existing features, and I've run into an issue where attributes with conditional visibility rules applied have their values deleted when visibility changes. An example of what I'm trying to do: I have a field for the number of PTZ cameras at a location, with a numeric range of 0 - 2. I then have fields for make/model/type for camera 1 and camera 2. If there are 0 PTZ cameras, I don't want any of those additional fields to show. If the number of PTZ's is 1, I want camera 1's make/model/type fields to show, but not camera 2's. Many of the features already have camera 1 data filled in for make/model/type. The problem is, if I change the value of "number of PTZ's" from 1 to 2, the conditional visibility rule briefly hides camera 1's fields, then re-shows them (along with camera 2's). That brief hiding clears the values that were entered for camera 1's make/model/type, which is not what I would expect to happen and is not great for the user. Is this expected behavior? I don't see why existing data in a field should be deleted when the field is hidden; it should just be hidden. I can get around this by just not using conditional visibility rules, but the form has a lot of fields and it's kind of an ideal use of that smart form capability. I like Field Maps so far and I'm excited about the possibilities it offers, so I'm hoping this can be changed.

Online Status	Offline
Date Last Visited	‎06-12-2024 01:51 PM

My Ideas

Latest Contributions by BrendanMadden

Enable/disable editing on tables in Map Viewer

Re: Conditional visibility erases attribute values when editing existing features

Re: Conditional visibility erases attribute values when editing existing features

Re: Conditional visibility erases attribute values when editing existing features

Re: Conditional visibility erases attribute values when editing existing features

Conditional visibility erases attribute values when editing existing features

Enable/disable editing on tables in Map Viewer

Re: Conditional visibility erases attribute values...

Re: Conditional visibility erases attribute values...