.png)
Export-SPBusinessDataCatalogModel
Published: May 12, 2010
Exports a Business Data Connectivity Model.
Export-SPBusinessDataCatalogModel -Identity <MetadataObject> -Path <String> [-AssignmentCollection <SPAssignmentCollection>] [-Force <SwitchParameter>] [-LocalizedNamesIncluded <SwitchParameter>] [-ModelsIncluded <SwitchParameter>] [-PermissionsIncluded <SwitchParameter>] [-PropertiesIncluded <SwitchParameter>] [-ProxiesIncluded <SwitchParameter>] [-SettingId <String>]
Parameters
| Parameter | Required | Type | Description | ||
|---|---|---|---|---|---|
|
Identity |
Required |
Microsoft.SharePoint.BusinessData.Administration.MetadataObject |
Specifies the Business Data Connectivity Metadata Store metadata object from which to export the Business Data Connectivity Model.
|
||
|
Path |
Required |
System.String |
Specifies the path and name to use to create the export file. The type must be a valid path in either of the following forms: - C:\folder_name \file.bdcm - \\server_name\folder_name \file.bdcm - …\folder_name\file.bdcm |
||
|
AssignmentCollection |
Optional |
Microsoft.SharePoint.PowerShell.SPAssignmentCollection |
Manages 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.
|
||
|
Force |
Optional |
System.Management.Automation.SwitchParameter |
Overwrites the output file if the file exists. |
||
|
LocalizedNamesIncluded |
Optional |
System.Management.Automation.SwitchParameter |
Specifies that names for business data fields in multiple languages are exported. |
||
|
ModelsIncluded |
Optional |
System.Management.Automation.SwitchParameter |
Specifies that models are included in the exported Business Data Connectivity Model file. A model contains the base XML metadata for a system. |
||
|
PermissionsIncluded |
Optional |
System.Management.Automation.SwitchParameter |
Specifies that permissions from the Business Data Connectivity Model are exported. |
||
|
PropertiesIncluded |
Optional |
System.Management.Automation.SwitchParameter |
Specifies that properties from the application definition are exported. |
||
|
ProxiesIncluded |
Optional |
System.Management.Automation.SwitchParameter |
Specifies that proxies for Business Data Connectivity Service applications are exported. |
||
|
SettingId |
Optional |
System.String |
Specifies the custom environment settings model slice to export. The type must be a valid string that identifies a model slice; for example, ModelSlice1. |
Note:
Detailed Description
The Export-SPBusinessDataCatalogModel cmdlet exports a Business Data Connectivity Model. There are two types of Business Data Connectivity models: Model type (.bdcm) and Resource type (.bdcr). The Model type contains the base XML metadata, and can also include resource properties. The Resource type includes only resource properties.
Input Types
Return Types
------------------EXAMPLE------------------
$Model = Get-SPBusinessDataCatalogMetadataObject -BdcObjectType "Model" -Name "ContosoModel" -ServiceContext http://contoso
Export-SPBusinessDataCatalogModel -Identity $Model -Path "C:\folder\model.bdcm"
This example gets a Business Data Connectivity Model from the Business Data Connectivity Metadata Store and exports it to the location specified with the name model and using the bdcm file extension.
Change History
| Date | Description | Reason |
|---|---|---|
|
May 12, 2010 |
Initial publication |
|
