To easily get a clear overview of the Digital Twins hierarchy of spaces, it would be great to add a (readonly) graph viewer for Digital Twins. A graph viewer has already been build and published to GitHub. Why not add this option to the Azure portal as the Digital Twins Explorer. (https://github.com/Azure/azure-digital-twins-graph-viewer)
Optionaly the explorer could be used to add, modify of delete spaces, devices or sensors in a non-readonly mode.

Currently, if you'd add a new sensor, for instance a 'Gas' sensor, we'd like to provide the following types:
Type: Manufacturer
Data type: Gas
Data sub type: Delivery
Data unit type: CubicMeterGas

However, the Data sub type has to be named 'DeliveryGas'. Even though we'd also like an Energy sensor with:
Type: Manufacturer
Data type: Energy
Data sub type: Delivery
Data unit type: KilowattHourEnergy

Now we have to define two separate sub types. If this is by design, let us know :)

Please add support for providing parameters for a Time Series Insights instance to which the Digital Twin resource can export all of its historical device data.

Since a max node limit now exists on API GET calls, it would be helpful to have support for the ODATA $count feature.

It save a lot of time if there was a downloadable Postman collection with the API calls already defined (as with Swagger). It is simple to export/import a collection and environments can be used to ensure that credentials are kept separate.

Current Space graph model of digital twin does not store historical information, such as sensor data. Model should have capability to define the store and attached to Sensor(s) and other model

The user is able to create a backup of ADT data and restore it using by ADT API. It's possible to backup one subscription and restore data in other empty subscription

After deleting my Digital Twins instance and deploying one with the same name a few minutes later I can't make any requests to the instance without the following error:

{
"error": {

"code": "500.600.999.999",

"message": "The underlying provider failed on Open.",

"innererror": {

  "code": "500.600.999.999",

  "message": "Login failed for user 'ManagementApi'."

}

}
}

This occurs on a GET request to
https://<instance-name>.westeurope.azuresmartspaces.net/management/api/v1.0/devices

When we specify a min and/or max value for creating a property key of type 'DateTime', we get an error stating that the min/max is invalid.

According to the doc, ISO8601 datetimes should be used, but:
- DateTime.ToString("o") gives a value that is too long (more than 20 chars, due to milliseconds);
- A string like "2000-01-01T00:00:00Z" is not accepted for instance;
- Tried with epoch notation, no luck either;

Do you have an example of a proper value? Could the documentation be updated to show such example? Or if it is a bug, then...

Thanks!

Space graph - Current Schema support, parent can have multiple children, However, we also need Schema to support child to have multiple parents as graph

Hello,

I recently moved a device from one spaceId to another via API call from Postman. To my surprise, the sensors attached to that device were still assigned to the previous spaceId. But, in the Azure Digital Twins Graph Viewer, they were properly displayed. Is this a bug in the API or is it a desired behaviour?

Kind regards,
Tudor Mazilu

It would be really helpful to be able to search for values within the content of the Digital Twins, e.g. searching in the names, properties, keys and attachments of the nodes within the Azure Twin tree.

Would be nice to be able to upload blobs using chunked API that Azure Blob Storage already uses. Also, would be nice to be able to associate a Storage Container with Space, so that all the blobs in that Space hierarchy would be stored there. Thanks!

We are service integrators, would like to understand how the spacial maps are created, say the Map of Building

Support for building the Azure Digital Twin special model from the existing automation systems which are based on Industry standard like ISA95, ISA106, AutomationML

Here's what the API metadata says is produced for ErrorInformation when creating a new Device with a POST call:

{
"code": "string",
"message": "string",
"target": "string",
"details": [

null

],
"exception": {}
}

Here's what's actually produced:

{"error":{"code":"400.600.000.000","message":"Device already exists."}}

The claimed ErrorInformation object is actually a child of what's produced in the "error" property, rather than being the root object. Please fix this as it is breaking our error handling strategies for Digital Twin.

How do you deal with conflictig permissions in Role defintions?

Is it a union of all permissions or intersection?