nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Generate feature report with most recent related record/max value

JRhodes

I have a feature layer representing electric utility structures, with a related table for inspections. I'm attempting to create a feature report with a record for each structure, along with information about the most recent inspection record in the related table as defined by a date field for the inspection date

I've successfully used the Stats method with max to get the most recent inspection date, but I can't figure out how to call that variable in a where clause to define the values for the other fields coming from the related table.

Any ideas would be much appreciated.

Find more posts tagged with

Accepted answers

BarbaraWebster1

Hi @JRhodes,

You could set the result record count for the inspection repeat to one and order the fields by the inspection date. Then you should still be able to add a where filter if needed. So something like this:

${#inspection_repeat| where:"1=1"|orderByFields:"inspection_date DESC" | resultRecordCount:1}

${inspector} ${defect} ${action}

${/}

- Barbara

All comments

BarbaraWebster1

${/}

- Barbara

JRhodes

Thanks so much Barbara! I was able to get that to work, but I had to pull the leftmost three columns (parent info) out of the table; otherwise, I got "Failed to parse ${FACILITYID} since FACILITYID cannot be found in the current parsing scope.".

So, I was able to do this:

But I was unable to put it all in a line in a single table, like the example in my post. Is it possible to put the parent info and a single related record in a table row within a single table? I tried putting the open/close parent tags both inside the table and outside the table, and both gave the parsing scope error on the first attribute the template was attempting to pull from the parent table.

BarbaraWebster1

Unfortunately I believe there's a limitation that prevents parent and repeat records from being on the same line in a table when exporting multiple parent records, however you can get all the records in the same table by putting the repeat record on a line below the parent record.

Template:

Export:

JRhodes

Thanks again Barbara. I think one of these approaches will meet our needs.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.