Skip to content

Commit 6b7b323

Browse files
committed
Changed note text
1 parent 50c2079 commit 6b7b323

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

articles/iot-hub/iot-hub-devguide-routing-query-syntax.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -142,10 +142,9 @@ deviceClient.sendEvent(message, (err, res) => {
142142
> [!NOTE]
143143
> This shows how to handle the encoding of the body in javascript. If you want to see a sample in C#, download the [Azure IoT C# Samples](https://github.com/Azure-Samples/azure-iot-samples-csharp/archive/main.zip). Unzip the master.zip file. The Visual Studio solution *SimulatedDevice*'s Program.cs file shows how to encode and submit messages to an IoT Hub. This is the same sample used for testing the message routing, as explained in the [Message Routing tutorial](tutorial-routing.md). At the bottom of Program.cs, it also has a method to read in one of the encoded files, decode it, and write it back out as ASCII so you can read it.
144144
145-
146145
### Query expressions
147146

148-
A query on a message body needs to be prefixed with the `$body`. You can use a body reference, body array reference, or multiple body references in the query expression. Your query expression can also combine a body reference with message system properties, and message application properties reference. For example, the following are all valid query expressions:
147+
A query on a message body needs to be prefixed with `$body`. You can use a body reference, body array reference, or multiple body references in the query expression. Your query expression can also combine a body reference with message system properties, and message application properties reference. For example, the following are all valid query expressions:
149148

150149
```sql
151150
$body.Weather.HistoricalData[0].Month = 'Feb'
@@ -164,7 +163,7 @@ $body.Weather.Temperature = 50 AND processingPath = 'hot'
164163
```
165164

166165
> [!NOTE]
167-
> To filter a twin notification payload, run your query on the message body:
166+
> To filter a twin notification payload based on what changed, run your query on the message body:
168167
>
169168
> ```sql
170169
> $body.properties.desired.telemetryConfig.sendFrequency

0 commit comments

Comments
 (0)