I have a feature service with three layers and a table. Layer [0] is 1:m with layer [1] and table [0]. Layer [1] is 1:m with layer [2].
The parent layer, layer [0], has a status field (ReportStatus). I have a view configured (for public consumption), with the only filter being on the parent layer (Report Status - 'Complete-Approved'). This, for a while, has successfully worked in automatically querying down related records downstream. But now it does not. We have records recently being created which are going past and appearing in the child table as 'orphans.'
I have checked and re-checked - the child records are related appropriately, their parent definitely does not meet the criteria to appear (and it doesn't, which is correct). I have removed the filter, saved the view, and then re-applied it, but the same records trickle in inappropriately. Can anyone offer guidance?
I have a workaround in mind, where I can add a field to the child tables and use a script to push the status downstream, putting filters there as well....but I'd rather the thing just work as it was designed, which it did just fine not too long ago.
Disregard: I was mistaken, no filtering was taking place originally on the child later. So now I know I need to add fields to get the status field to carry over.
So, Esri: you should allow the option to a) allow parent layers in views to filter child layers; b) allow me to delete posts?
