Merge pull request #218767 from dominicbetts/central-revert-error-view

IoT Central: temporary revert of previous PR

Author: BCS2022

articles/iot-central/core/concepts-telemetry-properties-commands.md

@@ -3,7 +3,7 @@ title: Telemetry, property, and command payloads in Azure IoT Central | Microsof
 description: Azure IoT Central device templates let you specify the telemetry, properties, and commands of a device must implement. Understand the format of the data a device can exchange with IoT Central.
 author: dominicbetts
 ms.author: dobett
-ms.date: 10/28/2022
+ms.date: 06/08/2022
 ms.topic: conceptual
 ms.service: iot-central
 services: iot-central
@@ -36,8 +36,6 @@ The JSON file that defines the device model uses the [Digital Twin Definition La
 
 For sample device code that shows some of these payloads in use, see the [Create and connect a client application to your Azure IoT Central application](tutorial-connect-device.md) tutorial.
 
-To troubleshoot payload errors, see [Unmodeled data issues](troubleshoot-connection.md#unmodeled-data-issues) in the troubleshooting FAQ.
-
 ## View raw data
 
 IoT Central lets you view the raw data that a device sends to an application. This view is useful for troubleshooting issues with the payload sent from a device. To view the raw data a device is sending:
@@ -48,9 +46,7 @@ IoT Central lets you view the raw data that a device sends to an application. Th
 
     :::image type="content" source="media/concepts-telemetry-properties-commands/raw-data.png" alt-text="Screenshot that shows the raw data view." lightbox="media/concepts-telemetry-properties-commands/raw-data.png":::
 
-    On this view, you can select the columns to display, set column widths, set a time range to view, and filter the messages.
-    * The **Unmodeled data** column shows data from the device that doesn't match any property or telemetry definitions in the device template.
-    * The **Error** column shows any error status for the message. To see details of the error, expand the message.
+    On this view, you can select the columns to display and set a time range to view. The **Unmodeled data** column shows data from the device that doesn't match any property or telemetry definitions in the device template.
 
 ## Telemetry
 

articles/iot-central/core/media/troubleshoot-connection/raw-data-error-detail.png

@@ -4,7 +4,7 @@ description: Troubleshoot why you're not seeing data from your devices in IoT Ce
 services: iot-central
 author: dominicbetts
 ms.author: dobett
-ms.date: 10/28/2022
+ms.date: 03/24/2022
 ms.topic: troubleshooting
 ms.service: iot-central
 ms.custom: device-developer, devx-track-azurecli
@@ -178,59 +178,6 @@ Here is a list of common error codes you might see when a device tries to upload
 
 When you've established that your device is sending data to IoT Central, the next step is to ensure that your device is sending data in a valid format.
 
-### Invalid JSON
-
-Use the **Raw data** view in your IoT Central to investigate invalid JSON errors.
-
-If the payload from the device includes invalid JSON, the **Raw data** view flags the message with the **JsonValidationError** error in the **Errors** column:
-
-:::image type="content" source="media/troubleshoot-connection/raw-data-error.png" alt-text="Screenshot that shows messages with a JSON validation error.":::
-
-> [!TIP]
-> To make it easier to find error messages, you can filter the **Raw data** view by error type, change column widths, and change the column order.
-
-To see the details of the invalid JSON, expand the message:
-
-:::image type="content" source="media/troubleshoot-connection/raw-data-error-detail.png" alt-text="Screenshot that shows the details of a message with invalid JSON.":::
-
-The payload shown by IoT Central has an `_error` object that includes the error code and message. It also shows the original invalid JSON payload. The previous example shows that the JSON message contained one or more `,` characters where there should be a `:` character. The device sent a message that looks like:
-
-```json
-{
-  "payload": [
-    {
-      "temp", 61.000000,
-      "humidity", 70.000000
-    },
-    {
-      "temp", 53.000000,
-      "humidity", 60.000000
-    }
-  ]
-}
-```
-
-The message should look like:
-
-```json
-{
-  "payload": [
-    {
-      "temp": 61.000000,
-      "humidity": 70.000000
-    },
-    {
-      "temp": 53.000000,
-      "humidity": 60.000000
-    }
-  ]
-}
-```
-
-To learn more about message payloads, see [Telemetry, property, and command payloads](concepts-telemetry-properties-commands.md).
-
-### Data not appearing in IoT Central
-
 To detect which categories your issue is in, run the most appropriate Azure CLI command for your scenario:
 
 - To validate telemetry, use the preview command:
@@ -247,9 +194,10 @@ To detect which categories your issue is in, run the most appropriate Azure CLI
 
 You may be prompted to install the `uamqp` library the first time you run a `validate` command.
 
-The two common types of issue that cause device data to not appear in IoT Central are:
+The three common types of issue that cause device data to not appear in IoT Central are:
 
 - Device template to device data mismatch.
+- Data is invalid JSON.
 - Old versions of IoT Edge cause telemetry from components to display incorrectly as unmodeled data.
 
 ### Device template to device data mismatch
@@ -290,6 +238,12 @@ When you've detected the issue, you may need to update device firmware, or creat
 
 If you chose to create a new template that models the data correctly, migrate devices from your old template to the new template. To learn more, see [Manage devices in your Azure IoT Central application](howto-manage-devices-individually.md).
 
+### Invalid JSON
+
+If there are no errors reported, but a value isn't appearing, then it's probably malformed JSON in the payload the device sends. To learn more, see [Telemetry, property, and command payloads](concepts-telemetry-properties-commands.md).
+
+You can't use the validate commands or the **Raw data** view in the UI to detect if the device is sending malformed JSON.
+
 ### IoT Edge version
 
 To display telemetry from components hosted in IoT Edge modules correctly, use [IoT Edge version 1.2.4](https://github.com/Azure/azure-iotedge/releases/tag/1.2.4) or later. If you use an earlier version, telemetry from components in IoT Edge modules displays as *_unmodeleddata*.