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: articles/iot-operations/connect-to-cloud/howto-create-dataflow.md
+44-40Lines changed: 44 additions & 40 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -471,9 +471,9 @@ To learn more, see [Understand message schemas](concept-schema-registry.md).
471
471
472
472
The transformation operation is where you can transform the data from the source before you send it to the destination. Transformations are optional. If you don't need to make changes to the data, don't include the transformation operation in the dataflow configuration. Multiple transformations are chained together in stages regardless of the order in which they're specified in the configuration. The order of the stages is always:
473
473
474
-
1. **Enrich**, **Rename**, or add a **New property**: Add additional data to the source data given a dataset and condition to match.
474
+
1. **Enrich**: Add additional data to the source data given a dataset and condition to match.
475
475
1. **Filter**: Filter the data based on a condition.
476
-
1. **Map**or **Compute**: Move data from one field to another with an optional conversion.
476
+
1. **Map**, **Compute**, **Rename**, or add a **New property**: Move data from one field to another with an optional conversion.
477
477
478
478
# [Portal](#tab/portal)
479
479
@@ -519,43 +519,7 @@ You can load sample data into the state store by using the [DSS set tool sample]
519
519
520
520
# [Portal](#tab/portal)
521
521
522
-
In the operations experience, the *Enrich* stage is currently supported using the **Rename** and **New property** transforms.
523
-
524
-
#### Rename
525
-
526
-
You can rename a datapoint using the **Rename** transform. This operation is used to rename a datapoint in the source data to a new name. The new name can be used in the subsequent stages of the dataflow.
527
-
528
-
1. Under **Transform (optional)**, select **Rename** > **Add**.
529
-
530
-
:::image type="content" source="media/howto-create-dataflow/dataflow-rename.png" alt-text="Screenshot using operations experience to rename a datapoint.":::
| Datapoint | Select a datapoint from the dropdown or enter a $metadata header using the format `$metadata.<header>.` |
537
-
| New datapoint name | Enter the new name for the datapoint. |
538
-
| Description | Provide a description for the transformation. |
539
-
540
-
1. Select **Apply**.
541
-
542
-
#### New property
543
-
544
-
You can add a new property to the source data using the **New property** transform. This operation is used to add a new property to the source data. The new property can be used in the subsequent stages of the dataflow.
545
-
546
-
1. Under **Transform (optional)**, select **New property** > **Add**.
547
-
548
-
:::image type="content" source="media/howto-create-dataflow/dataflow-new-property.png" alt-text="Screenshot using operations experience to add a new property.":::
| Property key | Enter the key for the new property. |
555
-
| Property value | Enter the value for the new property. |
556
-
| Description | Provide a description for the new property. |
557
-
558
-
1. Select **Apply**.
522
+
Currently, the *Enrich* stage isn't operations experience.
559
523
560
524
# [Bicep](#tab/bicep)
561
525
@@ -670,7 +634,47 @@ To map the data to another field with optional conversion, you can use the `map`
670
634
671
635
# [Portal](#tab/portal)
672
636
673
-
In the operations experience, mapping is currently supported using **Compute** transforms.
637
+
In the operations experience, mapping is currently supported using **Compute**, **Rename**, and **New property** transforms.
638
+
639
+
#### Rename
640
+
641
+
You can rename a datapoint using the **Rename** transform. This operation is used to rename a datapoint in the source data to a new name. The new name can be used in the subsequent stages of the dataflow.
642
+
643
+
1. Under **Transform (optional)**, select **Rename** > **Add**.
644
+
645
+
:::image type="content" source="media/howto-create-dataflow/dataflow-rename.png" alt-text="Screenshot using operations experience to rename a datapoint.":::
| Datapoint | Select a datapoint from the dropdown or enter a $metadata header using the format `$metadata.<header>.` |
652
+
| New datapoint name | Enter the new name for the datapoint. |
653
+
| Description | Provide a description for the transformation. |
654
+
655
+
1. Select **Apply**.
656
+
657
+
#### New property
658
+
659
+
You can add a new property to the source data using the **New property** transform. This operation is used to add a new property to the source data. The new property can be used in the subsequent stages of the dataflow.
660
+
661
+
1. Under **Transform (optional)**, select **New property** > **Add**.
662
+
663
+
:::image type="content" source="media/howto-create-dataflow/dataflow-new-property.png" alt-text="Screenshot using operations experience to add a new property.":::
| Property key | Enter the key for the new property. |
670
+
| Property value | Enter the value for the new property. |
671
+
| Description | Provide a description for the new property. |
672
+
673
+
1. Select **Apply**.
674
+
675
+
#### Compute
676
+
677
+
You can use the **Compute** transform to apply a formula to the source data. This operation is used to apply a formula to the source data and store the result field.
674
678
675
679
1. Under **Transform (optional)**, select **Compute** > **Add**.
0 commit comments