Add the ability to filter features in Hosted Feature Layer Views by logged in user.
This is similar to editor settings restricting users to see features they created. Except the editor tracking fields are system-managed and you would need to log in as the end user to 'create' the features they can see.
It would be great if we can create a field in a Hosted Feature Layer, assign username values to it and then create a Hosted Feature Layer View with a filter on this field by the logged in user.
This would allow us to greatly control who can see what work is assigned to them in a variety of apps.
In the Settings of the hosted view layer, you can change "What features can editors see?" to "Editors can only see their own features".
Note that confusingly this is in the Editing menu, so you will need to Enable editing, update the settings mentioned above, Save, and then disable editing again if you don't want them to have editing permissions.
Yes I agree that is a problem. I raised that issue on this forum some time ago but so far no response from ESRI: https://community.esri.com/t5/arcgis-online-questions/manually-assign-features-to-a-user-via-arcgis/...
Thanks. My question was more general than just Survey123, as a method for tagging records by user wouldn't necessarily require Survey123 to be involved.
Hello,
I have been waiting for a solution to this as well. We have records we would like to "assign" to users. Too many custom field map forms and webmap expressions to create a custom view layer for each user.
Hi @BriannaEttley, @ChrisCatania
A couple of examples for the community team to pass through to the user feedback and product teams.
This idea is two years old
They announced this functionality (to an extent) at the UC with the latest release of ArcGIS Online. Same with the below, there's active development in this space for map Tasks
I appreciate the ideas didnt garner a lot of attention. Id argue that this is something people want but it's hard to promote ideas in the community forum. Two years though.
Do ideas ever get reviewed? Why isn't this flagged as under consideration or in the product plan? How can we promote community support for ideas or recognise good ones? I'd say this is a legitimately good idea if it's ending up in the product.
Cheers, Chris
I'm just seeing your message - apologies on the delay. Ideas do get reviewed but I'm unsure on the process for following up with Ideas submitted. I'm assuming each case is different but I'll bring your feedback and thoughts back to the team specifically on this example. Tagging @DaraBurlo for visibility.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.