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/user/export-excel-dynamic-worksheet.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -48,12 +48,12 @@ You can’t export data to a dynamic worksheet in Excel for all record types. If
48
48
49
49
6. If you see the security warning **External Data Connections have been disabled**, select **Enable Content**.
50
50
51
-
7. To refresh data in the file, on the **Data** tab, select **Refresh from Power Apps**.
51
+
7. To refresh data in the file, on the **Data** tab, select **Refresh All**.
52
52
53
53
> [!NOTE]
54
-
> If you have a phone number that starts with **+** or **–** (for example +1-123-456-7890), when you refresh the dynamic worksheet, the phone number field will not display the number correctly.
55
-
>
54
+
> - If you have a phone number that starts with **+** or **–** (for example +1-123-456-7890), when you refresh the dynamic worksheet, the phone number field will not display the number correctly.
56
55
> To avoid the issue, use a space or parentheses **()**, like this: +1 123-456-7890 or +1 (123)-456-7890.
56
+
>- If you have any issues with dynamic worksheet, see [Troubleshoot export to Excel](ts-export-to-excel.md).
Copy file name to clipboardExpand all lines: powerapps-docs/user/import-data.md
+79-5Lines changed: 79 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -6,9 +6,8 @@ manager: kvivek
6
6
ms.service: powerapps
7
7
ms.component: pa-user
8
8
ms.topic: conceptual
9
-
ms.date: 11/16/2018
9
+
ms.date: 08/11/2020
10
10
ms.author: mduelae
11
-
ms.custom: ""
12
11
ms.reviewer: ""
13
12
ms.assetid:
14
13
search.audienceType:
@@ -25,6 +24,7 @@ Whether your data is stored in a spreadsheet, on your phone, or in an email prog
25
24
First, export your data into an Excel file. These file formats are supported:
26
25
- Excel workbook (.xlsx)
27
26
- Comma-separated values (.csv)
27
+
- XML Spreadsheet 2003 (.xml)
28
28
29
29
The maximum file size allowed for .zip files is 32 MB. For the other file formats, the maximum file size allowed is 8 MB.
30
30
@@ -69,10 +69,10 @@ Use a USB cable or an app to export your data such as contacts from your phone t
69
69
To find specific steps to export contacts for your brand of phone, search for “export contacts from my phone” in your favorite search engine (like Bing).
70
70
71
71
To find an app, search your phone’s online store.
72
-
72
+
73
73
## Step 2: Import the file
74
74
75
-
1. On the command bar, select **Import from Excel** or**Import from CSV**.
75
+
1. On the command bar, select **Import from Excel**, **[Import from CSV](#import-from-xml-or-csv-file)**, or **[Import from XML](#import-from-xml-or-csv-file)**.
76
76
77
77
> [!div class="mx-imgBorder"]
78
78
> 
@@ -83,7 +83,78 @@ To find an app, search your phone’s online store.
83
83
> You can import only one file at a time. To bring in more files, run the wizard again later.
84
84
85
85
3. Review the file name and verify that the field and data delimiters are correct using the **Review Mapping** option. If everything looks good, select **Finish Import**.
86
-
86
+
87
+
### Import from XML or CSV file
88
+
89
+
>[!NOTE]
90
+
>In the below process, we are importing an XML file. Similarly, you can follow the process to import CSV file.
91
+
92
+
1. On the **Import from XML** pane, select **Choose file** and browse to the folder where you saved the file that contains the export of your data. Select the file and then select **Open**.
93
+
94
+
> [!div class="mx-imgBorder"]
95
+
> 
96
+
97
+
2. Select **Next**.
98
+
99
+
3. (Optional) If you have to update the existing records in Dynamics 365 through import XML file, use the alternate key. Select it from the **Alternate Key** drop-down list. This option is available only when an alternate key is defined for the entity.
100
+
101
+
The alternate key is used to uniquely identify and update records during import. More information: [Define alternate keys to reference Dynamics 365 records](https://docs.microsoft.com/previous-versions/dynamicscrm-2016/administering-dynamics-365/dn949335(v=crm.8)?redirectedfrom=MSDN).
102
+
103
+
> [!div class="mx-imgBorder"]
104
+
> 
105
+
106
+
4. Select **Review Mapping** option and then on the **Review Mapping** page, review how your column headings are mapped to the fields in Dynamics 365.
107
+
108
+
> [!div class="mx-imgBorder"]
109
+
> 
110
+
111
+
- On the left side, by default the **Primary Fields** section of the **Review Mapping** page shows all the required fields for the entity that must be mapped for the data to be imported successfully.
112
+
- If you've selected an alternate key, all the fields of the alternate key also become required fields and must be mapped.
113
+
- If the column headings of your source file match the field display names, these fields will be automatically mapped. All the mapped fields will be shown with a green check mark.
114
+
- If the column headings don't match, the unmapped fields will be shown with a red exclamation point. Select a Dynamics 365 field to map to the unmapped column heading of your file.
115
+
- To quickly filter on only the unmapped fields, select **Unmapped** from the **Map Attributes** drop-down list.
116
+
117
+
5. In the **Optional Fields** section of the **Review Mapping** page, the left side shows the column headings in your source file. If the column headings match the field display names, the fields will be automatically selected in the corresponding drop-down lists.
118
+
119
+
- If the column headings don't match, the unmapped fields will be shown with a red exclamation point.
120
+
- Select a Dynamics 365 field to map to the unmapped column heading of your file.
121
+
- You can also choose **Ignore** from the drop-down list for one or more optional fields. Data from ignored columns won't be imported into Dynamics 365 Sales.
6. If any column in your source file includes a fixed set of values, you must map the column to a field of type **Option Set**. A column of this type has values such as "Yes" or "No," or "Hot," "Warm," or "Cold." To do this, select the  button next to the option set field. The **Option set mapping** section opens:
128
+
129
+
> [!div class="mx-imgBorder"]
130
+
> 
131
+
132
+
- For each **Source Option Values** item, select an item from the **Dynamics 365 Option Values** list to map it, and then select **OK**.
133
+
- The Dynamics 365 Option Values drop-down list combines the values available in the incoming file with those already in the Dynamics 365 database. For example:
134
+
-**Values in import file**: Low, High
135
+
-**Values already in Dynamics 365**: Cold, Warm, Hot
136
+
-**Resulting target values**: Cold, Warm, Hot, Low, High
137
+
- After import, the import wizard will add all mapped values to Dynamics 365, but will drop unmapped values from the import file that aren't yet in Dynamics 365. For example, you could map the "Low" source value to the "Cold" target value, but map the "High" source value to the (new) "High" target value. Based on these mappings, the import wizard creates "High" as a Dynamics 365 target value. It does not create "Low" as a Dynamics 365 target value because you didn't map any source to this target value.
138
+
139
+
>[!NOTE]
140
+
>You can also map a column in your source file to a field of type "Two Options" and "Multiselect Option Set" (where a field can have multiple values). You must map each **Source Option Values** to the items in the **Dynamics 365 Option Values** list. When mapping to a field of type "Multiselect Option Set," if your source file includes values that aren't available in Dynamics 365 Sales, new values won't be created in Dynamics 365 Sales.
141
+
142
+
7. If some data in your source file references other existing records in Dynamics 365 Sales, you must map the column in the source file to a lookup field of Dynamics 365 Sales.
143
+
144
+
For example, you might want to import a file named Leads.csv, which contains customer records. The **Customer** column in Leads.csv contains the associated account or contact data. To map this, select the **Lookup Reference** button next to the lookup field. The **Lookup Reference** section opens and lists the entities related to the current entity.
For each entity, select the fields to search during import to retain the relationships between the records, and then select **OK**.
150
+
151
+
8. To save your mapping settings for next time, enter a name in the **Name your data map** box. This way, the next time you need to import a similar set of data, you'll be able to use this mapping again.
152
+
153
+
> [!div class="mx-imgBorder"]
154
+
> 
155
+
156
+
9. When you're ready to continue, select **Finish Import** to import that data by using your mappings.
157
+
87
158
## Step 3: Check that the import is successful
88
159
89
160
After the wizard finishes, check your data (for example, list of contacts) to make sure they imported correctly.
@@ -92,6 +163,9 @@ After the wizard finishes, check your data (for example, list of contacts) to ma
92
163
93
164
2. Scroll through the contact list. Check that each person is listed and verify the contents of the fields for accuracy.
94
165
166
+
>[!NOTE]
167
+
>To verify the status of the imported records, view import logs. To view the import logs, go to **Settings** > **System** > **Data management** > **Imports**.
168
+
95
169
## Import double-byte characters
96
170
97
171
If you are importing data that includes double-byte characters for east asian languages, make sure the file is encoded as UTF-8 BOM. Plain UTF-8 may not be enough.
0 commit comments