RFNodeCoaxPortData
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 |
This is a unique identifier for the port data in the following format: {NodeId}:{PortNumber} For example, if the NodeId is {0BFD-4A49-9A2B} and the PortNumber is 4, the NetworkId would be: 0bfd-4a49-9a2b:4 The NodeId does not have curly braces and is not capitalized like the normal Esri GUID format. |
|
|
ConnectedItemId |
No |
Yes |
Yes |
Not Required |
None |
This is the NetworkId of the component that is connected to the node housing at a given port number. If a device such as a splitter, tap, etc. is connected directly to the output port, the ConnectedItemId refers to the housing to housing that connects the node to the other device, rather than the other device itself. If a cable is connected to the port, the ConnectedItemId refers to the cable’s NetworkId. An empty GUID in this field means that no components are connected on the given port number. |
|
|
CreationUser |
No |
Yes |
Yes |
Not Required |
MaxLength |
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. |
|
|
HomesPassed |
No |
Yes |
No |
Not Required |
None |
This is the total number of homes (residential and commercial) served by the leg beginning at a given port number. |
|
|
IsPowerOnly |
No |
Yes |
No |
Not Required |
None |
||
|
LastUser |
No |
Yes |
Yes |
Not Required |
MaxLength |
Importing this value is optional. Regardless of whether it is imported or not, DHFC sets the value when data are pushed to GIS. |
|
|
NodeId |
No |
Yes |
Yes |
Not Required |
None |
||
|
PortName |
No |
Yes |
Yes |
Not Required |
MaxLength |
This is the leg label for a given port location on the node housing. See the topic RFNode and the PortConfiguration Field for more information. This field can use FriendlyName="Port Name" |
|
|
PortNumber |
No |
Yes |
Yes |
Not Required |
None |
This is the output port index for the connection on the node housing. See the topic RFNode and the PortConfiguration Field for more information. This field can use FriendlyName="Port Number" |
|
|
Workflow_Status |
No |
Yes |
Yes |
CodedValueDomain |
None |
WorkflowState |
Can use FriendlyName="Workflow Status" |