RFNodeData
The following table describes your attribute editing configuration options for each field, separated into these categories:
-
Can Editable setting be changed?
-
This column answers the question, “Am I allowed to add or remove this field from the Attribute Editor?” The default for the Editable tag is Editable=“false”. If the table below states “Yes,” then you are allowed to add the tag Editable=“true” to that field, if desired. It then appears in the Attribute Editor in the application. Editable fields are inherently Viewable, even if the Viewable setting is not included in the Schema.xml.
-
-
Can Viewable setting be changed?
-
This column answers the question, “Am I allowed to add or remove this field from being viewed in the Attribute Editor?” To do so, add the tag Viewable=“true”. Viewable fields do not have to be Editable. In other words, you can provide them to your users in a read-only mode. A “No” in the table below means the value from that field is presented to the user in another, more meaningful way than the raw data contained in the field, and you cannot change its viewable setting.
-
-
Are attributes imported from GIS?
-
A “Yes” in the table below means the data originate from the GIS. These fields should have a tag of Import=“true”, and that tag should not be changed in the Schema.xml.
-
A “No” in the table below means the field is populated while working in the application.
-
-
Data Type
-
Because the default data type is “string”, notice that most of the entries in the table below state “Not Required.” This is because if you do not add a DataType tag, it uses the default string type.
-
-
Validation Options
-
Validation Options only apply to Editable fields. Because most of the fields are managed by the application, notice that most options in the table below state “None.”
-
-
Coded Domain Name
-
This lists the domain provided in the default Schema.xml.
-
-
Notes
-
This column includes other information for that field.
-
|
Field Name (CoaxName) |
Can Editable setting be changed? |
Can Viewable setting be changed? |
Are attributes imported from GIS? |
Data Type |
Validation Options |
Coded Domain Name |
Notes |
|---|---|---|---|---|---|---|---|
|
EsriId |
No |
Yes |
Yes |
Not Required |
None |
||
|
NetworkId |
No |
Yes |
Yes |
Not Required |
None |
||
|
AerialStructureId |
No |
Yes |
Yes |
Not Required |
None |
||
|
Amperage |
No |
No |
No |
Not Required |
None |
||
|
CatalogId |
No |
Yes |
Yes |
Not Required |
None |
||
|
CoaxPortCount |
No |
Yes |
No |
Not Required |
None |
||
|
CreationUser |
No |
Yes |
Yes |
Not Required |
None |
Importing this value is optional. Regardless of whether it is imported or not, DHFC sets the value when data are pushed to GIS. |
|
|
DateCreated |
No |
Yes |
Yes |
Not Required |
None |
Importing this value is optional. Regardless of whether it is imported or not, DHFC sets the value when data are pushed to GIS. |
|
|
DateModified |
No |
Yes |
Yes |
Not Required |
None |
Importing this value is optional. Regardless of whether it is imported or not, DHFC sets the value when data are pushed to GIS. |
|
|
DesignFrequency |
No |
Yes |
No |
Not Required |
None |
This value comes from the active project file. |
|
|
FedFromComponentId |
No |
Yes |
Yes |
Not Required |
None |
||
|
FiberPortCount |
No |
Yes |
No |
Not Required |
None |
||
|
Flipped |
No |
Yes |
No |
Not Required |
None |
||
|
ForwardOutputHighSignalLevel |
No |
No |
No |
Not Required |
None |
||
|
ForwardOutputLowSignalLevel |
No |
No |
No |
Not Required |
None |
||
|
InternalPowerMapping |
No |
No |
Yes |
Not Required |
None |
||
|
InventoryNum |
No |
Yes |
No |
Not Required |
None |
||
|
IsInMdu |
No |
Yes |
Yes |
Not Required |
None |
||
|
IsLocked |
No |
Yes |
Yes |
Not Required |
None |
The lock button on the device pane toggles the state of this property. |
|
|
LastUser |
No |
Yes |
Yes |
Not Required |
None |
Importing this value is optional. Regardless of whether it is imported or not, DHFC sets the value when data are pushed to GIS. |
|
|
Manufacturer |
No |
Yes |
No |
Not Required |
None |
||
|
Market |
No |
Yes |
No |
Not Required |
None |
This value comes from the active project file. |
|
|
ModelNumber |
No |
Yes |
No |
Not Required |
None |
||
|
Name |
Yes |
Yes |
Yes |
Not Required |
MaxLength |
This field does not appear in the Attribute Editor, but is editable at the top of the device pane. |
|
|
PortConfiguration |
No |
No |
Yes |
Not Required |
None |
See the topic RFNode and the PortConfiguration Field for more information. |
|
|
PoweringFedFromComponentId |
No |
Yes |
Yes |
Not Required |
None |
||
|
PowerSupplyId |
No |
Yes |
No |
Not Required |
None |
||
|
ProjectFileCatalogId |
No |
Yes |
Yes |
Not Required |
None |
IMPORTANT: If the application encounters a null ProjectFileCatalogId
(for example, if opening an older design prior to upgrading to 11.4
and beyond), the application falls back to locating the project file
by name. This means, if both the ProjectFileCatalogId is null and the project file name has been changed, the older design cannot
be loaded. Thus, during your transition to version 11.4 and beyond,
do not change any project file names until after older designs are
pushed or otherwise cleared from the system.
|
|
|
ProjectFileName |
No |
Yes |
Yes |
Not Required |
None |
||
|
ReturnInputHighSignalLevel |
No |
No |
No |
Not Required |
None |
||
|
ReturnInputLowSignalLevel |
No |
No |
No |
Not Required |
None |
||
|
SegmentationConfiguration |
No |
No |
Yes |
Not Required |
None |
This field is required if your company uses segmentable nodes. Otherwise, it is optional. When a node is segmented, the SegmentationConfiguration field contains information about the nodes and the legs they serve. The length of this field should be the Node Name field length + 50. For example, if your Node Name field length is limited to 45, then this field’s length should be 95 (45 + 50). When a node is not segmented, this field is null. |
|
|
SegmentationMode |
No |
No |
Yes |
Not Required |
None |
NodeSegmentation |
This field is required if your company uses segmentable nodes. Otherwise, it is optional. |
|
SpecSymbology |
No |
Yes |
No |
Not Required |
None |
||
|
SymbolRotation |
Yes |
Yes |
Yes |
double |
Range |
||
|
TotalHomesPassed |
No |
No |
No |
Not Required |
None |
||
|
TotalHomesPassedLegA |
No |
No |
No |
Not Required |
None |
||
|
TotalHomesPassedLegB |
No |
No |
No |
Not Required |
None |
||
|
TotalHomesPassedLegC |
No |
No |
No |
Not Required |
None |
||
|
TotalHomesPassedLegD |
No |
No |
No |
Not Required |
None |
||
|
UGStructureId |
No |
Yes |
Yes |
Not Required |
None |
||
|
Voltage |
No |
No |
No |
Not Required |
None |
||
|
Workflow_Status |
Yes |
Yes |
Yes |
Not Required |
None |
WorkflowState |
Can use FriendlyName="Workflow Status" |