This defines an association between values of two custom fields, CustomFieldOne and CustomFieldTwo. The set of associated values, AssociationValue, is an array of strings, each of which is an ordered pair denoting value of CustomFieldOne: value of CustomFieldTwo separated by a semicolon.
MSFT_IPAM_CustomFieldAssociation methods
MSFT_IPAM_CustomFieldAssociation has 3 methods (3 Local)
'Updates the associations between values of CustomFieldOne and CustomFieldTwo. The ordered pairs in AddAssociationValue array are added to the list, while the ordered pairs in RemoveAssociationValue are removed from the list of associations for the two custom fields'
'Specifies an array of strings each of which is represented as "CustomFieldValue1:CustomFieldValue2". This defines the values of custom field one which are associated with particular values of custom field 2, separated by a colon (:).'
AssociationValue property is in 1 class (MSFT_IPAM_CustomFieldAssociation) of ROOT\Microsoft\IPAM\ms_409 and in 2 namespaces
'A user-friendly name for the object. This property allows each instance to define a user-friendly name in addition to its key properties, identity data, and description information. Note that the Name property of ManagedSystemElement is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not reasonable that the same property can convey both identity and a user-friendly name, without inconsistencies. Where Name exists and is not a Key (such as for instances of LogicalDevice), the same information can be present in both the Name and ElementName properties. Note that if there is an associated instance of CIM_EnabledLogicalElementCapabilities, restrictions on this properties may exist as defined in ElementNameMask and MaxElementNameLen properties defined in that class.'
'InstanceID is an optional property that may be used to opaquely and uniquely identify an instance of this class within the scope of the instantiating Namespace. Various subclasses of this class may override this property to make it required, or a key. Such subclasses may also modify the preferred algorithms for ensuring uniqueness that are defined below. To ensure uniqueness within the NameSpace, the value of InstanceID should be constructed using the following "preferred" algorithm: : Where and are separated by a colon (:), and where must include a copyrighted, trademarked, or otherwise unique name that is owned by the business entity that is creating or defining the InstanceID or that is a registered ID assigned to the business entity by a recognized global authority. (This requirement is similar to the _ structure of Schema class names.) In addition, to ensure uniqueness, must not contain a colon (:). When using this algorithm, the first colon to appear in InstanceID must appear between and . is chosen by the business entity and should not be reused to identify different underlying (real-world) elements. If not null and the above "preferred" algorithm is not used, the defining entity must assure that the resulting InstanceID is not reused across any InstanceIDs produced by this or other providers for the NameSpace of this instance. If not set to null for DMTF-defined instances, the "preferred" algorithm must be used with the set to CIM.'
'This defines an association between values of two custom fields, CustomFieldOne and CustomFieldTwo. The set of associated values, AssociationValue, is an array of strings, each of which is an ordered pair denoting value of CustomFieldOne: value of CustomFieldTwo separated by a semicolon.'
✗
✓
✓
✗
✓
LOCALE
'MS_409'
✗
✗
✓
✗
✓
MSFT_IPAM_CustomFieldAssociation System properties