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.