You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In practical use cases, twin hierarchies will often be created from data stored in a different database, or perhaps in a spreadsheet or a CSV file. This section illustrates how to read data from a CSV file and create a twin graph out of it.
164
+
This section describes strategies for creating a graph with multiple elements at the same time, rather than using individual API calls to upload models, twins, and relationships to upload them one by one.
165
165
166
-
Consider the following data table, describing a set of digital twins and relationships.
166
+
### Import graph with Azure Digital Twins Explorer
167
+
168
+
[Azure Digital Twins Explorer](concepts-azure-digital-twins-explorer.md) is a visual tool for viewing and interacting with your twin graph. It contains a feature for importing a graph file in either JSON or Excel format that can contain multiple models, twins, and relationships.
169
+
170
+
For detailed information about using this feature, see [Import graph](how-to-use-azure-digital-twins-explorer.md#import-graph) in the Azure Digital Twins Explorer documentation.
171
+
172
+
### Create twins and relationships from a CSV file
173
+
174
+
Sometimes, you might need to create twin hierarchies out of data stored in a different database, or in a spreadsheet or a CSV file. This section illustrates how to read data from a CSV file and create a twin graph out of it.
175
+
176
+
Consider the following data table, describing a set of digital twins and relationships. The models referenced in this file must already exist in the Azure Digital Twins instance.
167
177
168
178
| Model ID | Twin ID (must be unique) | Relationship name | Target twin ID | Twin init data |
Copy file name to clipboardExpand all lines: articles/digital-twins/how-to-use-azure-digital-twins-explorer.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -384,7 +384,7 @@ In the file selector box that appears, navigate on your machine to a folder cont
384
384
385
385
#### Limitations of bulk model upload
386
386
387
-
The limitations in this section apply to models that are contained within a single JSON file, therefore being uploaded at the same time.
387
+
The limitations in this section apply to models that are contained within a single JSON file, being uploaded to Azure Digital Twins Explorer at the same time.
388
388
389
389
While there's no limit to how many models you can include with a single JSON file, there are special considerations for files containing more than 50 models. If you're uploading more than 50 models within the same model file, follow these tips:
390
390
* If there are any models that inherit from other models that are defined in the same file, place them near the end of the list.
0 commit comments