Stormwater Utility Network Elevations not saving

[MarkWasdahl1]

We have just migrated an ArcHydro Stormwater File GeoDB to a File GeoDB Stormwater Utility Network v1.4. We have been unable to save Upstream and Downstream elevations for Stormwater Lines. DB is Z enabled with an NAVD 1988 in US-Survey Ft units. XY is NAD83 SP West in US-Survey Ft units. Options: Distance Units are also set to Foot_US. ArcGIS Pro version is 3.5.4. Elevation Z-values are saving to Stormwater Devices.

[MarkWasdahl1]

I need to clarify the issue arising upon hitting the "Apply" button.

Before: 

After: 

None of the three fields have a default value of zero.

[MikeMillerGIS · Accepted solution]

Then you need to disable the Set Attributes from Z attribute rule.  That is overriding your values with the Z of the line.

[MarkWasdahl1]

You have correctly identified the problem and your solution works. Thank you for your advice.

[RobertKrisher]

If you ever want to turn that attribute rule back on, while still supporting the workflow of manually entering attributes. You would want to add logic to skip over updating the fields if they're already populated.

[MarkWasdahl1]

We figured out our workflow was faulty. We thought the Z-elevations were supposed to be entered into the Attribute table. Now we enter by selecting the line and using the Edit Vertices tool that then updates the Attribute table. That allows us to bring the Z-value rule back into use. However, that has brought up a related issue. A single point can have only a single elevation while with manholes there are multiple elevations. See image from Storm Drain Profile plan sheet:

The invert elevation of the pipe from the catch basin is 746.532 meters. The invert elevation from the stormwater main upstream is 745.668 meters. And the invert elevation from the pipe out downstream is 744.518 meters. So, two out of three pipes will have an incorrect Z-value and an incorrect slope measurement. 

[RobertKrisher]

The attribute rule should only fire on create, giving you initial elevation values to drive your slope/analysis. If you are blessed with having more detailed information about each invert that you can use to fine-tune the elevation data on your pipes after that then you should absolutely capture it.

@MikeMillerGIS  thoughts?

[MarkWasdahl1]

Edit Vertices tool will set all line points at that edited point with the same Z-values. Is there a different workflow we should follow?

[RobertKrisher]

@MarkWasdahl1 after you've created the feature, you can go back into the attributes and update the elevation values of pipes that you know the elevation for. If that's the workflow you want then you can either disable the attribute to fire on update (i.e. on have it fire on create) or modify the rule so that if the elevation values of a feature are already populated that they won't be overwritten. This would allow you to manually specify an elevation when you know one without it being overwritten, and to null out the elevation and edit the feature to trigger the system to recalculate it.