Skip to content

Commit 78a4083

Browse files
committed
Tweaks
1 parent 785931d commit 78a4083

File tree

2 files changed

+43
-43
lines changed

2 files changed

+43
-43
lines changed

powerapps-docs/developer/common-data-service/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -135,7 +135,7 @@
135135
href: data-import-entities.md
136136
- name: Data Export Service
137137
href: data-export-service.md
138-
- name: Migrate data between Common Data Service instances with OData dataflows
138+
- name: Migrate data between environments using OData dataflows
139139
href: cds-odata-dataflows-migration.md
140140
- name: Synchronize data
141141
href: data-synchronization.md

powerapps-docs/developer/common-data-service/cds-odata-dataflows-migration.md

Lines changed: 42 additions & 42 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
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
33
author: denisem-msft
44
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.
66
ms.date: 05/05/2020
77
ms.service: powerapps
88
ms.topic: "article"
@@ -11,23 +11,23 @@ search.app:
1111
- PowerApps
1212
---
1313

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
1515

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.
1717

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.
1919

2020
## Prerequisites
2121

2222
- System Administrator or System Customizer security role permission on both source and the target environments.
2323

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)
2525

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).
2727

2828
## Scenarios
2929

30-
- A one-time cross-environment or cross tenant migration is needed (for example, geo-migration)
30+
- A one-time cross-environment or cross-tenant migration is needed (for example, geo-migration)
3131

3232
- 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.
3333

@@ -42,33 +42,32 @@ In this article, we walk you through how to migrate data between Common Data Ser
4242

4343
> [!NOTE]
4444
> 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.
4647

4748
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.
4949

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.
5251

5352
## Step 2: Get the OData endpoint
5453

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.
5655

5756
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.
5857

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:
6059

61-
1. Go to [Power Apps maker portal](https://make.powerapps.com)
60+
1. Sign into [Power Apps](https://make.powerapps.com).
6261

63-
1. Make sure you are in the desired **"source"** environment.
62+
1. Select the required source environment from the top-right corner.
6463

65-
1. Select the gear icon and select **Advanced Settings**.
64+
1. Select the Settings (gear) icon in the top-right corner, and select **Advanced Settings**.
6665

67-
1. In the top ribbon expand the **Settings** menu, in the **Customizations** tab select **Customizations**.
66+
1. On the **Settings** page, select the drop-down arrow next to ****Settings**, and select **Customizations**.
6867

69-
1. Select **Developer Resources**.
68+
1. On the **Customizations** page, select **Developer Resources**.
7069

71-
1. Copy the **Service Root URL** and save it in notepad.
70+
1. Copy the **Service Root URL** to notepad.
7271

7372
> [!div class="mx-imgBorder"]
7473
> ![Copy the service root URL in the developer resources](./media/get-odata-endpoint-url.png)
@@ -77,44 +76,45 @@ From the **source** environment, get the [OData endpoint](https://docs.microsoft
7776

7877
In the **target** environment, create a new dataflow with the OData connector.
7978

80-
1. Go to [Power Apps maker portal](https://make.powerapps.com).
81-
82-
1. Make sure you are in the desired **target** environment.
79+
1. Sign into [Power Apps](https://make.powerapps.com).
8380

84-
1. In the left navigation pane, expand the **Data** menu, then select **Dataflows**.
81+
1. Select the required target environment from the top-right corner.
8582

86-
1. Select **New dataflow** to create a new dataflow. Provide a meaningful name for the dataflow.
83+
1. In the left navigation pane, expand the **Data** menu, and select **Dataflows**.
8784

88-
1. Select **Create**.
85+
1. Select **New dataflow** to create a new dataflow. Provide a meaningful name for the dataflow. Select **Create**.
8986
> [!div class="mx-imgBorder"]
9087
> ![Prompt for a new dataflow](./media/enter-name-for-new-dataflow.png)
9188
92-
1. Select the OData connector, and enter the field values:
89+
1. Select the **OData** connector.
9390

9491
> [!div class="mx-imgBorder"]
9592
> ![Select OData source](media/select-odata-data-source.png)
9693
94+
1. In the Connection Settings dialog box, type the field values:
95+
96+
> [!div class="mx-imgBorder"]
97+
> ![Confirm the field values are correct](./media/enter-odata-connector-parameters.png)
98+
99+
97100
| Field | Description |
98101
|--|--|
99102
| URL | Provide the Service Root URL in the URL field of the connection settings |
100103
| 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 | |
102105
| 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-
> ![Confirm the field values are correct](./media/enter-odata-connector-parameters.png)
106+
| Authentication kind | Organizational account. Select the Sign in button to open the login dialog that authenticates the account associated with the connection. |
107107

108108
> [!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.
110110
111111
1. Select **Next** in the bottom right.
112112

113113
## Step 4: Select and transform data with the Power Query
114114

115-
Use the Power Query, which allows to select the tables and also allows the transformation of data.
115+
Use Power Query to select the tables and also transform data as per your requirement.
116116

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.
118118

119119
> [!div class="mx-imgBorder"]
120120
> ![Power query navigator](./media/edit-queries-for-selected-entities.png)
@@ -135,11 +135,11 @@ First, select the entities that need to be transferred. You can browse all entit
135135
136136
1. Select **Next** in the bottom right.
137137

138-
## Step 5: Configure destination environment settings
138+
## Step 5: Configure target environment settings
139139

140-
This section describes how to define the target instance settings.
140+
This section describes how to define the target environment settings.
141141

142-
### Step 6: Map entities
142+
### Step 5.1: Map entities
143143

144144
For each entity chosen, select the behavior for importing that entity in these settings and select **Next**.
145145

@@ -166,11 +166,11 @@ For each entity chosen, select the behavior for importing that entity in these s
166166

167167
- 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.
168168

169-
### Step 7: Refresh settings
169+
### Step 5.2: Refresh settings
170170

171171
Select **Refresh manually** since this is a one-time migration ad select **Create**.
172172

173-
### Step 8: Run the dataflow
173+
## Step 6: Run the dataflow
174174

175175
The initial dataflow load initiates when you select the **Create** button.
176176

@@ -194,6 +194,6 @@ You can manually initiate a dataflow by selecting **(...)** in the dataflows lis
194194

195195
## Limitations
196196

197-
1. Many to many relationship data imports are not supported.
197+
- Many to many relationship data imports are not supported.
198198

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

Comments
 (0)