[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]

Represents an overrideable configuration parameter in a monitor or module type definition.

Schema Hierarchy

        OverrideableParameters (DataSourceModuleType)


<OverrideableParameter ID=”ParameterID” ParameterType=”dataType” Selector=”$Config/ParameterID”/>

Attributes and Elements

The following sections describe attributes, child elements, and the parent element of the OverrideableParameter element.


Attribute Description


Required attribute. Represents the ID of the overrideable parameter. Must be unique within the module or monitor type definition.


Optional attribute. Represents commentary by the management pack author.


Required attribute. Represents the simple data type of the parameter to be overridden. Only simple types can be overridden.


Required attribute. Represents the XPath location within the schema defined in the Configuration (DataSourceModuleType) element of the parameter to be overridden.

ParameterType Attribute Values

Value Description


The overrideable parameter is of an integer type.


The overrideable parameter is of a decimal type.


The overrideable parameter is of a double type.


The overrideable parameter is of a string type.


The overrideable parameter is of a datetime type.


The overrideable parameter is of a GUID type.


The overrideable parameter is of a Boolean type.

Child Elements


Parent Elements

Element Description

OverrideableParameters (DataSourceModuleType)

Contains any overrideable configuration parameters a monitor or module type definition.


Because parameter overrides are displayed in the console so that users can implement the overrides, it is advised to supply a display string for each override. For more information, see DisplayStrings.


The following sample shows how to define an OverrideableParameter element within a DataSourceModuleType module definition.

A management pack that implements this data source module type may hard code the Frequency parameter in one of its workflows. Because Frequency is an OverrideableParameter element, the customer can override whatever value that is set by the management pack author. If you want to implement a module type but do not want to offer its defined OverrideableParameter elements to the customer, you must write your own module type without the override definition.

  Copy Code
<DataSourceModuleType ID="Microsoft.Windows.RegistryProviderSingle" Accessibility="Public">
	<xsd:element name="ComputerName" type="xsd:string" />
	<xsd:element name="AttributeName" type="xsd:ID" />
	<xsd:element name="Path" type="xsd:string" />
	<xsd:element name="PathType" type="xsd:integer" />
	<xsd:element name="AttributeType" type="xsd:integer" />
	<xsd:element name="Frequency" type="xsd:unsignedInt" />
	<xsd:element name="RegistryView" minOccurs="0" maxOccurs="1" type="RegistryViewType" />
	<OverrideableParameter ID="Frequency" Selector="$Config/Frequency$" ParameterType="int" />
		<DataSource TypeID="System!System.Scheduler" ID="Scheduler">
			<Interval Unit="Seconds">$Config/Frequency$</Interval>
			<ExcludeDates />
		<ProbeAction TypeID="Microsoft.Windows.RegistryProbe" ID="Probe">
		<Node ID="Probe">
		<Node ID="Scheduler" />

See Also