| external help file | sharepointonline.xml |
|---|---|
| Module Name | Microsoft.Online.SharePoint.PowerShell |
| online version | https://learn.microsoft.com/powershell/module/sharepoint-online/remove-spodataconnectionsetting |
| applicable | SharePoint Server 2013, SharePoint Server 2016 |
| title | Remove-SPODataConnectionSetting |
| schema | 2.0.0 |
| author | trent-green |
| ms.author | trgreen |
| ms.reviewer |
Removes a Business Connectivity Services connection.
Remove-SPODataConnectionSetting [-Identity] <ODataConnectionSettings>
-ServiceContext <SPServiceContextPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm]
[-WhatIf] [<CommonParameters>]Remove-SPODataConnectionSetting -ServiceContext <SPServiceContextPipeBind> -Name <String>
[-AssignmentCollection <SPAssignmentCollection>] [-Confirm] [-WhatIf] [<CommonParameters>]This cmdlet contains more than one parameter set. You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. For more information about how to use parameter sets, see Cmdlet parameter sets.
Use the Remove-SPODataConnectionSetting cmdlet to remove a Business Connectivity Services connection for a particular Business Connectivity Services service application in the farm.
The metadata object associated with the Business Connectivity Services connection is also deleted.
This cmdlet applies to an on-premises environment only. You cannot use this command in the SharePoint Online Management Shell.
For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Remove-SPODataConnectionSetting -ServiceContext "http://contoso" -Name "ContosoServiceApp"This example removes the Business Connectivity Services connection named ContosoServiceApp. Metadata properties are also removed.
Remove-SPODataConnectionSetting -ServiceContext "http://contoso" -Name "ContosoServiceApp-metadata"This example removes the Business Connectivity Services connection metadata named ContosoServiceApp.
The associated Business Connectivity Services connection object is also removed.
$ConnectionVariable = Get-SPODataConnectionSettingMetadata -ServiceContext http://contoso -Name "ContosoServiceApp"
Remove-SPODataConnectionSetting -Identity $ConnectionVariable -ServiceContext "http://contoso"This example removes the Business Connectivity Services and its associated metadata connection named ContosoServiceApp.
Specifies the OData Connection Settings object.
Type: ODataConnectionSettings
Parameter Sets: Identity
Aliases:
Applicable: SharePoint Server 2013, SharePoint Server 2016
Required: True
Position: 1
Default value: None
Accept pipeline input: True (ByValue)
Accept wildcard characters: FalseSpecifies the service context which is in the form of an instance of an SPServiceContext object, an SPSiteAdministration object identifier, or a SPSite object. An example of a service context value is an identifier from the ID field, a string identifier, a URI, or a string representation of a GUID.
Type: SPServiceContextPipeBind
Parameter Sets: (All)
Aliases:
Applicable: SharePoint Server 2013, SharePoint Server 2016
Required: True
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: FalseSpecifies the name of the existing Business Connectivity Services connection.
Type: String
Parameter Sets: Name
Aliases:
Applicable: SharePoint Server 2013, SharePoint Server 2016
Required: True
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: FalseManages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used.
When the Global parameter is used, all objects are contained in the global store.
If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur.
Type: SPAssignmentCollection
Parameter Sets: (All)
Aliases:
Applicable: SharePoint Server 2013, SharePoint Server 2016
Required: False
Position: Named
Default value: None
Accept pipeline input: True (ByValue)
Accept wildcard characters: FalsePrompts you for confirmation before executing the command.
For more information, type the following command: get-help about_commonparameters
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
Applicable: SharePoint Server 2013, SharePoint Server 2016
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: FalseDisplays a message that describes the effect of the command instead of executing the command.
For more information, type the following command: get-help about_commonparameters
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
Applicable: SharePoint Server 2013, SharePoint Server 2016
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: FalseThis cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters.