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/maker/data-platform/data-platform-import-export.md
+52-63Lines changed: 52 additions & 63 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: sabinn-msft
5
5
ms.service: powerapps
6
6
ms.topic: how-to
7
7
ms.component: cds
8
-
ms.date: 08/27/2020
8
+
ms.date: 02/06/2021
9
9
ms.subservice: dataverse-maker
10
10
ms.author: sabinn
11
11
search.audienceType:
@@ -14,82 +14,74 @@ search.app:
14
14
- PowerApps
15
15
- D365CE
16
16
---
17
-
# Import or export data from Microsoft Dataverse
17
+
# Import or export data from Dataverse
18
18
19
+
To get (import) data into Microsoft Dataverse tables, use an Excel worksheet file, a comma-separated values (CSV) file, or one of the many connectors available.
19
20
21
+
When you export Dataverse table data, it's exported as a CSV file.
20
22
21
-
To bulk import and export data from Microsoft Excel or CSV files, use the Get Data from Excel file and Export Data features for updated Dataverse environments.
23
+
## Import using a connector
22
24
23
-
There are two ways that you can import files into tables from Excel or CSV files.
25
+
Use a connector to import data from a selection of many different sources, such as Microsoft Excel, Azure, SQL Server database, SharePoint, Access, OData, and more.
24
26
25
-
## Option 1: Import by creating and modifying a file template
27
+
1. Sign into [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc).
28
+
1. On the left navigation pane expand **Data**, and then select **Tables**.
29
+
1. Select **Data** > **Get data** > **Get data**.
30
+
1. From the **Data sources** list, select the connector that you want to import data from.
26
31
27
-
Every table has required columns that must exist in your input file. We recommend that you create a template. First, export data from the table. Use the same file (modified with your data) to import data into the table. This template saves time and effort. You won't have to account for the required columns for each table.
32
+
For information about the connector you want to use as your data source, see [List of all Power Apps connectors](/connectors/connector-reference/connector-reference-powerapps-connectors)and [List of all connectors published by Microsoft](/connectors/connector-reference/connector-reference-microsoft-connectors).
28
33
29
-
1. Prepare the file template.
34
+
## Import from an Excel or CSV file
30
35
31
-
a. Export the table data to the CSV file. Follow the steps in **Export data to CSV**.
32
-
b. Define a plan to make sure data is unique. Use either **primary keys** or **Alternate Keys**.
33
-
c. Refer to the next section for instructions to make sure data is unique before you import it into a table.
36
+
There are two ways to import data from Excel.
37
+
-[Option 1: Import by creating and modifying a file template](#option-1-import-by-creating-and-modifying-a-file-template)
38
+
-[Option 2: Import by bringing your own source file](#option-2-import-by-bringing-your-own-source-file)
34
39
35
-
1. Modify the file with your data.
40
+
### Option 1: Import by creating and modifying a file template
36
41
37
-
- Copy data from your Excel or CSV file into the template that you just created.
42
+
Every table has required columns that must exist in your input file. We recommend that you create a template. To do this, export data from the table. Then, use the same file and modify it with your data. Finally, import the modified file back into the table. Using a template can save you time because you won't have to specify the required columns for each table.
38
43
39
-
1. Import the file.
40
-
a. On [powerapps.com](https://make.powerapps.com/), expand the **Data** section. Select **Tables** in the left navigation pane.
41
-
b. Select the table that you want to import data into.
42
-
c. Select the ellipsis or menu at the top. Select **Get Data**. Select **Get data from Excel**.
44
+
#### Prepare the file template
43
45
44
-
> [!NOTE]
45
-
> To import data into more than one table, in the top menu, select **Get Data**. Select **Get data from Excel**. Then you can choose multiple tables and select **Next**.
46
-
47
-
> [!div class="mx-imgBorder"]
48
-
> 
46
+
1.[Export the table data](#export-data).
47
+
1. Define a plan to make sure data is unique before you import it. Use either primary keys or alternate keys. More information: [Ensure uniqueness when you import data into a table from Excel or CSV](#ensure-uniqueness-when-you-import-data-into-a-table-from-excel-or-csv)
49
48
50
-
d. On the **Import data** screen, choose whether to import data from an Excel or a CSV file.
51
-
e. Select **Upload**.
52
-
f. Choose your file. Follow the prompts to upload your file.
49
+
#### Modify the file with your data
53
50
54
-
<!-- > [!div class="mx-imgBorder"]
55
-
>  -->
51
+
Copy data from your Excel or CSV file into the template that you created in the previous step.
56
52
57
-
g. After the file is uploaded and **Mapping status** is green, select **Import** in the top-right corner. Refer to the next section to navigate and fix any mapping errors.
53
+
#### Importthe file
58
54
59
-
h. After the import finishes successfully, you'll see the total number of inserts and updates.
55
+
1. On [powerapps.com](https://make.powerapps.com/), expand the **Data** section. Select **Tables** in the left navigation pane.
56
+
1. Select **Get Data** > **Get data from Excel**.
57
+
1. Select the tables where you want to import data, and then select **Next**.
58
+
1. On the **Import data** page, select **Upload**, and choose your file. Follow the prompts to upload your file.
59
+
1. After the file is uploaded and **Mapping status** indicates **Mapping was successful**, select **Import** from the top-right corner. Go to [Troubleshoot mapping errors with Excel](#troubleshoot-mapping-errors-with-excel) to navigate and fix any mapping errors.
After the import finishes successfully, you'll see the total number of inserts and updates.
60
62
61
-
> [!NOTE]
62
-
> Use the Upsert (Update or Insert) logic to either update the row, if it already exists, or to insert a new row.
63
-
64
-
## Option 2: Import by bringing your own source file
63
+
### Option 2: Import by bringing your own source file
65
64
66
-
If you're an advanced user and know the required columns for a given table for Dataverse tables, define your own Excel or CSV source file. Follow the steps in **Import the file**.
65
+
If you're an advanced user and know the required columns for a given table for Dataverse tables, define your own Excel or CSV source file. Follow the steps in [Import the file](#import-the-file).
67
66
68
-
##Navigate mapping errors
67
+
### Troubleshoot mapping errors with Excel
69
68
70
69
If you get mapping errors after you upload your file, select **Map status**. Take the following steps to inspect and rectify the column mapping errors.
71
70
72
71
1. Use the drop-down menu on the right, under **Show**, to walk through the **Unmapped columns**, **Fields with error**, or **Required Fields**.
73
72
74
73
> [!TIP]
75
-
> Depending on whether you get a Warning or an Error, inspect **Unmapped columns** or **Fields with error** through the drop-down menu in **Column Mappings**.
76
-
77
-
<!-- > [!div class="mx-imgBorder"]
78
-
> 
74
+
> - Depending on whether you get a **Warning** or an **Error**, inspect **Unmapped columns** or **Fields with error** through the drop-down menu in **Column Mappings**.
75
+
> - Use the *upsert* (**Update** or **Insert**) logic to either update the row, if it already exists, or to insert a new row.
79
76
80
-
> [!div class="mx-imgBorder"]
81
-
> 
82
-
83
-
> [!div class="mx-imgBorder"]
84
-
>  -->
77
+
1. After you resolve all the errors and warnings, select **Save Changes** in the top-right corner. You'll go back to the **Import Data** screen.
78
+
1. When the **Mapping status** column shows **Mapping was successful**, select **Import** from the top-right corner.
85
79
86
-
2. After you resolve all the errors and warnings, select **Save Changes** in the top-right corner. You'll go back to the **Import Data** screen.
87
-
3. When the **Mapping Status** column shows **Completed** in green, select **Import** in the top-right corner.
88
-
4. When you get the **Import completed successfully** message, it shows the total inserts and updates.
80
+
When the **Import completed successfully** message appears, the total inserts and updates are displayed.
89
81
90
-
## Ensure uniqueness when you import data into a table from Excel or CSV
82
+
###Ensure uniqueness when you import data into a table from Excel or CSV
91
83
92
-
Dataverse tables use a primary key to uniquely identify rows within a Dataverse table table. The primary key for a Dataverse table is a globally unique identifier (GUID). It forms the default basis for row identification. Data operations, like importing data into Dataverse tables, surface the default primary keys.
84
+
Dataverse tables use a primary key to uniquely identify rows within a Dataverse table. The primary key for a Dataverse table is a globally unique identifier (GUID). It forms the default basis for row identification. Data operations, like importing data into Dataverse tables, surface the default primary keys.
93
85
94
86
Example:
95
87
The primary key for an **Account** table is **accountid**.
@@ -100,41 +92,38 @@ The primary key for an **Account** table is **accountid**.
100
92
Sometimes, a primary key might not work when you integrate data from an external source. Use Dataverse to define alternate keys that uniquely identify a row in place of the primary key.
101
93
102
94
Example:
103
-
For an **Account** table, you might set **transactioncurrencyid** as an alternate key by using a natural key-based identification. For example, use **US Dollar** instead of the GUID value **88c6c893-5b45-e811-a953-000d3a33bcb9** shown previously. You can also choose **currency symbol** or **currency name** as keys.
95
+
For an **Account** table, you might set **transactioncurrencyid** as an alternate key by using a natural key-based identification. For example, use **US Dollar** instead of the GUID value **88c6c893-5b45-e811-a953-000d3a33bcb9** shown previously. You can also choose **currency symbol** or **currency name** as keys. More information: [Define alternate keys using Power Apps portal](define-alternate-keys-portal.md)
104
96
105
97
> [!div class="mx-imgBorder"]
106
98
> 
107
99
108
100
> [!div class="mx-imgBorder"]
109
101
> 
110
102
111
-
Users can still use primary keys as identifiers after they specify alternate keys. In the preceding sample, the first file is still valid if GUIDs are valid data.
103
+
You can still use primary keys as identifiers after you specify alternate keys. In the preceding sample, the first file is still valid if GUIDs are valid data.
112
104
113
-
## Export data to CSV
105
+
## Export data
114
106
115
-
You can do a one-time data export from a standard table or custom table. And you can export data from more than one table at a time. If you export data from more than one table, each table is exported into its own Microsoft CSV file.
107
+
Export data from one or more tables. Exported data is in comma-separated value (CSV) format. When you export data from more than one table, each table is exported into its own CSV file.
116
108
117
-
1.On [powerapps.com](https://make.powerapps.com/), expand the **Data** section. Select **Tables** on the left navigation pane.
118
-
1. Select the table that you want to export data from.
119
-
1. Select the ellipsis or menu at the top. Select**Export data**.
109
+
1.Sign into [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc), on the left navigation pane expand **Data**, and then select **Tables**.
110
+
1. Select **Data** > **Export data**.
111
+
1. Select the tables that you want to export data from, and then select**Export data**.
120
112
121
113
> [!div class="mx-imgBorder"]
122
114
> 
123
115
124
-
> [!NOTE]
125
-
> To export data from multiple tables, in the top menu, select **Export**. Select **Data**. You can choose multiple tables.
126
-
127
-
1. After the export finishes successfully, you can **Download exported data**. This download gives you a link to the downloadable CSV file.
116
+
1. After the export finishes successfully, select **Download exported data** to download the CSV file to the download folder specified in your web browser.
128
117
129
-
<!-- > [!div class="mx-imgBorder"]
130
-
> -->
118
+
> [!div class="mx-imgBorder"]
119
+
> 
131
120
132
121
## Unsupported data types
133
122
134
-
The following data types aren't currently supported.
123
+
The following data types aren't currently supported for import or export.
0 commit comments