You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: powerapps-docs/developer/common-data-service/cds-odata-dataflows-migration.md
+42-42Lines changed: 42 additions & 42 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
---
2
-
title: Migrate data between Common Data Service instances with dataflow OData connector
2
+
title: Migrate data between Common Data Service environments using the dataflows OData connector
3
3
author: denisem-msft
4
4
ms.reviewer: "nabuthuk"
5
-
description: Migrate data between Common data Service instance using Power Platform OData connector.
5
+
description: Migrate data between Common data Service environments using dataflows OData connector.
6
6
ms.date: 05/05/2020
7
7
ms.service: powerapps
8
8
ms.topic: "article"
@@ -11,23 +11,23 @@ search.app:
11
11
- PowerApps
12
12
---
13
13
14
-
# Migrate data between Common Data Service instances using the dataflows OData connector
14
+
# Migrate data between Common Data Service environments using the dataflows OData connector
15
15
16
-
Common Data Service web API works with any technology that supports OData and OAuth. There are many options available to move data in and out of Common Data Service. OData connector is one of the dataflows, which is designed to support migration and synchronization of large datasets in Common Data Service.
16
+
Common Data Service Web API works with any technology that supports OData and OAuth. There are many options available to move data in and out of Common Data Service. OData connector is one of the dataflows, which is designed to support migration and synchronization of large datasets in Common Data Service.
17
17
18
-
In this article, we walk you through how to migrate data between Common Data Service instances using the dataflows OData connector.
18
+
In this article, we walk you through how to migrate data between Common Data Service environments using the dataflows OData connector.
19
19
20
20
## Prerequisites
21
21
22
22
- System Administrator or System Customizer security role permission on both source and the target environments.
23
23
24
-
-Premium Power Apps, Power Automate, or Common Data Service license (per app or per user)
24
+
- Power Apps, Power Automate, or Common Data Service license (per app or per user)
25
25
26
-
- Two environments with Common Data Service instances provisioned.
26
+
- Two Common Data Service [environments with database](/power-platform/admin/create-environment#create-an-environment-with-a-database).
27
27
28
28
## Scenarios
29
29
30
-
- A one-time cross-environment or crosstenant migration is needed (for example, geo-migration)
30
+
- A one-time cross-environment or cross-tenant migration is needed (for example, geo-migration)
31
31
32
32
- Developer needs to update an app that is being used in production. Test data is needed in their development environment to easily build out changes.
33
33
@@ -42,33 +42,32 @@ In this article, we walk you through how to migrate data between Common Data Ser
42
42
43
43
> [!NOTE]
44
44
> Switch to **source** and **target** environments by selecting the **Environment** on the top right corner and select the appropriate environment from the list.
45
-
1. Make sure that the entities are already defined in the target environment. Ideally both environments should have the same entities defined with the same solution.
45
+
46
+
1. Ensure that the entities are already defined in the target environment. Ideally both environments should have the same entities defined with the same solution.
46
47
47
48
1. When importing relationships, multiple dataflows are required.
48
-
- One (parent/independent) to many (children/dependent) entities require separate dataflows. Configure the parent dataflow to run before any child entities, since the data in the parent needs to be loaded first to correctly map to the fields in the corresponding child entities.
49
49
50
-
> [!NOTE]
51
-
> The words to describe a Common Data Service `instance` and `environment` are used interchangeably in this article. Each environment in Microsoft Power Platform can have 0 or 1 Common Data Service instance(s). More information: [Create Common Data Service database](https://docs.microsoft.com/power-platform/admin/create-database).
50
+
One (parent/independent) to many (children/dependent) entities require separate dataflows. Configure the parent dataflow to run before any child entities, since the data in the parent needs to be loaded first to correctly map to the fields in the corresponding child entities.
52
51
53
52
## Step 2: Get the OData endpoint
54
53
55
-
Common Data Service provides an OData endpoint that does not require any additional configuration to authenticate with the dataflows connector. It is relatively easy process to connect to the source instance.
54
+
Common Data Service provides an OData endpoint that does not require any additional configuration to authenticate with the dataflows connector. It is relatively easy process to connect to the source environment.
56
55
57
56
This article will walk through how to set up a new dataflow with the OData connector. See, [Creating dataflows](https://docs.microsoft.com/powerapps/maker/common-data-service/create-and-use-dataflows) article for connecting to all data sources supported by dataflows.
58
57
59
-
From the **source** environment, get the [OData endpoint](https://docs.microsoft.com/powerapps/developer/common-data-service/view-download-developer-resources) (aka Service Root URL) for that instance:
58
+
From the **source** environment, get the [OData endpoint](https://docs.microsoft.com/powerapps/developer/common-data-service/view-download-developer-resources) (aka Service Root URL) for that environment:
1. In the Connection Settings dialog box, type the field values:
95
+
96
+
> [!div class="mx-imgBorder"]
97
+
> 
98
+
99
+
97
100
| Field | Description |
98
101
|--|--|
99
102
| URL | Provide the Service Root URL in the URL field of the connection settings |
100
103
| Connection | Create new connection. This will be automatically chosen if you have not made an OData connection in dataflows before. |
101
-
| Connection name | Optionally rename the connection name, but a value is automatically populated ||
104
+
| Connection name | Optionally, rename the connection name, but a value is automatically populated ||
102
105
| On-premise data gateway | None. An on-premises data gateway is not needed for connections to this cloud service. |
103
-
| Authentication kind | Organizational account. Select the Sign in button to open the login dialog that authenticates the account associated with the connection. |
104
-
105
-
> [!div class="mx-imgBorder"]
106
-
> 
106
+
| Authentication kind | Organizational account. Select the Sign in button to open the login dialog that authenticates the account associated with the connection. |
107
107
108
108
> [!IMPORTANT]
109
-
> Disable pop-up and cookies blocker in your browser in order to configure the AAD authentication. This is orthogonal to the fact that you are using the Common Data Service OData endpoint or any other OAuth based authentication data source.
109
+
> Disable pop-up and cookies blocker in your browser in order to configure the Azure AD authentication. This is orthogonal to the fact that you are using the Common Data Service OData endpoint or any other OAuth based authentication data source.
110
110
111
111
1. Select **Next** in the bottom right.
112
112
113
113
## Step 4: Select and transform data with the Power Query
114
114
115
-
Use the Power Query, which allows to select the tables and also allows the transformation of data.
115
+
Use Power Queryto select the tables and also transform data as per your requirement.
116
116
117
-
First, select the entities that need to be transferred. You can browse all entities in the source instance and preview some of the data in each entity.
117
+
First, select the entities that need to be transferred. You can browse all entities in the source environment and preview some of the data in each entity.
This section describes how to define the target instance settings.
140
+
This section describes how to define the target environment settings.
141
141
142
-
### Step 6: Map entities
142
+
### Step 5.1: Map entities
143
143
144
144
For each entity chosen, select the behavior for importing that entity in these settings and select **Next**.
145
145
@@ -166,11 +166,11 @@ For each entity chosen, select the behavior for importing that entity in these s
166
166
167
167
- There is an option to **Do not load**, but do not include entities in the dataflow that are not being loaded. You can select **Back** from this menu to return to the Power Query menu and remove the entities that are not needed.
168
168
169
-
### Step 7: Refresh settings
169
+
### Step 5.2: Refresh settings
170
170
171
171
Select **Refresh manually** since this is a one-time migration ad select **Create**.
172
172
173
-
###Step 8: Run the dataflow
173
+
## Step 6: Run the dataflow
174
174
175
175
The initial dataflow load initiates when you select the **Create** button.
176
176
@@ -194,6 +194,6 @@ You can manually initiate a dataflow by selecting **(...)** in the dataflows lis
194
194
195
195
## Limitations
196
196
197
-
1. Many to many relationship data imports are not supported.
197
+
- Many to many relationship data imports are not supported.
198
198
199
-
1. Parent dataflows must be manually configured to run before child dataflows.
199
+
- Parent dataflows must be manually configured to run before child dataflows.
0 commit comments