I've been struggling to find the best way to retrieve attributes from edges traversed in routes generated by a Find Routes GP service nested within another GP service. Currently, I'm returning edges in my outputs and storing the SourceOIDs as keys in a dictionary with empty values, then populating the values with the necessary attributes by referencing the OBJECTID field in a feature service of the source edges. This method works fine, but it requires that I republish a new table service each time I update the network dataset (may be unnecessary, but I'm still wrapping my head around server-side concepts so that's why I'm here). I'm updating the ND frequently enough that this has become cumbersome and I'm hoping there's a better way.
Some questions/thoughts I've had:
I've gotten to the point where I'm just spinning my wheels, so I hope that someone else has been faced with this issue and can provide some more insight.
We too have almost the exact same need...to get at what used to be called the "section" table (in "coverages", yes I am showing my age). Basically the pieces that make up a route. We plan to enter a support ticket to get help with this issue.