Skip to content

Commit ebef025

Browse files
removed some content - wasn't too sure
1 parent a75e96d commit ebef025

File tree

1 file changed

+7
-37
lines changed

1 file changed

+7
-37
lines changed

articles/iot-operations/connect-to-cloud/howto-create-dataflow.md

Lines changed: 7 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -345,7 +345,7 @@ var assetDeltaSchema = '''
345345
'''
346346
```
347347

348-
To register the schema with the Azure Schema Registry, use the following Bicep configuration. This configuration creates a schema definition and assigns it a version within the schema registry, allowing it to be referenced later in your data transformations.
348+
The following Bicep configuration registers the schema with the Azure Schema Registry. This configuration creates a schema definition and assigns it a version within the schema registry, allowing it to be referenced later in your data transformations.
349349

350350
```bicep
351351
param opcuaSchemaName string = 'opcua-output-delta'
@@ -401,22 +401,12 @@ Currently, the enrich operation isn't available in the operations experience por
401401

402402
# [Bicep](#tab/bicep)
403403

404-
For example, you could use the `deviceId` field in the source data to match the `asset` field in the dataset:
404+
This example shows how you could use the `deviceId` field in the source data to match the `asset` field in the dataset:
405405

406406
```bicep
407407
builtInTransformationSettings: {
408-
datasets: [
409-
{
410-
key: 'assetDataset'
411-
inputs: [
412-
'$source.deviceId', // Reference to the device ID from the source
413-
'$context(assetDataset).asset' // Reference to the asset from the dataset context
414-
]
415-
expression: '$1 == $2' // Expression to evaluate the inputs
416-
}
417-
]
408+
// TODO: Add bicep template to enrich data
418409
}
419-
420410
```
421411

422412
### Passthrough operation
@@ -431,8 +421,6 @@ builtInTransformationSettings: {
431421
output: '*'
432422
}
433423
]
434-
schemaRef: 'aio-sr://${opcuaSchemaName}:${opcuaSchemaVer}'
435-
serializationFormat: 'Delta' // Can also be 'Parquet'
436424
}
437425
```
438426

@@ -488,18 +476,12 @@ To filter the data on a condition, you can use the `filter` stage. The condition
488476

489477
For example, you could use the `temperature` field in the source data to filter the data:
490478

479+
```bicep
491480
```bicep
492481
builtInTransformationSettings: {
493-
filter: [
494-
{
495-
inputs: [
496-
'temperature ? $last' // Reference to the last temperature value, if available
497-
]
498-
expression: '$1 > 20' // Expression to filter based on the temperature value
499-
}
500-
]
482+
// TODO: Add bicep template to filter data
501483
}
502-
484+
```
503485
```
504486
505487
# [Kubernetes](#tab/kubernetes)
@@ -542,19 +524,7 @@ For example, you could use the `temperature` field in the source data to convert
542524
```bicep
543525
builtInTransformationSettings: {
544526
map: [
545-
{
546-
inputs: [
547-
'temperature' // Reference to the temperature input
548-
]
549-
output: 'temperatureCelsius' // Output variable for the converted temperature
550-
expression: '($1 - 32) * 5/9' // Expression to convert Fahrenheit to Celsius
551-
}
552-
{
553-
inputs: [
554-
'$context(assetDataset).location' // Reference to the location from the dataset context
555-
]
556-
output: 'location' // Output variable for the location
557-
}
527+
// TODO: Add bicep template to move data from one field to another
558528
]
559529
}
560530

0 commit comments

Comments
 (0)