We would need a way to mass update the modal changes and reflect to all nodes of the type being updated.
When I add a simple field to one of the nodes of the modal scheme I need to go through all the nodes of that type and change the metadata.
Need an easier way to handle modal metadata changes.
One idea could be to extend the ADT viewer. Another would be an api to update metadata for all nodes of the type being updated.1 vote
Thanks for the feedback! As we gather more feedback and understand more scenarios with regards to model versioning, we certainly want to continue to support updating twin data at scale. Please continue to upvote and provide feedback so that we can keep moving in the right direction!
In the meantime, check out this article on managing model versioning in our documentation – https://docs.microsoft.com/en-us/azure/digital-twins/how-to-manage-model#model-versioning
To support use cases in relation to spatial digital twins for eg. government, energy, smart cities, utilities etc. the inability to associate a twin to a geospatial definition is a limitation. Sure we can relate a twin to a geospatial definition held elsewhere, but the inclusion of location properties (point, polyline, polygon, arrays etc) would really open up the use case possibilities of standalone ADT0 votes
- Don't see your idea?