For example, we have a dataset collected via Survey123 that goes through a review process. Once the record has been reviewed/updated etc., a status in the parent table is updated to indicate that the feature and its associated related data are ready to be displayed publicly. Our plan was to create a hosted feature view filtered only to show records where the status is set to 'public', with the expectation that only related records linked to those filtered parent records would be visible. However, in practice, when the parent table is filtered in a hosted feature view, all related records are still returned - regardless of whether their parent has been filtered out. This results in related data being exposed to the public before it has been approved for release.
You should be able to turn off fields after it is published.
You go to the hosted service, navigate to the Visualization tab, and it opens something like a web map. Here, you can control what the public sees.
You can turn off fields in the table, and you can customize the pop-up tab.
Just make sure you save in the Upper Left Hand Corner.
This functionality is essential. Why go through the trouble of maintaining relationships if they are not honored by the system? For now we are forced to propagate AND maintain our filter fields to every child layer and table, in order to apply the same filters. This means simple workflows, like the OP describes require complex behind the scenes processing. Also, for clarification, the above post does not address the OPs issue.
This needs to happen! I'm actually shocked by the lack of attention this is getting.
I have a parent layer called Development Area, which are polygons showing a project boundary, and a child layer called Development Parcels, which is all the parcels within the project area. The Development Area has a "Status" field which users will update as the site progresses through development.
I want to create View layers based on the "Status" field that includes each Development Area per status and the related Development Parcels. Without this functionality, I have to either manually add the desired Development Parcels to the view (and monitor the statuses to maintain this list) or create a Notebook or some other form of webhook to update the View for me. This just seems way more complicated than it should be.
Here's some other posts about this same issue:
Filter Related Records by Parent in Map Viewer
How Can I Propagate Filters from a Parent Layer to a Related Table in ArcGIS Online?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.