I'm glad to see this new functionality, however the documentation poses more questions than answers for me.
Hi,
Thanks for this one! We had some consternation when writing that part of the documentation, where we weren't completely sure how much to actually include, and I think in our process of trying to figure out what was and wasn't essential, we missed writing a few things that actually were essential (because, as developers, we already knew them). So to answer your questions directly:
Hi Claire,
Thanks for getting back to me. In response to your points:
Hopefully this makes sense? Please let me know if it doesn't!
I agree @RobBlash . The syntax for reports in not very intuitive at all. That's why I submitted this 'Idea Request' for better documentation. Please vote thumbs up to make this a reality.
Hi @ClaireProctor ,
I'd like to revive this and also point to the idea by @Jen_Zumbado-Hannibal, the documentation can still be expanded in my opinion. Here's another example where the feature report help could be improved:
Hi @ClaireProctor . I have a 5-level relational database, and am wanting to write reports with a summary section and then the details in repeats. I am completely stumped on how to summarize the area for all of one type of child feature, like repeat1_polygon. The errors are "cannot parse field, field not available in this scope", and such.
I've experimented with the Note on this page "To access questions in a nested repeat,..."which also addresses duplicate layer (or other object, seemingly) names. I've read through the report queries page you reference above, and this blog post by @IsmaelChivite .
In the summary section, I'd like to sum the area for repeat1_poolygon. An individual record an be retrieved by calling ${ Planting_Unit.Planting_Unit_polygon | getValue:"area":"square-meters":"planar"}. A non-geometric field can be accessed by "sum,pop2000,populationTotal" in the stats statement.
$<$summary>
${Planting_Unit ["Planting_Unti.Planting_Unit_polygon" or variants are declared out of scope] | stats:"sum, [[what goes here??]], PU_SumArea"}
$</>
In the summary section, if getValue syntax is inserted into the "outStatistics" portion of the stats format, it breaks the interpreter because of confusion around opening and closing of brackets, as it does with area(${Planting_Unit_polygon}).
Declaring variables, or other such Arcade syntax seems to be not interpreted. I can do this in a popup, it is frustrating to not be able to execute such a summary in a report...
How can I access the area field to sum the area of (in my example) all planting Units on a Restoration Site?
Here is another unanswered question on gis.stackexchange.com if you're looking for more. Thanks for any and all help!
Best,
David Richey