Attribute Editor

The Component tab includes an Attribute Editor. For example, the following image shows an example of editable attributes for a pole:

The fields available to edit vary by component type and by customer, and depending on your configuration, some components do not have any editable fields. Thus, the fields you see on your application might differ from the image above.

IMPORTANT: In string fields, angle brackets < > are not supported and result in errors when pushing a design back to the GIS. This is because surrounding text with angle brackets could inadvertently create an HTML tag, which uses angle brackets in its formatting. The push process then attempts to render the HTML tag, resulting in error. While it is possible to disable the web content filter on the published map service (which would stop the application from trying to render the HTML tag), this is not recommended as it creates a cross site scripting vulnerability. For more information about the HTML tags, see the esri support topic Feature Services and Client Applications > Entering HTML into Text Fields. For more information about the cross site scripting vulnerability, see the esri support topic Editor Permissions for Feature Services > Advanced Editing Options.

After editing fields, click Save. This saves the changes to the fields, but it does not save the entire project. To have your changes persist beyond the current session, always save the entire project.

Cable Lengths and Strand Lengths

As described in the topic Cable Lengths, there is a relationship between the cable length and the strand length(s). In short, a cable’s length is driven by the span length (and by structures and transitions, if present), and in a multiple-span installation, the cable length is driven by the sum of those spans.

If you edit a span length using the Attribute Editor, the cable length is automatically adjusted. For example, if the installation has three spans with measurements of 100 feet, 200 feet, and 300 feet, the cable length would be 600 feet. If you later update the second span from 200 feet to 225 feet, the cable length automatically adjusts to be 625 feet.

IMPORTANT: For this functionality to work, the RFCable Length field needs to be set to editable in the configuration, but it does not need to be visible. It is recommended to be visible so that the user can confirm the length adjustment.