RFAmplifierData

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	No	Yes	Not Required	None
Amperage	No	Yes	No	Not Required	None
AmpNumber	No	Yes	Yes	Not Required	None		Can use FriendlyName="Amp Number"
AmpType	Yes	Yes	No	CodedValueDomain	None	AmplifierType	Can use FriendlyName="Amp Type"
CascadeNumber	No	Yes	No	Not Required	None		Can use FriendlyName="Cascade Number"
CatalogId	No	Yes	Yes	Not Required	MaxLength		Can use FriendlyName="Catalog Id"
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.
DistanceToLastActive	No	Yes	No	Not Required	None		Can use FriendlyName="Distance To Last Active (ft)"
FedFromComponentId	No	Yes	Yes	Not Required	None
Flipped	No	Yes	Yes	Not Required	None
ForwardInputHighLevel	No	Yes	No	Not Required	None		Can use FriendlyName="Fwd Input High (dBmV)"
ForwardInputLowLevel	No	Yes	No	Not Required	None		Can use FriendlyName="Fwd Input Low (dBmV)"
ForwardOutputHighLevel	No	Yes	No	Not Required	None		Can use FriendlyName="Fwd Output High (dBmV)"
ForwardOutputLowLevel	No	Yes	No	Not Required	None		Can use FriendlyName="Fwd Output Low (dBmV)"
GainControlMode	No	Yes	No	Not Required	None		Can use FriendlyName="Gain Control Mode"
HotDotPortNumber	No	Yes	Yes	Not Required	None		Can use FriendlyName="Hot Dot Port Number"
InternalCouplerCompanyID1	No	Yes	Yes	Not Required	MaxLength
InternalCouplerCompanyID2	No	Yes	Yes	Not Required	MaxLength
InternalCouplerCompanyID3	No	Yes	Yes	Not Required	MaxLength
InternalCouplerValue1	No	Yes	Yes	Not Required	MaxLength
InternalCouplerValue2	No	Yes	Yes	Not Required	MaxLength
InternalCouplerValue3	No	Yes	Yes	Not Required	MaxLength
IsInMdu	No	Yes	No	Not Required	None
IsLocked	No	Yes	Yes	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.
Manufacturer	No	No	No	Not Required	MaxLength
ModelNumber	No	No	Yes	Not Required	MaxLength
Name	No	No	Yes	Not Required	MaxLength		This field does not appear in the Attribute Editor, but is editable at the top of the device pane.
NetworkPath	No	Yes	No	Not Required	MaxLength		Can use FriendlyName="Network Path"
NodeId	No	Yes	No	Not Required	None		Can use FriendlyName="Node Id"
NodeLeg	No	Yes	No	Not Required	MaxLength		Can use FriendlyName="Node Leg"
NodeName	No	Yes	No	Not Required	MaxLength		Can use FriendlyName="Node Name"
OperationalForwardGain	No	No	No	Not Required	None
OperationalReturnGain	No	No	No	Not Required	None
PoweringFedFromComponentId	No	No	Yes	Not Required	None
PowerMode	No	Yes	No	Not Required	MaxLength		Can use FriendlyName="Power Mode"
PowerSupplyName	No	Yes	No	Not Required	MaxLength		Can use FriendlyName="Power Supply Name"
ReverseInputHighLevel	No	Yes	No	Not Required	None		Can use FriendlyName="Reverse Output High (dBmV)"
ReverseInputLowLevel	No	Yes	No	Not Required	None		Can use FriendlyName="Reverse Input High (dBmV)"
ReverseOutputHighLevel	No	Yes	No	Not Required	None		Can use FriendlyName="Reverse Output High (dBmV)"
ReverseOutputLowLevel	No	Yes	No	Not Required	None		Can use FriendlyName="Reverse Output Low (dBmV)"
SpecSymbology	No	Yes	No	Not Required	None
SymbolRotation	No	Yes	Yes	Not Required	None		Can use FriendlyName="Symbol Rotation"
UGStructureId	No	No	Yes	Not Required	None
Voltage	No	Yes	No	Not Required	None
Workflow_Status	Yes	Yes	Yes	CodedValueDomain	None	WorkflowState	Can use FriendlyName="Workflow Status"