Merge pull request #208689 from dominicbetts/central-model-export

prmerger-automator[bot] · web-flow · commit 053a1dd9ef50 · 2022-08-22T13:30:49.000Z
IoT Central: Model export updates
diff --git a/articles/iot-central/core/concepts-device-implementation.md b/articles/iot-central/core/concepts-device-implementation.md
@@ -46,7 +46,7 @@ A DTDL model can be a _no-component_ or a _multi-component_ model:
 - Multi-component model. A more complex model that includes two or more components. These components include a single root component, and one or more nested components. For an example, see the [Temperature Controller](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/DTDL/v2/samples/TemperatureController.json) model.
 
 > [!TIP]
-> You can [export a device model](howto-set-up-template.md#interfaces-and-components) from an IoT Central device template as a DTDL v2 file.
+> You can [import and export a complete device model or individual interface](howto-set-up-template.md#interfaces-and-components) from an IoT Central device template as a DTDL v2 file.
 
 To learn more about device models, see the [IoT Plug and Play modeling guide](../../iot-develop/concepts-modeling-guide.md)
 
diff --git a/articles/iot-central/core/concepts-device-templates.md b/articles/iot-central/core/concepts-device-templates.md
@@ -66,11 +66,11 @@ To lean more about the DPS payload, see the sample code used in the [Tutorial: C
 
 ## Device models
 
-A device model defines how a device interacts with your IoT Central application. The device developer must make sure that the device implements the behaviors defined in the device model so that IoT Central can monitor and manage the device. A device model is made up of one or more _interfaces_, and each interface can define a collection of _telemetry_ types, _device properties_, and _commands_. A solution developer can import a JSON file that defines the device model into a device template, or use the web UI in IoT Central to create or edit a device model.
+A device model defines how a device interacts with your IoT Central application. The device developer must make sure that the device implements the behaviors defined in the device model so that IoT Central can monitor and manage the device. A device model is made up of one or more _interfaces_, and each interface can define a collection of _telemetry_ types, _device properties_, and _commands_. A solution developer can import a JSON file that defines a complete device model or individual interface into a device template, or use the web UI in IoT Central to create or edit a device model.
 
 To learn more about editing a device model, see [Edit an existing device template](howto-edit-device-template.md)
 
-A solution developer can also export a JSON file that contains the device model. A device developer can use this JSON document to understand how the device should communicate with the IoT Central application.
+A solution developer can also export a JSON file from the device template that contains a complete device model or individual interface. A device developer can use this JSON document to understand how the device should communicate with the IoT Central application.
 
 The JSON file that defines the device model uses the [Digital Twin Definition Language (DTDL) V2](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/DTDL/v2/dtdlv2.md). IoT Central expects the JSON file to contain the device model with the interfaces defined inline, rather than in separate files. To learn more, see [IoT Plug and Play modeling guide](../../iot-develop/concepts-modeling-guide.md).
 
@@ -345,7 +345,7 @@ You can choose queue commands if a device is currently offline by enabling the *
 Offline commands are one-way notifications to the device from your solution. Offline commands can have request parameters but don't return a response.
 
 > [!NOTE]
-> This option is only available in the IoT Central web UI. This setting isn't included if you export a model or interface from the device template.
+> Offline commands are marked as `durable` if you export the model as DTDL.
 
 ## Cloud properties
 
diff --git a/articles/iot-central/core/concepts-telemetry-properties-commands.md b/articles/iot-central/core/concepts-telemetry-properties-commands.md
@@ -1062,7 +1062,7 @@ When the device has finished processing the request, it should send a property t
 
 In the IoT Central web UI, you can select the **Queue if offline** option for a command. Offline commands are one-way notifications to the device from your solution that are delivered as soon as a device connects. Offline commands can have a request parameter but don't return a response.
 
-The **Queue if offline** setting isn't included if you export a model or interface from the device template. You can't tell by looking at an exported model or interface JSON that a command is an offline command.
+Offline commands are marked as `durable` if you export the model as DTDL.
 
 Offline commands use [IoT Hub cloud-to-device messages](../../iot-hub/iot-hub-devguide-messages-c2d.md) to send the command and payload to the device.
 
diff --git a/articles/iot-central/core/howto-manage-device-templates-with-rest-api.md b/articles/iot-central/core/howto-manage-device-templates-with-rest-api.md
@@ -180,7 +180,7 @@ The request body has some required fields:
 * `capabilityModel` : Every device template has a capability model. A relationship is established between each module capability model and a device model. A capability model implements one or more module interfaces.
 
 > [!TIP]
-> The device template JSON is not a standard DTDL document. The device template JSON includes IoT Central specific data such as cloud property definitions and display units. You can use the device template JSON format to import and export device templates in IoT Central by using the REST API and the CLI.
+> The device template JSON is not a standard DTDL document. The device template JSON includes IoT Central specific data such as cloud property definitions and display units. You can use the device template JSON format to import and export device templates in IoT Central by using the REST API, the CLI, and the UI.
 
 There are some optional fields you can use to add more details to the capability model, such as display name and description.
 
diff --git a/articles/iot-central/core/howto-set-up-template.md b/articles/iot-central/core/howto-set-up-template.md
@@ -212,7 +212,7 @@ Cloud-to-device messages:
 - Require the device to implement a message handler to process the cloud-to-device message.
 
 > [!NOTE]
-> This option is only available in the IoT Central web UI. This setting isn't included if you export a model or component from the device template.
+> Offline commands are marked as `durable` if you export the model as DTDL.
 
 ## Cloud properties
 
diff --git a/articles/iot-central/core/howto-use-commands.md b/articles/iot-central/core/howto-use-commands.md
@@ -99,7 +99,7 @@ The following snippet shows the JSON representation of the command in the device
 ```
 
 > [!TIP]
-> You can export a device model from the device template page.
+> You can export a device model or interface from the device template page.
 
 You can relate this command definition to the screenshot of the UI using the following fields:
 
