...
| (rowId) | column2 | column3 | column4 | column5 |
|---|---|---|---|---|
| 1 | Racer Y | 41.33 | DQ | 38.04 |
| 2 | Racer | Heat 1 | Heat 2 | Heat 3 |
| 3 | Racer X | 37.22 | 38.22 | 37.61 |
| 4 | Racer Z | 39.27 | 39.04 | 38.85 |
While you can undo your sort steps to return to the original sort order, this approach works best if you did not include other steps in between that are based on the sort order.
If you have steps that require retaining your sort steps, you can revert to the original sort order by adding this transform stepYou can use the following transformation to use the third row as your header for each column:
| Info |
|---|
NOTE: Source row information may be lost after operations such as joins, unions, and aggregations are performed. In these cases, you cannot sort by the source row information. You may be able to generate a column of source row number earlier in your recipeThe following does not use the header transform. |
| D code |
|---|
sort order:SOURCEROWNUMBER() |
Then, you can create the header with the following simple step:
| D code |
|---|
header sourcerownumber:1rename type: header method: index sourcerownumber: 3 |
Results:
After you have applied the last header transform, your data should look like the following:
...
