Right now functions like Reports generally don't work with Survey123 or ExB when a hosted feature layer has a database with multiple relationship classes that interact with some of the same tables. Errors in the report widget in ExB like "multiple relationship classes is not supported".
So I can do a view and turn off the tables I'm not interested in. Then the reports can run.
But for once case, where I have three tables where there is a 1:M relationship class between Table1:Table3 and Table1:Table2 and Table2:3... the report can't handle both Table1:Table3 and Table2:Table3 if my report wants to return Table 3 records. It just focuses on the Table1:Table3 relationship, and if I nest Table3 inside of Table2 it doesn't return the records.
So if instead, in my view, I could turn off the relationship class between Table1:Table3, and then use that view for my report, I think that would allow me to specify that I want the report to only focus on the Table1:2 and Table2:Table3 relationship and it could ignore the Table1:Table3 relationship class.
Kind of like how you can turn off attachments on views!
I agree.
In the meantime, I have a complex survey with the following structure (each bullet a different table)
In the survey, I pass in a (s123 generated via the uuid() function) UUID from the parent to the children and grandchildren, and another one from the children to the grandchildren.
Then, in my report, I use those uuids to apply filters to whatever I'm doing. For example, this is my map expression that filters the map to show just the parent, the children, and the grandchildren.
${$map |
map: "341daecb71f14d598d13a2e08c532845" |
mapExtent:mapminx:mapminy:mapmaxx:mapmaxy:4326|
mapFilters: "19c58b9b708-layer-5:where=childuuid ='"+parentuuid+"'":
"'19c58b9b708-layer-4':where=grndchilduuid='"+parentuuid+"'":
"'19c58b9b707-layer-3':where=grndchilduuid='"+parentuuid+"'"
}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.