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
Below are functions that aren't supported. This list isn't exhaustive and is subject to change.
114
-
* Merge columns (can be achieved with AddColumn)
115
-
* Split column
116
-
* Append queries
117
-
* 'Use first row as headers' and 'Use headers as first row'
111
+
## Known unsupported functions
112
+
113
+
| Function | Status |
114
+
| -- | -- |
115
+
| Table.PromoteHeaders | Not supported. The same result can be achieved by setting “First row as header” in the dataset. |
116
+
| Table.CombineColumns | This is a common scenario that isn't directly supported but can be achieved by adding a new column that concatenates two given columns. For example, Table.AddColumn(RemoveEmailColumn, “Name”, each [FirstName] & ” ” & [LastName]) |
117
+
| Table.TransformColumnTypes | This is supported in most cases. The following scenarios are unsupported: transforming string to currency type, transforming string to time type, transforming string to Percentage type. |
118
+
| Table.NestedJoin | Just doing a join will result in a validation error. The columns must be expanded for it to work. |
| Table.RowCount | Not supported, but can be achieved with an add column with all cells empty (condition column can be used) and then using group by on that column. Table.Group is supported. |
122
+
| Row level error handling | Row level error handling is currently not supported. For example, to filter out non-numeric values from a column, one approach would be to transform the text column to a number. Every cell which fails to transform will be in an error state and need to be filtered. This scenario isn't possible in wrangling data flow. |
123
+
| Table.Transpose | Not supported |
124
+
| Table.Pivot | Not supported |
118
125
119
126
## Next steps
127
+
128
+
Learn how to [create a wrangling data flow](wrangling-data-flow-tutorial.md).
When you create a wrangling data flow, all source datasets become dataset queries and are placed in the **ADFResource** folder. By default, the UserQuery will point to the first dataset query. All transformations should be done on the UserQuery as changes to dataset queries are not supported nor will they be persisted. Renaming, adding and deleting queries is currently not supported.
Currently not all Power Query M functions are supported for data wrangling despite being available during authoring. While building your wrangling data flows, you'll be prompted with the following error message if a function isn't supported:
54
+
55
+
`The wrangling data flow is invalid. Expression.Error: The transformation logic isn't supported. Please try a simpler expression`
56
+
57
+
For more information on supported transformations, see [wrangling data flow functions](wrangling-data-flow-functions.md).
58
+
59
+
Currently wrangling data flow only supports writing to one sink.
60
+
37
61
## Next steps
38
62
39
63
Learn how to [create a wrangling data flow](wrangling-data-flow-tutorial.md).
0 commit comments