Remove-IpamCustomFieldAssociation
Remove-IpamCustomFieldAssociation
Removes an association between two custom fields that are defined in IPAM.
Syntax
Parameter Set: Remove2
Remove-IpamCustomFieldAssociation [-CustomFieldOne] <String> [-CustomFieldTwo] <String> [-AsJob] [-CimSession <CimSession[]> ] [-Force] [-PassThru] [-ThrottleLimit <Int32> ] [-Confirm] [-WhatIf] [ <CommonParameters>]
Detailed Description
The Remove-IpamCustomFieldAssociation cmdlet removes an association between two custom fields that are defined in IP Address Management (IPAM). Specify the custom fields by using the CustomFieldOne and CustomFieldTwo parameters. The cmdlet does not find an association that contains both specified fields, it informs you of the error. The cmdlet does not delete the custom fields themselves.
Use the Get-IpamCustomFieldAssociation cmdlet to see existing associations. Use the Add-IpamCustomFieldAssociation cmdlet to create associations. Use the Set-IpamCustomFieldAssociation cmdlet to modify associations.
Parameters
-AsJob
Aliases |
none |
Required? |
false |
Position? |
named |
Default Value |
none |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
-CimSession<CimSession[]>
Runs the cmdlet in a remote session or on a remote computer. Enter a computer name or a session object, such as the output of a New-CimSession or Get-CimSession cmdlet. The default is the current session on the local computer.
Aliases |
Session |
Required? |
false |
Position? |
named |
Default Value |
none |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
-CustomFieldOne<String>
Specifies a custom field. The cmdlet removes an association between this field and the field specified by the CustomFieldTwo parameter.
Aliases |
none |
Required? |
true |
Position? |
2 |
Default Value |
none |
Accept Pipeline Input? |
True (ByPropertyName) |
Accept Wildcard Characters? |
false |
-CustomFieldTwo<String>
Specifies a custom field. The cmdlet removes an association between this field and the field specified by the CustomFieldOne parameter.
Aliases |
none |
Required? |
true |
Position? |
3 |
Default Value |
none |
Accept Pipeline Input? |
True (ByPropertyName) |
Accept Wildcard Characters? |
false |
-Force
Forces the command to run without asking for user confirmation.
Aliases |
none |
Required? |
false |
Position? |
named |
Default Value |
none |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
-PassThru
Returns an object representing the item with which you are working. By default, this cmdlet does not generate any output.
Aliases |
none |
Required? |
false |
Position? |
named |
Default Value |
none |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
-ThrottleLimit<Int32>
Specifies the maximum number of concurrent operations that can be established to run the cmdlet. If this parameter is omitted or a value of 0 is entered, then Windows PowerShell® calculates an optimum throttle limit for the cmdlet based on the number of CIM cmdlets that are running on the computer. The throttle limit applies only to the current cmdlet, not to the session or to the computer.
Aliases |
none |
Required? |
false |
Position? |
named |
Default Value |
none |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
-Confirm
Prompts you for confirmation before running the cmdlet.
Required? |
false |
Position? |
named |
Default Value |
false |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
-WhatIf
Shows what would happen if the cmdlet runs. The cmdlet is not run.
Required? |
false |
Position? |
named |
Default Value |
false |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
<CommonParameters>
This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer, and -OutVariable. For more information, see about_CommonParameters (https://go.microsoft.com/fwlink/p/?LinkID=113216).
Inputs
The input type is the type of the objects that you can pipe to the cmdlet.
Outputs
The output type is the type of the objects that the cmdlet emits.
Examples
Example 1: Remove association between fields
This example removes an association between fields, and then verifies the removal.
The first command removes the association between the two custom fields, VmmLogicalNetwork and NetworkSite. The cmdlet prompts you before it removes associations.
PS C:\> Remove-IpamCustomFieldAssociation -CustomFieldOne "VmmLogicalNetwork" -CustomFieldTwo "NetworkSite"
The second command uses the Get-IpamCustomFieldAssociation to get all associations. The associations that the first command removed do not appear.
PS C:\> Get-IpamCustomFieldAssociation
Example 2: Remove all associations for a field
This example removes all associations for a specified field, and then verifies the removal.
The first command uses the Get-IpamCustomFieldAssociation cmdlet to get all the associations specified by the ManagedByService custom field, and then passes them to the current cmdlet by using the pipeline operator. The cmdlet prompts you for confirmation, and then removes all the associations.
PS C:\> Get-IpamCustomFieldAssociation -CustomFieldOne "ManagedByService" | Remove-IpamCustomFieldAssociation
The second command uses the Get-IpamCustomFieldAssociation to get all associations. The associations that the first command removed do not appear.
PS C:\> Get-IpamCustomFieldAssociation
Related topics
Add-IpamCustomFieldAssociation