Filtering Related Records in a Hosted Feature View Based on Parent Table Filters

[hpnels1358]

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.

[Nick_Creedon]

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.

[jfisher]

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.