Write Facility Data Back to a Tandem Twin
A 6-step recipe with Autodesk. We can help you get access.
Recipe · 6 steps
Write Facility Data Back to a Tandem Twin
with Autodesk · Digital Twin & Asset Data
Scan twin elements and write custom property values back to them.
- List the digital twin facilities the authenticated user can reach and take the first as the working twin.
- List the BIM models bound to the twin. Element data is addressed per model, not per twin.
- Read the twin's schema. This tells the integration which custom property attributes exist and are therefore writable, before it attempts a mutation.
- Scan the model for the elements of interest, narrowed by category and family so a large facility does not return every element in the building.
- Read the current property values for the specific element keys being synced, so the caller can diff before writing.
- Write the new custom property values onto the elements. Requires data:write, and will reject any property that is not part of a user-created schema.
What you'll need to have ready
- twinName: Name of the target facility twin, used to identify it among the listed twins.
- categoryId: Revit category id to restrict the element scan to.
- families: Revit family names to restrict the element scan to.
- propertyFamily: Property family qualifier for the columns to return (the "fam" value).
- propertyColumn: Property column qualifier for the columns to return (the "col" value).
- elementKeys: Element keys to read properties for, as returned by the scan.
- mutationElementKey: The single element key to write custom property values onto. Callers syncing many elements send one mutation entry per key.
- propertyUpdates: Custom property values to write, keyed by property family and column. Only properties from user-created schemas are mutable.
For your developer
Arazzo workflow autodesk:sync-element-properties, 6 operations: getTwins → getModels → getSchema → scanElements → getElementProperties → mutateElements. Specs on APIs.io.